On Feb 10, 12:11 pm, Hugo Palma <[email protected]> wrote: > I'm not sure i understand your solution, so your build process find an > index.html and replaces all the text there to all the languages and creates > the appropriate index_<lang>.html file ?
Yes May seem like a hack, but on the other hand I honestly don't understand how people deal with mostly textual websites that consist of templates with nothing but e.g. <wicket:message key="foo"> all over the place. Webapps with a limited amount of text, sure, but making up new property keys for every paragraph. . .are you serious? > If so, where do you keep the translated text at dev time ? Is it still on > resource bundles ? > Yes, translated text is in resource bundles, used by the script that does the xml translation (well, we keep a .po version as well as the java properties file, because of existing gettext toolchain, but that's incidental) -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
