Title: Message Title
Christian Ringele updated an issue
Suggestion Box / SUGGEST-36
New i18n mechanism: Provide a conveniant way to get the complete list of the auto generated keys.
Change By:
Christian Ringele
Hi,I discussed it quickly with topher Yopher yesterday:I think we need to provide the possibility to get all keys of a certain module (light & non light modules) in a conveniant convenient way.I love the new mechanis mechanism , as it prevents me of having to define all the keys in the config manually.But it has a big downside:The keys get generated by a certain pattern.So its hard to know for the developer, which keys will be in the end expected by Magnolia.Having to do that manually uses even more time then having to add them manually to the configuration, because there I can just use any key I want (foo.blah would work).There is a config that can be used to get a out for apps:config:modules/i18n/config@debug=trueThen it shows the list in the ActionBar (looks awefull awe full , but at least you have all keys needed to be translated for an app).But of course this works only for apps.Meaning that the code base would already be there, not that much of backend development needed.So the goal:I can tell the system " * Get me a complete list of all key generated/expected by the system, to copy it manually into a empty message bundle file * ".This would not even need a fancy app. All what the dev needs (minimum thinking) would be a propert proper console out with the list of all empty keys.Nice would be, if I can also target a single configuration.But the real need is to be able to gat get all of a module:I just create my configs, then trigger the list, and can start translating them.This is generally the first thing I get asked in every training, when showing the i18n mechanism:How do I know all concrete keys?Can I get them form the system?Why not, the system knows what it expects?Cheers
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
