Hi André, I don't think so. The module_options.php file is located in out/admin/en/ in the module directory, so I think it's used only for the Settings tab in the Admin theme.
If you need to add translations for your module (and be sure that it will be available on front theme), you have to create a language file in out/lang/language_code/ (e.g. modules/module_name/out/lang/fr/mymodule_lang.php ). Best regards, Nicolas Hodin www.takeitweb.fr 2013/2/6 André Herrmann <andre.herrm...@fatchip.de> > Hi Nicolas, > Hi Gernot, > > does this also work for frontend themes? I mean, in most cases the theme > folder is customized so the module cannot rely on having "azure" for > example. Or does the subfolder place not harm the basic functionality of > module_options.php? > > @oxid: Please document the translation options inside a module > configuration somewhere like here: > http://wiki.oxidforge.org/Features/Extension_metadata_file > > Best wishes > > André > > > > On 24.01.2013 17:17, Gernot Payer wrote: > > Hi Nicolas, > > > > thanks a lot, that helped! :) > > > > regards > > Gernot > > > > Am Thu, 24 Jan 2013 15:27:10 +0100 > > schrieb Nicolas Hodin <nho...@noxnet.fr>: > > > >> Hi Gernot, > >> > >> You will find some information on translating module settings on this > >> url : > >> > http://www.oxid-esales.fr/gestion-des-modules-fichier-module_options-php/. > >> Sorry it's french, but you will easily find the main information that > >> you have to create this language file : > >> modules\module_name\out\admin\language_code\module_options.php . > >> > >> Best regards, > >> > >> Nicolas Hodin > >> www.takeitweb.fr > >> > >> > >> 2013/1/24 Gernot Payer <pa...@shoptimax.de> > >> > >>> Hi devs, > >>> > >>> I tried to include module settings into a module via the "settings" > >>> parameter in the metadata.php. > >>> This part worked, however having translated texts for these options > >>> seems to be impossible. > >>> > >>> So far I tried "lang/de/my_module_lang.php", > >>> "out/lang/de/my_module_lang.php" and > >>> "out/admin/de/my_module_lang.php", all inside the > >>> "module/my_module" directory. None of them worked. > >>> Using /views/admin/de/cust_lang.php worked, but that would be bad > >>> style, as you are supposed to put all your module files inside your > >>> module directory. > >>> > >>> Can anyone give me a hint how to do this? > >>> > >>> regards > >>> Gernot > >>> > >>> -- > >>> ******************************************* > >>> Dipl.-Inf. Gernot Payer > >>> Software-Entwickler > >>> > >>> shoptimax GmbH > >>> Guntherstraße 45a > >>> 90461 Nürnberg > >>> Amtsgericht Nürnberg HRB 21703 > >>> GF Friedrich Schreieck > >>> > >>> Tel.: 0911/25566-17 > >>> Fax: 0911/25566-29 > >>> pa...@shoptimax.de > >>> http://www.shoptimax.de > >>> ******************************************* > >>> > >>> _______________________________________________ > >>> dev-general mailing list > >>> dev-general@lists.oxidforge.org > >>> http://dir.gmane.org/gmane.comp.php.oxid.general > > > > > > > -- > > André Gregor-Herrmann > Entwicklung, Administration, Projektmanagement > > mail [ andre.herrm...@fatchip.de ] > > web [ www.fatchip.de ] > > FATCHIP [ GmbH ] | sitz [ Helmholtzstrasse 2-9 | 10587 Berlin ] | fon > [ 030.39 88 93 51 ] | fax [ 030.39 88 93 52 ] | mail [ > kont...@fatchip.de ] | Ust-Id. [ DE 265567757 ] | Amtsgericht [ > Berlin-Charlottenburg ] | HRB [120567 B] | Geschäftsführung [ Dipl.-Ing. > Hendrik Bahr ] > > Be Smart, Go Green. Don’t print this email unless you really need to. > > _______________________________________________ > dev-general mailing list > dev-general@lists.oxidforge.org > http://dir.gmane.org/gmane.comp.php.oxid.general >
_______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
