[mkgmap-dev] mixed index branch merge

Sat Feb 14 14:57:21 GMT 2015

What about multi-lingual countries such as Belgium or Switzerland? I
think the primary factor should be language, not country. Belgian
French, French French and Swiss French are probably similar enough for
these purposes that they can share a solution. But Belgian French and
Belgian Dutch are completely different animals.... 

Of course you can try to map countries (or at least a generic area like
"territories") to default languages, but the user may still want to
override the default. 

How about this (sorry the abbreviations are wrong but it is only to
illustrate my point): 

mkgmap:country=POL {set mkgmap:lang=polish;} 

mkgmap:region=Vlaanderen {set mkgmap:lang=dutch;} 

mkgmap:country=NED {set mkgmap:lang=dutch;} 

mkgmap:region=Wallonie {set mkgmap:lang=french;} 

mkgmap:country=FRA {set mkgmap:lang=french;} 

mkgmap:lang=french {set mkgmap:stopwords="rue,place,..."} 

mkgmap:lang=dutch {set mkgmap:stopwords="de,het,..."} 

mkgmap:lang=polish {set mkgmap:stopwords="ulica;ul."} 

If the stopwords were also defined to be regular expressions, then it
could also handle prefixes and suffixes as well as whole words. 

On 2015-02-14 15:38, Andrzej Popowski wrote: 

> Hi,
> 
> in my opinion stopwords sholud be dependent on country code and should be defined in style or in definition of local parameters, the same way like zip code before street name.
> 
> Style would be preferred, since definitions can be included in default style, where contribute many people. Probably we could get definitions for many countries quite fast. I think it could be something like:
> 
> mkgmap:country=POL {set mkgmap:stopwords='ulica;ul.'}
> 
> Looking for solution, please take in consideration maps, which include many countries at once.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150214/39d028ce/attachment-0001.html>