How to localize ui-components
Locked
 
|
Hi
How do I localize ui-component's buttons? Example "today"-button in calendar, "close" button in help-dialog, etc? I can localize xforms document content using xslt but default components remain unlocalized. |
Re: How to localize ui-components
|
|
Mauno,
We have a thread about this here: http://www.nabble.com/Customize---Traslate-the-pop-up-calendar-to11348487.html Let us know if this helps or not. Regarding the help panel: this is defined in a file called help- panel.xml stored in orbeon-resources-private.jar. If you have only one language, then you can override that file by copying it into RESOURCES/ config/help-panel.xml and then change the language. I entered a bug to track this: http://forge.objectweb.org/tracker/index.php?func=detail&aid=308170&group_id=168&atid=350207 In the longer term we will need an easier solution for these two cases. -Erik On Jan 2, 2008, at 8:57 AM, Mauno wrote: > > Hi > > How do I localize ui-component's buttons? Example "today"-button in > calendar, "close" button in help-dialog, etc? > I can localize xforms document content using xslt but default > components > remain unlocalized. > -- > View this message in context: http://www.nabble.com/How-to-localize-ui-components-tp14574813p14574813.html > Sent from the ObjectWeb OPS - Users mailing list archive at > Nabble.com. Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
|
|
Thanks Erik for quick reply.
I've to internationalize few forms for 3 languages. Are there any plans on implementing support for multiple languages?
|
Re: How to localize ui-components
|
Administrator
|
Mauno,
We don't have super-immediate plans to address this, but any help is welcome. The first thing would be to figure out the best way to implement the feature. At this point, we don't have cases with this kind of localization, as forms handle their localization themselves by storing their resources in an XML instance. What we have here is slightly different as we are talking about "components" (help panel, calendar) which are not themselves written in XForms and somehow need to know what language to use. One approach would be for these "components" to honor the xml:lang attribute. But then this would make it hard to switch the language. If this is done, then it would be fairly easy for the calendar I think. For the help panel, it's slightly harder, as we would need to XInclude a different file depending on the language. Then arises the question of what to do if the file doesn't exist. Any thoughts on this? -Erik On Jan 4, 2008, at 9:27 AM, Mauno wrote: > > Thanks Erik for quick reply. > > I've to internationalize few forms for 3 languages. Are there any > plans on > implementing support for multiple languages? > > > Erik Bruchez-3 wrote: >> >> Mauno, >> >> We have a thread about this here: >> >> >> http://www.nabble.com/Customize---Traslate-the-pop-up-calendar-to11348487.html >> >> Let us know if this helps or not. >> >> Regarding the help panel: this is defined in a file called help- >> panel.xml stored in orbeon-resources-private.jar. If you have only >> one >> language, then you can override that file by copying it into >> RESOURCES/ >> config/help-panel.xml and then change the language. >> >> I entered a bug to track this: >> >> >> http://forge.objectweb.org/tracker/index.php?func=detail&aid=308170&group_id=168&atid=350207 >> >> In the longer term we will need an easier solution for these two >> cases. >> >> -Erik >> >> On Jan 2, 2008, at 8:57 AM, Mauno wrote: >> >>> >>> Hi >>> >>> How do I localize ui-component's buttons? Example "today"-button in >>> calendar, "close" button in help-dialog, etc? >>> I can localize xforms document content using xslt but default >>> components >>> remain unlocalized. >>> -- >>> View this message in context: >>> http://www.nabble.com/How-to-localize-ui-components-tp14574813p14574813.html >>> Sent from the ObjectWeb OPS - Users mailing list archive at >>> Nabble.com. >> >> -- >> Orbeon Forms - Web Forms for the Enterprise Done the Right Way >> http://www.orbeon.com/ >> >> >> >> -- >> You receive this message as a subscriber of the [hidden email] >> mailing >> list. >> To unsubscribe: mailto:[hidden email] >> For general help: mailto:[hidden email]?subject=help >> OW2 mailing lists service home page: http://www.ow2.org/wws >> >> > > -- > View this message in context: http://www.nabble.com/How-to-localize-ui-components-tp14574813p14612495.html > Sent from the ObjectWeb OPS - Users mailing list archive at > Nabble.com. > > > -- > You receive this message as a subscriber of the [hidden email] > mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
|
|
Ok.
For me, it'd be enough it "components" locale would be set by http-request's language on server side without any xforms changes. Although this causes situations where xforms content might differ from language that user's browser uses. I suspect this isn't big issue since user is already familiar with browser's language and has got used to similiar behavior example: html-page and file-upload being with different language. Using xml:lang sound very good to me. Could localization still be done java-server-side without any XInclude's or other forms changes? Missing property file's for some locale would be handled by orbeon.
|
«
Return to Orbeon Forms community mailing list
|
1 view|%1 views
| Free forum by Nabble | Edit this page |