Hi,
I would like to propose the following changes: * Do Not use language keys like x_BEFORE and x_AFTER. They are very hard to translate. Instead use a variable System like Alexander proposed. But use named variables instead of Position dependend keys since different languages use other ordering * Using the database for translations would be nice, but Keep the File mechanism for overwriting database translations for develompent purposes * Do Not include colons in the templates, instead Keep them in the language keys. In french for example you place a space in front of a colon. If the colons are in the templates, we would have to maintain a whitespace at the end of some translations -- ooxi Violetland — An open source cross-platform game similar to Crimsonland — http://violetland.github.com Tadas Rimkus <[email protected]> schrieb: > >Hello everyone, > >We are working on OXID eShop translations. We are optimizing language >constants: removing duplicates, removing colons ':' from constants. Colons >will be placed in template files. Also, mapped constants will be replaced with >generic ones. > >Is there any other suggestions we could use to improve multi language handling >? > > >Tadas Rimkus >Software Developer > >[email protected]<mailto:[email protected]> >Fon +49 761 36889-0 >Fax +49 761 36889-29 >www.oxid-esales.com<http://www.oxid-esales.com?campaign=emailsignatur/oxid-esales-com> > > > > >_______________________________________________ >dev-general mailing list >[email protected] >http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
