[yast-devel] create translation for a new yast module
Hi all! When creating a new YaST module, how do I create the po and mo files needed for its translation? Is there any tool or I have to create it by hand copying the po file from another module? greetings, -- Jordi Massaguer i Pla openTrends Solucions i Sistemes, S.L. Torre Llacuna C/Llacuna 166, 10º 1ª A 08018 Barcelona Phone: (+34) 93 320 84 14 Fax: (+34) 93 300 35 27 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hi! To make the .po files, just do make pot in the top lever directory of the YaST module. It will create the .pot file(s) according to textdomains present. Then you have to translate them :-) and convert to .mo files via /usr/bin/msgfmt Hope that helps! Jiri Dne Friday 25 of January 2008 14:18:58 Jordi Massaguer Pla napsal(a):
-- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
I've created the YaST module myself and have no makefile at all. Actually what I've done is write a ycp module and compile it by "ycpc -c" . How do I create the makefile? Is there a template? thanks El dv 25 de 01 del 2008 a les 15:32 +0100, en/na Jiri Srain va escriure:
-- Jordi Massaguer i Pla openTrends Solucions i Sistemes, S.L. Torre Llacuna C/Llacuna 166, 10º 1ª A 08018 Barcelona Phone: (+34) 93 320 84 14 Fax: (+34) 93 300 35 27 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dne Monday 28 January 2008 15:36:02 Jordi Massaguer Pla napsal(a):
In that case, you may want to use 'y2tool y2makepot' utility (from have yast2-devtools package). It (recursively) collects all *.ycp and afaik also *.pm files and several others in the current directory and creates appropriate *.pot files for each textdomain found in these files. However, it has some limitations (see bug #354678), so you may want to specify the exact files you want to collect the strings from by creating POTFILES plain text file in your working directory. POTFILES should contain (relative) paths to ycp files with translatable strings, one per line. Hope I did not confuse you very much ;-) B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
Hi! To make the .po files, just do make pot in the top lever directory of the YaST module. It will create the .pot file(s) according to textdomains present. Then you have to translate them :-) and convert to .mo files via /usr/bin/msgfmt Hope that helps! Jiri Dne Friday 25 of January 2008 14:18:58 Jordi Massaguer Pla napsal(a):
-- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
I've created the YaST module myself and have no makefile at all. Actually what I've done is write a ycp module and compile it by "ycpc -c" . How do I create the makefile? Is there a template? thanks El dv 25 de 01 del 2008 a les 15:32 +0100, en/na Jiri Srain va escriure:
-- Jordi Massaguer i Pla openTrends Solucions i Sistemes, S.L. Torre Llacuna C/Llacuna 166, 10º 1ª A 08018 Barcelona Phone: (+34) 93 320 84 14 Fax: (+34) 93 300 35 27 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dne Monday 28 January 2008 15:36:02 Jordi Massaguer Pla napsal(a):
In that case, you may want to use 'y2tool y2makepot' utility (from have yast2-devtools package). It (recursively) collects all *.ycp and afaik also *.pm files and several others in the current directory and creates appropriate *.pot files for each textdomain found in these files. However, it has some limitations (see bug #354678), so you may want to specify the exact files you want to collect the strings from by creating POTFILES plain text file in your working directory. POTFILES should contain (relative) paths to ycp files with translatable strings, one per line. Hope I did not confuse you very much ;-) B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
participants (3)
-
Jiri Srain -
Jordi Massaguer Pla -
Katarina Machalkova