[
https://issues.apache.org/jira/browse/SLING-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635873#action_12635873
]
Alexander Klimetschek commented on SLING-686:
---------------------------------------------
I am also against this idea. Translations come and go by language, so you want
a single subtree with the translations for a single language.
BTW, also see SLING-517 for other ideas of improving the i18n node structure.
> 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.
