On Feb 8, 5:07 pm, Timothy Perrett <[email protected]> wrote: > Generally I find that to be only of use when needed specific adjustments to > templates. For instance, english vs german... the german language is > significantly more verbose so requires different div heights etc sometimes. > Its not generally a strategy one adopts for their entire localisation scheme. >
We're using the built-in localized template lookup (index_fr.html) in production, and I find it to be better than any alternative I've seen across any web framework. As you noted, most pages aren't actually different, so our build process is scripted to translate index.html to index_fr.html in the target directory. Our source tree isn't cluttered with _fr versions of everything, our templates aren't filled with <loc> or <&|/l&> tags everywhere . . . so far it seems like a win-win to me. Only minor snag we've run into with lift localization was that S.? isn't really parseable by xgettext, so we just used a wrapper function with a different character. To the OP, like David said, try what's there first, chances are it will meet your needs. -- 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.
