Hi,
if i'm not mistaken, then you can do replacements in language strings like this:
[{"MY_LANGUAGE_VAR"|oxmultilangassign|replace:":count":"5"}]
or if you're using getters:
[{"MY_LANGUAGE_VAR"|oxmultilangassign|replace:":count":$oView->getMyCount()}]
Of course, having the option of passing replacements as smarty parameters would lead to cleaner code in the templates... ;-)
Cheers,
Robert
-----Ursprüngliche Daten-----
Datum: 01.03.2013 11:47:22
Von: Alexander Kludt <[email protected]>
An: <[email protected]>
Betreff: Re: [oxid-dev-general] cleaning OXID eShop translations
Vorgang: T-91WH2OBKBT-56
Datum: 01.03.2013 11:47:22
Von: Alexander Kludt <[email protected]>
An: <[email protected]>
Betreff: Re: [oxid-dev-general] cleaning OXID eShop translations
Vorgang: T-91WH2OBKBT-56
Hi,
+1 for Marat's idea - everytime a customer (shop owner) needs to be able to change language
stuff we need to transform it into a CMS content so he can do that in the backend. Most people
just don't get it how to edit a file through FTP. Sounds like this might be done through oTrance, marco?
--
mit freundlichen Grüßen
Alexander Kludt
__________________________
Phone: 09283-5925453
Fax: 09283-592671
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.
Hello,
+1 for Alexander's idea
and it would be awesome if you could move the lang keys managemet into the database.
Perhaps there would be a table like with lang key, language, default translation and a custom translation, and the languages can be cached into the temp file. It makes the whole translation process and adding custom keys a lot easier, cause the user can simply translate the stuff in backend instead of searching and editing some php lang files.
Greeetz
Marat
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.generalHi there,
Maybe this is already been done, but having parameters inside the translations would make things a lot easier.
Like this:
'MY_LANGUAGE_VAR' => 'You have :count items in your cart'
[{oxmultilang ident="MY_LANGUAGE_VAR" count="5" }]
gives
You have 5 items in your cart
_______________________________________________ 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
