Re: [Maposmatic-dev] Document mo file generation from the po files in INSTALL
Hello Florian, 2013/10/14 Florian Lohoff f...@zz.de: maposmatic@osmdb:~/ocitysmap$ grep i18n INSTALL | wc -l 0 I agree. So make it this: commit 206dcdcb89f5455f18b158258e1f0a07d0cad0e2 Author: Florian Lohoff f...@zz.de Date: Mon Oct 14 07:48:40 2013 + Document running the i18n.py for localization diff --git a/INSTALL b/INSTALL index 237e436..04bea05 100644 --- a/INSTALL +++ b/INSTALL @@ -266,6 +266,15 @@ are using. They have been tested on several x86_64 hosts. Create a ~/.ocitysmap.conf configuration file, modeled after the provided ocitysmap.conf.dist file. +e. Localization + +run + + ./i18n.py -m + +to create the ocitysmap.mo files for localization of e.g. the index. And add sentence: Please see I18N file for further details. Can somebody commit the above patch? (I can't) Best regards, david
Re: [Maposmatic-dev] Document mo file generation from the po files in INSTALL
Hello Florian, 2013/10/9 Florian Lohoff f...@zz.de: this is my way how i generated the mo files from the po files. There might be a simpler way - just document it in the INSTALL file. Hmm, you'd probably better use i18n.py script, which *is* documented: ;-) http://git.savannah.gnu.org/cgit/maposmatic/ocitysmap.git/tree/I18N Best regards, david
Re: [Maposmatic-dev] Document mo file generation from the po files in INSTALL
On Mon, Oct 14, 2013 at 09:43:46AM +0200, David MENTRE wrote: Hello Florian, 2013/10/9 Florian Lohoff f...@zz.de: this is my way how i generated the mo files from the po files. There might be a simpler way - just document it in the INSTALL file. Hmm, you'd probably better use i18n.py script, which *is* documented: ;-) http://git.savannah.gnu.org/cgit/maposmatic/ocitysmap.git/tree/I18N maposmatic@osmdb:~/ocitysmap$ grep i18n INSTALL | wc -l 0 So make it this: commit 206dcdcb89f5455f18b158258e1f0a07d0cad0e2 Author: Florian Lohoff f...@zz.de Date: Mon Oct 14 07:48:40 2013 + Document running the i18n.py for localization diff --git a/INSTALL b/INSTALL index 237e436..04bea05 100644 --- a/INSTALL +++ b/INSTALL @@ -266,6 +266,15 @@ are using. They have been tested on several x86_64 hosts. Create a ~/.ocitysmap.conf configuration file, modeled after the provided ocitysmap.conf.dist file. +e. Localization + +run + + ./i18n.py -m + +to create the ocitysmap.mo files for localization of e.g. the index. + + 12. Run OCitySMap ./render.py -t Ceci n'est pas Paris --osmid=-411354 # Contern, LU Flo -- Florian Lohoff f...@zz.de signature.asc Description: Digital signature
Re: [Maposmatic-dev] Document mo file generation from the po files in INSTALL
Hi Florian, Good thinking in documenting this. Perhaps it can be simplified further by using msgfmt's -o/--output-file option to directly write ocitysmap.mo? Cheers, Jeroen On Wed, Oct 9, 2013 at 7:45 PM, Florian Lohoff f...@zz.de wrote: Hi, this is my way how i generated the mo files from the po files. There might be a simpler way - just document it in the INSTALL file. Took me a while to find this. commit 17281de7c5586cd420e19f2400ab7dd26f69142a Author: Florian Lohoff f...@zz.de Date: Wed Oct 9 17:42:29 2013 + Add mo file generation from the po files to INSTALL diff --git a/INSTALL b/INSTALL index 237e436..8802714 100644 --- a/INSTALL +++ b/INSTALL @@ -266,6 +266,18 @@ are using. They have been tested on several x86_64 hosts. Create a ~/.ocitysmap.conf configuration file, modeled after the provided ocitysmap.conf.dist file. +e. Create mo files from po files + +Install the package + +sudo aptitude install gettext + +and then run the following command in the ocitysmap folder + +for i in locale/*/LC_MESSAGES; do ( cd $i ; msgfmt ocitysmap.po ; mv messages.mo ocitysmap.mo ); done + +to create the necessary mo files from the po file translations + 12. Run OCitySMap ./render.py -t Ceci n'est pas Paris --osmid=-411354 # Contern, LU -- Florian Lohoff f...@zz.de -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIVAwUBUlWWPpDdQSDLCfIvAQgX8A//S8hb3vxsLux8uMns1ZiDR/W6J8RW86tv scU105x7R9tHhYrVYWUCtHk708EqU+eSAW/QdwQKa1FZo22gkjqkAIDDuDWqu4t7 vzCIDnUTtxrO91Mn9UwJlUdpkxFXB4xZwVmGLeI2M9gSHHNuDhxd3H2+TfEwUWPw 3fA3+j9cd+iaeEmhwqf5popOxqvTmE6zE/fI1BWw7S3GujfCFhdNT86DTutPapt7 v+xU/wSM4ADnIgiPgFHRUFZcau/InyQ/XkW7OcYr+sAMbFaa7x/canfaLoo8XM2k WtBcIA8L6oFtweKjbkT6yN2ThoUv52xyr5vOKJAkxklyPCePMGONMsMTzVaPgypW gsk1qoO4La/TIr+GaXoNPlM/8RHC8ZgTqO4oR4T8LK5dhQ5lLEuhxk0taldUTfDA 4Sv1hOzI+x7IYi0q28F0ylVtpj+4yBFCVRIgcQDmTWr+3u2zriUyYjnhiRVBPko2 eGt/752dWi+cXjnV+T7YlGoKMXrkH/V8jCpG3oKx1IYSvxoEOEW5N7LmMqXR2nKG w6DMOkvBT27z6iKAJxDg0cYr37ycn6au6Aw5rEoKDzYvbImhz5sr5HQNVGZIkm57 QjkN69qCS7UXF22eKJnjOyuKkSKIuHS7eZylZJo0ECb1/oNcczOFlItEuIMWSFlo w4y7wbM4cSs= =EjkE -END PGP SIGNATURE- -- ↑↑↓↓←→←→BA[Start]
Re: [Maposmatic-dev] Document mo file generation from the po files in INSTALL
On Wed, Oct 09, 2013 at 07:49:25PM +0200, Jeroen van Rijn wrote: Hi Florian, Good thinking in documenting this. Perhaps it can be simplified further by using msgfmt's -o/--output-file option to directly write ocitysmap.mo? grmpf - i looked at the manpages 20 Times now but overlooked that :) So make it this: commit 17ef46089138996acecac323dfca8d26ce7d99a0 Author: Florian Lohoff f...@zz.de Date: Wed Oct 9 17:52:13 2013 + Add mo file generation from the po files to INSTALL diff --git a/INSTALL b/INSTALL index 237e436..6b213ee 100644 --- a/INSTALL +++ b/INSTALL @@ -266,6 +266,18 @@ are using. They have been tested on several x86_64 hosts. Create a ~/.ocitysmap.conf configuration file, modeled after the provided ocitysmap.conf.dist file. +e. Create mo files from po files + +Install the package + +sudo aptitude install gettext + +and then run the following command in the ocitysmap folder + +for i in locale/*/LC_MESSAGES; do msgfmt $i/ocitysmap.po -o $i/ocitysmap.mo; done + +to create the necessary mo files from the po file translations + 12. Run OCitySMap ./render.py -t Ceci n'est pas Paris --osmid=-411354 # Contern, LU -- Florian Lohoff f...@zz.de signature.asc Description: Digital signature
