Hi Corin, That's correct, the form module's dialogs are currently still missing i18n support; essentially, relevant controls of each dialog would need an "i18n" property set to true to fix this.
Best way to go at it would be to write update tasks to add those properties, and update the bootstrap files. If that's enough info to get you started, go ahead and file an issue at http://jira.magnolia-cms.com/browse/MGNLFORM .. patches would be great! ;) We'll try to update http://documentation.magnolia-cms.com/technical-guide/i18n.html shortly in that regard. In the meantime, these blog entries might help get you started: http://philipp-baerfuss-magnolia.blogspot.com/2010/01/i18n-support-in-dialogs-magnolia-43.html http://philipp-baerfuss-magnolia.blogspot.com/2010/02/i18n-authoring-support-on-stage.html .. and if not, shoot back ! ;) Cheers, -greg On Oct 22, 2010, at 14:42, Corin Moss wrote: > > Hi everyone, > > We've been working quite successfuly with the i18n features of Magnolia for > standard content, and we're now looking at how to use it in conjunction with > some of the modules. Case in point at the moment is the form module. It > appears that this module doesn't yet support i18n for the generated form > elements - is this correct, or are we missing something? > > If it indeed doesn't support i18n, we'd be interested in providing that > support. Where should one look for a best practice example? > > Many thanks, > > Corin > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
