[
https://issues.apache.org/jira/browse/SLING-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635838#action_12635838
]
Tobias Bocanegra commented on SLING-686:
----------------------------------------
another drawback of this suggestion is, that you can't export/import just an
entire tree (eg. for let it translate by an external company). also adding a
new language/translation later on results probably in a big mess.
> ... and it would make it more easy to create quickly the different
> translation for a given key.
which in real life is difficult to find a language genius that speaks 4
different languages :-). usually the messages are translated language by
language by the same person.
> Change i18n storage structure for less redundancy
> -------------------------------------------------
>
> Key: SLING-686
> URL: https://issues.apache.org/jira/browse/SLING-686
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Extensions i18n 2.0.2
> Reporter: Thierry Yge
> Priority: Minor
>
> it would be nicer to structure the i18n nodes as follow
> {
> "en": "hi",
> "sling:key": "hi",
> "de": "hallo",
> "jcr:primaryType": "sling:Message",
> "fr": "bonjour",
> "it": "bonjourno"
> }
> This it would avoid so many redundancy as in the actual solution, and it
> would make it more easy to create quickly the different translation for a
> given key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
