Closed (duplicate)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Aug 2013 at 19:47 UTC
Updated:
29 Jul 2014 at 22:44 UTC
Jump to comment: Most recent file

Comments
Comment #1
jose reyero commentedAnd here's the patch (that produces the UI above). In short:
- Move all date format localization to locale module.
- Create new UI that allows to translate existing date formats.
- Cleans up the configuration translations for date formats created by the old system, which had a lot of duplicated date.
To do:
- Well, discuss the new UI....
- Update tests.
- Remove language (locale) options from date format configurations
Comment #3
gábor hojtsyHow does this compare to the Drupal 7 features? There does not seem to be an upgrade path in this code(?)
Comment #4
jair commentedComment #5
penyaskito+ Needs usability review, but IMHO it looks far better than D7 UI. Congrats!
I started reviewing the patch and I have some comments.
1.
Needs to be removed or not commented.
2.
Namespace should be Drupal\locale\Form now.
3.
I think we shouldn't be calling theme() but returning the render array, but this is a theme_* function so I am not really sure about it. Maybe affected by #2006152: [meta] Don't call theme() directly anywhere outside drupal_render()?
Comment #6
gábor hojtsyI think this should still have a more holistic look and hopefully natively integrated with config translation.
Comment #7
gábor hojtsyAFAIS let's focus on solving this with a standard solution as part of config translation, that already manages the files, we can integrate this with locale module (localize.drupal.org distribution of translations). So I think this is covered by #2098089: Date formats cannot be translated (the core UIs are useless) and #2099997: Use config translation to translate date formats and will have a standard solution in core the same way every other config has.