[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Maposmatic-dev] MapOSMatic i18n workflow?

From: Jeroen van Rijn
Subject: Re: [Maposmatic-dev] MapOSMatic i18n workflow?
Date: Wed, 6 Nov 2013 17:07:00 +0100

Hi David,

The language specific index code might be nice to mention as well. In short it uses language specific regexes to split the street name into parts.

In Dutch for example you have lots of prefixed surnames which find their way into streets, and you'd want a 'van der Plankstraat' to be indexed under P, not V. That's what the indexer takes care of, because the rules/habits for that differ between localities. Using a Dutch map with English-style indexing would be very confusing for a Dutchman to use, because you'd keep looking up streets under the 'wrong' letter.


On Wed, Nov 6, 2013 at 4:17 PM, David MENTRE <address@hidden> wrote:

I will do a small presentation on MapOSMatic internationalization next
week[1]. I would like to talk about our code but also our
infrastructure and workflow using Transifex. Could someone refresh my
mind on that side?

As far as I remember :
 - we have strings to internationalize in ocitysmap (back-end) and
maposmatic (web front-end) modules;

 - we use language specific Python code for index generation;

 - through Django, we generate PO files, one for each module and
language. We use home made script file for that;

 - those PO files are uploaded to transifex (automatically?);

 - translated PO files are downloaded from transifex (automatically?)
and integrated (how?) into our dev git tree (which one exactly)?

 - the dev git tree is pushed on for tests and
sometimes merged into for word consumption.

Has anybody any stats on our i18n effort, like number and extent of
supported languages?

Best regards,



reply via email to

[Prev in Thread] Current Thread [Next in Thread]