[jira] Issue Comment Edited: (SLING-686) Change i18n storage structure for less redundancy

["Felix Meschberger (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635818#action_12635818 ] 

fmeschbe edited comment on SLING-686 at 9/30/08 12:29 PM:
-------------------------------------------------------------------

I don't think this is a good idea. For one thing we loose the per-language structuring people have gotten used to. In addition we loose all options to selectively grant access to different language trees to different people.

Thus, unless being convinced with some other arguments, I would not oppose this change.

      was (Author: fmeschbe):
    I don't think this is a good idea. For one thing we loose the per-language structuring people have gotten used to. In addition we loose all options to selectively grant access to different language trees to different people.

Thus, unless being convinced with some other arguments, I would not opt for this change.
  
> 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.