Nice to see Fabien replying on the list and so quickly :)
As for the language, when i start tinyerp-client.py from the path
where it resides (./tinyerp-client.py) it works perfectly.
Try to edit the ~/.terprc
One path is probably wrong.
The swedish
po file exists but it is incomplete comparing to the pot file, what i
would like to do is to open the pot file and import all the already
translated strings and then do the rest of them and compile it into
the mo file, how do i do this? I could write a small python script but
i rather not...
There is standard gettext command for this:
updating the .pot file:
xgettext -k_ -kN_ -o bin/po/terp-msg.pot $(PYTHON_FILES) bin/terp.glade
merging the sv.po with the .pot file
msgmerge bin/po/sv.po bin/po/terp-msg.pot -o bin/po/sv.po
Regenerating the .mo file
msgfmt bin/po/sv.po -o bin/po/sv/LC_MESSAGES/terp.mo
See the Makefile which is in the client distribution.
Yesterday I translated the server for about 5 hours,
seems I am on a mission :)
Great, I suggest you to upload your work on the Tiny Forge. So that, we
will package your version at the next release of Tiny ERP.
I found out that when translating the
server now that it is a little different than the docs say, this is
how I did it.
You are right on these steps.
But old requests --i18n-import or --i18n-export are still valid.
1. Start with a clean database: dropdb terp;createdb terp
--encoding=unicode
But you do not need this point as the database is created from the
client interface.
--
Fabien
Tiny ERP - when brains matter more than size
-- George Jacobson, 2005
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users
