You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can't concatenate localized strings because RTL and other languages might not accept this order. Localized strings should be a single string with arguments. However with durations we need multiple variables to define the plurals, which we can't do (too many combinations), so we need to choose a form that will work in all cases.
Suggestions, with the example of 2 days and 3 minutes.
2 different strings
When it's not a single unit: "approximately 2 days" and for single units: "2 days"
Only use the biggest unit: "2 days"
We will ignore the smaller parts of the duration.
The text was updated successfully, but these errors were encountered:
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).
This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.
@MikeAlhayek note that the actual HTML should display the simple translated text, and have a tooltip with the actual duration in an official dotnet format. Check the GH commits history that shows when a commit was merged.
In DateTimeShapes
We can't concatenate localized strings because RTL and other languages might not accept this order. Localized strings should be a single string with arguments. However with durations we need multiple variables to define the plurals, which we can't do (too many combinations), so we need to choose a form that will work in all cases.
Suggestions, with the example of 2 days and 3 minutes.
When it's not a single unit: "approximately 2 days" and for single units: "2 days"
We will ignore the smaller parts of the duration.
The text was updated successfully, but these errors were encountered: