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
