You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2015/03/27 15:27:53 UTC

[jira] [Commented] (SLING-4543) i18n: support for json dictionaries

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

Felix Meschberger commented on SLING-4543:
------------------------------------------

Thanks [~alexander.klimetschek] for the patch. I am going to apply this. Since this looks like new feature I also increased the intended next version to be 2.4.0

> i18n: support for json dictionaries
> -----------------------------------
>
>                 Key: SLING-4543
>                 URL: https://issues.apache.org/jira/browse/SLING-4543
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: i18n 2.3.2
>            Reporter: Alexander Klimetschek
>            Assignee: Felix Meschberger
>             Fix For: i18n 2.4.0
>
>         Attachments: SLING-4543.patch
>
>
> Support json dictionaries as alternative to individual sling:Message nodes.
> The fine grained JCR sling:Message node approach does not scale very well when dictionaries contain thousands of entries, at least installation of such a dictionary is slow, but also reading can be affected (even if this is cached), especially viewing in a tree browser becomes impossible.
> The individual string overlay mechanism (/apps string overlays same /libs string) must still work.
> In our case (AEM) this can save more than a minute during installation time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)