1. Export DB translated strings into new properties files (one per locale as is standard) 2. Export DB translated strings and merge them into the existing translation properties files (again one per locale)
I haven't really had any thoughts about the best way to actually implement this. In uP4 we added the up-shell ant target which can run groovy scripts with all of the beans from the uPortal ApplicationContext, this is how the db-* and data-* ant tasks work now. So following in that vein a utility bean could be created to handle these operations (give it the export type, dest dir as arguments) and it would handle the export or export & merge.
I'm not thinking that there is a need to import messages into the DB as you would be able to just use your exported DB message data as your new flat message files.
-Eric On 10/17/11 1:30 PM, Eric Dalquist wrote:
Just had a chance to look at the translator portlet, it looks great my only comments are:1. Move the portlet JS into it's own file in uportal-war/src/main/webapp/media/skins/universality/common/javascript then add that file to uportal-war/src/main/webapp/media/skins/universality/common/common_skin.xml 2. Move the portlet CSS into uportal-war/src/main/webapp/media/skins/universality/common/css/portlet.css Other than that the changes look great! -Eric On 10/05/2011 06:46 AM, Arvīds Grabovskis wrote:Hi,Yesterday on IRC there was a little conversation about Translator portlet that would enable database entity translation. I've created a very simple wireframe of a portlet and attaching it to email. Everything is intended to be loaded by AJAX - by selecting entity type to translate, appropriate values to translate will be loaded. For example, if one selects portlet definition to translate, then all portlet definitions will be loaded into list and upon clicking each portlet, translation form will be enabled.If entities can be added (like in case with message keys), then additional creation form will be available.Currently i see only two entity types to be translated - portlet definitions and messages (see https://issues.jasig.org/browse/UP-3097). In future groups and layout structure elements can be added.I'd love to hear your thoughts about it. -- Arvīds -- You are currently subscribed [email protected] as:[email protected] To unsubscribe, change settings or access archives, seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev
smime.p7s
Description: S/MIME Cryptographic Signature
