Re: [uportal-dev] i18n and l10n files in uportal-impl/src/main/resources/properties/db

[Eric Dalquist]

So I discovered that at least the i18n data for channel definitions is used by the framework and is actually causing problems in the trunk right now as channels are getting published with ids that match data in data-i18n.xml so channels render with incorrect titles and such. I had a short chat with Drew about this yesterday in regards to import/export support for i18n data. I think we both agreed that the appropriate resolution here would be to add support for the xml:lang attribute to the exported entity files in the import and export scripts to allow multiple translations of a string in a single entity file.

-Eric

Eric Dalquist wrote:

This isn't going to make 3.0 though, so for that target I'm planning on cleaning up the i18n related files leaving stubs with commented out data for examples. We can probably schedule the xml:lang support for a 3.0.x release if someone has enough interest in this support to do the work involved.

Does anyone know if the internationalization and localization files in uportal-impl/src/main/resources/properties/db are still usable in the framework? I'm near positive they haven't been maintained and the data loaded by them does not correspond to any of the actual initial channels or layouts. I also know that the recently added import/export scripts do not have any sort of i18n or l10n support.

Any and all insight is welcome,
-Eric

I'm unsure what to do about this lag, should we leave the out-of-date files as examples, remove all but one language to leave as an example?

smime.p7s
Description: S/MIME Cryptographic Signature