There is of course many tools, mostly Babel, to translate the interface and the message strings that live in the python vivarium. A good documentation can be found on the pylon website.
More difficult is to manage the i18n of the content of the RDBMS.
werner, on the sqlalchemy mailing list pointed me to an old thread regarding a discussion about dynamic_loader.
He also sent me links to a blog with a lot of thoughts about my problem.
- http://rwec.co.uk/blog/2009/11/atomic-translations-part-1/
- http://rwec.co.uk/blog/2009/12/atomic-translations-part-2/
Graham Higgins had derived the versioning extension of elixir and modified it to implement a concept of Local content. He shared his code, but it failed to pass its tests, elixir had moved up from 0.4 to 0.7. So I took upon me to rewrite this component and make it work, it is now available as an elixir extension.
It is hosted on google code and you can easily check out a copy.
Hi,
ReplyDeleteI have to implement i18n of content in one of my sites. Looking for python solutions i stumbled upon your one.
I am storing rather large strings which need to be translated, so the question is if there's a big performance hit when searching.
Sorry, I missed another question: did you benchmark it?
ReplyDeleteHi, I'm sorry I haven't seen your comments before. Actually no, I haven't benchmarked it. If you have some feedback regarding the code performance, or any suggestions to improve it, please do not hesitate.
ReplyDelete