Hi! I find l10n solutions somewhat questionable: it seems that they use runtime lookups even for things that could be done in compile time. I'd like to ask you to point me to some readings on this topic if I am missing something.
A very good l10n doc is http://code.bestpractical.com/bps-public/Locale-Maketext-Lexicon/docs/webl10n.html It suggests constructs like these: % $m->print(loc("Another line of text", $args...)); <&|/l, $args...&>Single line of text</&> I am wondering if a different approach would be possible: why don't we hack the mason compiler to compile not just .obj files from the templates, but .en.obj, .fr.obj, .de.obj, ... When a component is to be run, then the appropriate .obj file is taken, and would run the same speed as there were no internationalization would be in place. I know that if a new feature is asked for, it is best to give some code, not just "bright" ideas... I am ok with it, however, before I try to tweak Mason this way, I'd like to ask you if there exists prior art, so I don't reinvent the wheel. Also, I'd like to hear criticism of the idea, because if it is stupid, I'd better not invest too much time in it... Best regards, Baldvin Kovacs ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
