-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unify display of dates across the app #853
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Closing, converted to a feature request in #4156 because this isnt a bug |
MacOSX 10.11.6, FreeTube 0.9.3 Beta
If possible, please unify the display of dates across the app. Currently, in the case of Croatian, two different date formats are used:
span.uploadedTime
=> 30. 07. 2015.div.datePublished
=> srp 30, 2015 (See screenshot below.)Ideally, only one date format per language/locale should be used.
In the case of Croatian, span.uploadedTime would be correct, while div.datePublished is completely unusable/wrong.
The text was updated successfully, but these errors were encountered: