Hi, alright, baptism of fire. Shall we put it to feature request list like bespoken before? Not to forget [code improvement] beforehand the subject ;)
Regards Marco -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Alexander Kludt Gesendet: Freitag, 22. Oktober 2010 15:39 An: [email protected] Betreff: Re: [oxid-dev-general] Problem with translation of phrasesin differentlanguages Feature request is nice, but please consider multiple params in one string -- mit freundlichen Grüßen Alexander Kludt __________________________ Phone: 09283-5925453 Skype: kingschnulli Email: [email protected] Website: www.aggrosoft.de __________________________ Aggrosoft it intelligence GbR Tannstrasse 12 95111 Rehau GERMANY Sitz Rehau, Amtsgericht Hof Steuernummer: 223/165/54508 Ust.-Id. Nr. gemäß § 27 a Umsatzsteuergesetz: DE260722773 ___________________________ Diese Nachricht ist nur für den Empfänger () bestimmt, sollten Sie nicht der Empfänger sein löschen Sie diese Nachricht umgehend und geben Sie uns bitte per Email ([email protected]) Bescheid über den fälschlichen Erhalt. Sarunas Valaskevicius schrieb: > Hi, > > this is a good idea and we will consider it, currently there is no > such functionality implemented. > > Regards, > Sarunas > > > ----- Original Message ----- From: <[email protected]> > To: <[email protected]> > Sent: Friday, October 22, 2010 2:48 PM > Subject: [oxid-dev-general] Problem with translation of phrases in > differentlanguages > > >> Hello developers! >> We are currently trying to add another language to the shop. >> There we have the following problem: >> >> Let's say in English the text is >> "Only in packaging units of 5" >> >> Now we have the translation in lang.php >> 'BASKET_VPE_MESSAGE' => "Only in >> packaging units of ", >> >> The code in the template: >> [{ oxmultilang ident="BASKET_VPE_MESSAGE" }] [{ >> $basketproduct->oxarticles__oxvpe->value}] >> >> Now we have a new language were the sentence is created in a >> different way, so that after the "5" there has to be text as well: >> "This item can only be bought in packaging units that contain 5 items." >> (I used English, not the original new language just for explanation) >> Now you would need something like [{ oxmultilang >> ident="BASKET_VPE_MESSAGE1" }] [{ >> $basketproduct->oxarticles__oxvpe->value}] [{ oxmultilang >> ident="BASKET_VPE_MESSAGE2" }] in the template and the corresponding >> entries in lang.php. >> It is quite some work to modify all the places where this issue >> occurs (change the templates and add the 2nd entry to all language >> files). >> >> What do you think about an extended oxmultilang modifier in smarty >> that can also work with additional attributes? >> Place holders in the multilang string would be replace by these >> attributes. >> Something like: >> >> [{ oxmultilang ident="BASKET_VPE_MESSAGE" >> value="$basketproduct->oxarticles__oxvpe->value" }] (in the tpl) >> >> 'BASKET_VPE_MESSAGE' => "Only in >> packaging units of %s", >> 'BASKET_VPE_MESSAGE' => "This item can >> only be bought in packaging units that contain %s items." >> (in lang.php) >> >> I know this could be achieved somehow with the smarty modifier >> "string_format" as well. >> But I like my idea more ;-) >> >> Is there maybe something like this in the new template system that is >> announced for 4.5.0? >> If yes, it would be great to have this code already now so that I >> could implement it myself for older releases. >> >> Regards, >> Martin >> >> >> >> _______________________________________________ >> 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 _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
