Mark, first of all, thank you for a wonderful piece of expirience! Your way of separating things definitely worth attention. I'm going to try it for my next i18n-enabled project.
One little thing I'd like to mention. Let us all use full locale names instead of ISO language codes. de_DE.ISO8859-1 or en_US.ASCII may seem a little too verbose, but in addition to language code they contain country code (which may or may not be useful) and charset name (which is VERY useful). So that one could create and use, e.g. both ru_RU.KOI8-R and ru_RU.CP1251 set of internationalized items. Alas, the world is more complex with CJK encodings and customers over there will appreciate it even more than russians. * Mark A. Fuller <[EMAIL PROTECTED]> [August 24 2004, 21:43]: > I understand what he's saying. When initially facing the chore of > international language support, it's perplexing how to balance > between language specific templates, replaceable text, and some > replaceable text which is pull-down values you'd more naturally > consider to be part of the template. [skip] -- Alex Kapranoff. ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Html-template-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/html-template-users
