i think it is currently not possible to deploy json-file bases i18n resources with Sling-Initial-Content. as described in [1] the json file node nt:file needs an additional mixin mix:language for the language code. and this is not possible to define with or without ignoreImportProviders=json currently.
i would be also very interested to support i18n json files with Sling-Initial-Content, but i think we have to improve the content loader mechanism for this. stefan [1] https://sling.apache.org/documentation/bundles/internationalization-support-i18n.html#json-file-based >-----Original Message----- >From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] >Sent: Friday, April 28, 2017 9:43 AM >To: users >Subject: Re: Sling pipes release > >On Fri, Apr 28, 2017 at 12:28 AM, Correia ><carlos.manuel.corr...@celfocus.com> wrote: >> ...The "ignoreImportProviders=json" is not a solution because I use JSON >for >> all my content... > >That option is per path, so I suppose if you isolate those .json files >in a specific path that should work - but maybe that prevents you from >creating the structure that the i18n bundle needs? > >Worst case, using a JCR SystemView XML file should work but maybe >that's inconvenient to generate and edit. > >-Bertrand