Hi all, we've already done moving translations from lang files to DB. We have need it for an easy way to translate and find strings, and its easier ;).I have to admit that we dont have handle the problem for new lang files that comes by modules, because we dont need it. For our own modules we make now a sql insert instead of writing a lang file. Of course, its not the final or best solution but enough at the moment.
Another reason why we made a module for the lang handling is that we need to do replacements for strings thats depending on active shop and active lang and we dont want to write the stuff into the TPL files like you can allready do(with '%1s' ) because you have to handle all these placeholders in the tpl and if they changed you have to change all of the tpl files. So we write a functions thats replacing the our placeholder on langcache generation not at first by using them in the tpl. It would be nice if there are a possibility to make replacement by langcache file generation for values that are depending on active shop and active lang because you dont have to handle that in the tpl files anymore. For example we replacing Shopnames and Shopurls. (that are in the middle of a sentence) Maybe no one other will need a function like these, but we allready use it ;). 2013/3/1 Tadas Rimkus <[email protected]> > ** ** > > 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]* > 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
