Creating a clean .pot file and making a localised version by adding some translations works well. My suspicion is that there is a parsing error in your translation. Need to debug further. Out of curiosity: do you use tooling to edit the translation or are you using a text editor?
On 1 November 2015 at 15:23, Jeroen van der Wal (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/ISIS-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984409#comment-14984409 > ] > > Jeroen van der Wal commented on ISIS-1221: > ------------------------------------------ > > Hi Cesar, thanks for setting up the repo. I will check it out later today. > > > > > > JSON Format Layouts not recognized with i18n translations in Wicket > Viewer > > > -------------------------------------------------------------------------- > > > > Key: ISIS-1221 > > URL: https://issues.apache.org/jira/browse/ISIS-1221 > > Project: Isis > > Issue Type: Bug > > Components: Core: Viewer: Wicket > > Affects Versions: 1.9.0 > > Environment: Windows Server, HSQLDB > > Reporter: Cesar Lugo > > Assignee: Dan Haywood > > > > I am working with Apache Isis Wicket viewer 1.9.0, and I have some form > layout json files to define the layout for some domain objects. I also > added a translation file (i18n) with some translations. When running the > application in the browser, when I am in “writing translations” mode it > shows the object form with the layout defined in the json file (ok), but > when I switch to “reading translations”, it goes back to the “default” > layout, ignoring the layout defined in the json file. > > In regards to those modes, I am referring to the Apache wicket viewer > menu which, in prototype mode, has a "Prototyping" menu, which has an > option "Switch to Reading Translations". When you select that option and > keep using the application is when it loses the layouts defined in the json > layout files. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
