Time-related values should be displayed using the user's time formatting preferences.
Version: master
Severity: major
Whiteboard: u=dev c=backend p=0
Time-related values should be displayed using the user's time formatting preferences.
Version: master
Severity: major
Whiteboard: u=dev c=backend p=0
Project | Branch | Lines +/- | Subject | |
---|---|---|---|---|
mediawiki/extensions/Wikibase | master | +12 -12 | Allow wikibase-time-precision-* to be translated, expand Qqq |
li3939108 wrote:
YYYY-MM-DD is very OK for Chinese. Something like "Jan 20 2013" seems rather strange when internationalized but not localized.
There is a partial solution implemented in the frontend in Change-Id: I093af8477b1bba7ea3fca497d03561a9c52b8d93.
This does reordering of day, month and year according to the user preference. However this does not support all available settings in MW and will fall back to "mdy" for not supported settings.
I've submitted Change-Id: Ib2073071b5d46eaf9cbd1d09ac92a842a0ef4233 that change wgPageContentLanguage to the language of the displayed content (ie, for Wikibase entities, the user language). If this change is merged, wgDefaultDateFormat will be, for entities, in the user language and may be used as default format for dates, if the user haven't configure anything.
In some languages, such as Hebrew it isn't correct to write "27 June" but instead "27th of June"
[in Hebrew:
27 יוני - wrong
27 ביוני - correct
]
The correct way to define format of day and month is "j xg" and not "j F". (The same way as it is defined in preferences)
see related change: https://gerrit.wikimedia.org/r/#/c/142519/
Date format for Hungarian is broken.
Instead of "1970. január 1." it is "1 január 1970" This is also valid for the {{#property}} parser function on huwiki. It was fine in November 2013. Why it has changed?
Suggestion from the sprint planning meeting:
Change 202455 had a related patch set uploaded (by Hoo man):
Allow wikibase-time-precision-* to be translated, expand Qqq
Change 202455 merged by jenkins-bot:
Allow wikibase-time-precision-* to be translated, expand Qqq
IMO this bug is solved, as these can be localized now... but we should probably create some bug about having a better (more flexible) localization system than we have now.