You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Thierry Yge (JIRA)" <ji...@apache.org> on 2008/09/30 21:01:47 UTC
[jira] Created: (SLING-686) Change i18n storage structure for less
redundancy
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.
[jira] Issue Comment Edited: (SLING-686) Change i18n storage
structure for less redundancy
Posted by "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.
[jira] Commented: (SLING-686) Change i18n storage structure for
less redundancy
Posted by "Alexander Klimetschek (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (SLING-686) Change i18n storage structure for less
redundancy
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-686.
----------------------------------
Resolution: Won't Fix
> 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.
[jira] Commented: (SLING-686) Change i18n storage structure for
less redundancy
Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SLING-686) Change i18n storage structure for
less redundancy
Posted by "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 ]
Felix Meschberger commented on SLING-686:
-----------------------------------------
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.