Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.The problem
Date format localization is currently handled by the system module, which provides its own UI not consistent with the rest of the localization system and requires features -config translation- provided by locale module. This causes multiple issues ranging from usability to some ugly workarounds to update localized formats, to hidden functional dependencies (and maybe the feature being in the wrong module).
Proposed solution
- Move Date format localization to locale module (#2059835: Implement translation interface for date formats as part of locale UI)
- Use the right API, aka config translation, to update and handle date format localization.
- Integrate the UI with Regional and Language / User Interface translation.
- Make it consistent with interface translation respecting locale settings like 'translate english'.
Related issues
While there are multiple related issues, none of them is trying to address the problem as a whole, but just a few symptoms/sides of it.
The main patch, that needs review and UI discussion, #2059835: Implement translation interface for date formats as part of locale UI
#2003892: Convert date formats to config entities
#2003802: Under Configuration => regional and language, merge Regional settings and date and time formats
#987534: Default installed vocabulary name, tags, date types, block region names, timezone locations, tabs and menus not translatable
#2015021: Update configuration schema of system date formats
#1966538: Translation is not updated for configuration, when the config changes
#1267520: Improve date and time localization user experience
#2098089: Date formats cannot be translated (the core UIs are useless)
#2100351: Date format name 'custom' is reserved but not checked for
Remaining Tasks
- click through the UI and figure out the features, a full UI / feature comparison of D7 and D8, so we know what regressed in fact.
Comments
Comment #1
Gábor HojtsyThe purpose of the date formats to languages feature is to assign languages to different date formats. It does not actually make it possible to assign different date formats for different languages I believe. I don't fully grasp how it uses the language overrides and if so why it stores language copies that may be the same. I think I posted several things to this effect on the original issue, but it was a big conversion either way. I may have understood it at one point but cannot recall :(
Comment #1.0
Gábor HojtsyRemoved issue retagged for D7 instead of D8 #939392: Localized date formats are initialized too late
Comment #2
Gábor HojtsyRetitling so the problem is more evident, also raising to major.
Comment #3
Gábor HojtsyAlso a regression.
Comment #3.0
Gábor HojtsyUpdated issue summary.
Comment #4
Gábor HojtsyComment #5
penyaskitoCreated #2095917: Move Date format localization to language module
Comment #5.0
penyaskitoadded task to do a full feature comparison to identify regressions
Comment #5.1
penyaskitoAdded subtask
Comment #6
penyaskitoClosing that as duplicated, added #2059835: Implement translation interface for date formats as part of locale UI to the summary instead.
Comment #7
Gábor HojtsyI opened #2098089: Date formats cannot be translated (the core UIs are useless) to cover this with schema. IMHO there is a very quick way in config_translation to solve it, and that would be the first step.
Comment #7.0
Gábor HojtsyRemoving duplicated
Comment #7.1
Gábor HojtsyAdd https://drupal.org/node/2098089
Comment #8
Gábor HojtsySeveral other subissues are on sprint.
Comment #8.0
Gábor HojtsyAdded #2100351
Comment #9
BerdirBump,are there still issues here?
Comment #10
Gábor Hojtsy@Berdir: for starters, moved #987534: Default installed vocabulary name, tags, date types, block region names, timezone locations, tabs and menus not translatable to 7.x and #1267520: Improve date and time localization user experience is duplicate of other issues. #2003802: Under Configuration => regional and language, merge Regional settings and date and time formats would probably still make sense but that seems to be the only remaining issue of this meta.
#1345758: META: Provide locale (regional) formats framework for automated translation of non textual data is a much larger meta that is related but has a lot broader scope.
So not sure this META is worth keeping around.