Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work

2023-03-02 Thread Vadim Karpov

Hi
 
I did a search for the word " CONTOUR " in the file  MPCTypes.txt .
In addition to the types mentioned above, there are several more:
 
0x10105 =Marine Lines/MARINE_CONTOUR_LINE/Marine contour line/Non NT, NT
0x10301 =Isobath Area Outlines/ISOBATH_DEPTH_CONTOUR/Depth contour/Non NT, NT
 
0x10900 =Contour Lines/MINOR_CONTOUR(NT)/Minor land-based contour line/NT
0x10901 =Contour Lines/INT_CONTOUR(NT)/Intermediate contour (should be used for 
about every 5th contour line)/NT
0x10902 =Contour Lines/MAJOR_CONTOUR(NT)/Major contour (should be used for 
about every 10th contour line)/NT
0x10903 =Contour Lines/MINOR_BATHY_CONTOUR(NT)/Minor bathymetric, or depth, 
contour/NT
0x10904 =Contour Lines/INT_BATHY_CONTOUR(NT)/Intermediate bathymetric, or 
depth, contour (should be used for about every 5th contour line)/NT
0x10905 =Contour Lines/MAJOR_BATHY_CONTOUR(NT)/Major bathymetric, or depth, 
contour (should be used for about every 10th contour line)/NT
 
The first two types ( 0x10105 and 0x10301 ) seem to be string types.
But the rest of the types ( 0x10900 … 0x10905 ) are numeric and affected by the 
same subject problem :(
  PS: I haven't tested the new build yet.
 
>
>Четверг, 2 марта 2023, 18:01 +03:00 от Gerd Petermann 
>:
> 
>Hi all,
>
>OK, I see no problems to change this method in GType.java:
>public static boolean isContourLine(MapLine line) {
>return line.getType() >= 0x20 && line.getType() <= 0x22 && 
>!(line instanceof MapShape);
>}
>
>All I have to do is to change 0x22 to 0x25, right?
>
>Gerd
>
>
>Von: mkgmap-dev < mkgmap-dev-boun...@lists.mkgmap.org.uk > im Auftrag von 
>Vadim Karpov < bom...@mail.ru >
>Gesendet: Donnerstag, 2. März 2023 14:38
>An:  mkgmap-dev@lists.mkgmap.org.uk
>Betreff: Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP 
>files does not work
>
>Hi
>
>Yes.
>
>Types 0x23.0x24.0x25 are used to create bathymetric maps.
>
>Information from the MPCTypes.txt file (TypViewer application):
>
>0x02000=Contour Lines/MINOR_CONTOUR/Minor land-based contour line/Non NT
>0x02100=Contour Lines/INT_CONTOUR/Intermediate contour (should be used for 
>about every 5th contour line)/Non NT
>0x02200=Contour Lines/MAJOR_CONTOUR/Major contour (should be used for about 
>every 10th contour line)/Non NT
>
>0x02300=Contour Lines/MINOR_BATHY_CONTOUR/Minor bathymetric, or depth, 
>contour/Non NT
>0x02400=Contour Lines/INT_BATHY_CONTOUR/Intermediate bathymetric, or depth, 
>contour (should be used for about every 5th contour line)/Non NT
>0x02500=Contour Lines/MAJOR_BATHY_CONTOUR/Major bathymetric, or depth, contour 
>(should be used for about every 10th contour line)/Non NT
>
>Четверг, 2 марта 2023, 12:01 +03:00 от Ticker Berkin < rwb-mkg...@jagit.co.uk 
>>:
>
>Hi
>
>My understanding of the default Garmin usage is that
> 0x20..0x22 are land/height contours (Minor to Major)
> 0x23..0x25 are sea/depth " "
>
>Ticker
>
>On Thu, 2023-03-02 at 08:52 +, Gerd Petermann wrote:
>> Hi Vadim,
>>
>> I see code in mkgmap to handle the statement with Elevation=m or
>> Elevation=M, but it is only used for the line types 0x20 .. 0x22.
>> Do you have a good reason to use line type 0x25 instead?
>>
>> Gerd
>>
>>
>> 
>> Von: mkgmap-dev > /compose?To=mkgmap%2ddev%2dboun...@lists.mkgmap.org.uk >> im Auftrag
>> von Vadim Karpov >
>> Gesendet: Mittwoch, 1. März 2023 13:00
>> An: mkgmap-dev@lists.mkgmap.org.uk< 
>> /compose?To=mkgmap%2d...@lists.mkgmap.org.uk >
>> Betreff: [mkgmap-dev] The "Elevation=M" in the header of the polish
>> .MP files does not work
>>
>> Good afternoon !
>>
>> I am using the latest version of MkGMap and trying to create a depth
>> chart with isolines (types 0x24, 0x25).
>>
>> The problem is that the compiler interprets the depth specified in
>> Meters as in Feet.
>> The result is independent of the presence or value of the
>> "Elevation=M" parameter.
>>
>> And I didn't find an alternative command line option. :(
>>
>> So how can I tell the compiler to treat all numerical depth and
>> height values in an .MP file as meters and not feet?
>>
>> Thanks for the advice.
>>
>> PS: cGpsMapper works fine with "Elevation=M" of course.
>> PPS: Example of polylyne defs:
>>
>> [POLYLINE]
>> Type=0x02500
>> Label=21
>> EndLevel=3
>> Data0=(47.13926351703,-122.560520313), ...
>> [END]
>>
>> [POLYLINE]
>> Type=0x02500
>> Label=12
>> EndLevel=3
>> Data0=(47.12784640003,-122.562501059), ...
>> [END]
>>
>> --
>> Vadim Karpov
>> ___
>> mkgmap-dev mailing list
>> mkgmap-dev@lists.mkgmap.org.uk< /compose?To=mkgmap%2d...@lists.mkgmap.org.uk 
>> >
>>  https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>--
>Vadim Karpov
>Отправлено из Почты Mail.ru
> 
 
--
Vadim Karpov
 ___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk

[mkgmap-dev] Commit r4906: Treat also line types 0x23..0x25 as contour lines in method isContourLine()

2023-03-02 Thread svn commit
Version mkgmap-r4906 was committed by gerd on Thu, 02 Mar 2023

Treat also line types 0x23..0x25 as contour lines in method isContourLine() 


http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4906
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work

2023-03-02 Thread Ticker Berkin
Hi Gerd

Change looks good. I've forgotten why contours have different
RoundCoordsFilter but these line-types will now be included in this
behaviour.

Ticker

On Thu, 2023-03-02 at 15:01 +, Gerd Petermann wrote:
> Hi all,
> 
> OK, I see no problems to change this method  in GType.java:
>     public static boolean isContourLine(MapLine line) {
>     return line.getType() >= 0x20 && line.getType() <=
> 0x22 && !(line instanceof MapShape);
>     }
> 
> All I have to do is to change 0x22 to 0x25, right?
> 
> Gerd
> 
> 
> Von: mkgmap-dev  im Auftrag
> von Vadim Karpov 
> Gesendet: Donnerstag, 2. März 2023 14:38
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] The "Elevation=M" in the header of the
> polish .MP files does not work
> 
> Hi
> 
> Yes.
> 
> Types 0x23.0x24.0x25 are used to create bathymetric maps.
> 
> Information from the MPCTypes.txt file (TypViewer application):
> 
> 0x02000=Contour Lines/MINOR_CONTOUR/Minor land-based contour line/Non
> NT
> 0x02100=Contour Lines/INT_CONTOUR/Intermediate contour (should be
> used for about every 5th contour line)/Non NT
> 0x02200=Contour Lines/MAJOR_CONTOUR/Major contour (should be used for
> about every 10th contour line)/Non NT
> 
> 0x02300=Contour Lines/MINOR_BATHY_CONTOUR/Minor bathymetric, or
> depth, contour/Non NT
> 0x02400=Contour Lines/INT_BATHY_CONTOUR/Intermediate bathymetric, or
> depth, contour (should be used for about every 5th contour line)/Non
> NT
> 0x02500=Contour Lines/MAJOR_BATHY_CONTOUR/Major bathymetric, or
> depth, contour (should be used for about every 10th contour line)/Non
> NT
> 
> Четверг, 2 марта 2023, 12:01 +03:00 от Ticker Berkin
> :
> 
> Hi
> 
> My understanding of the default Garmin usage is that
>  0x20..0x22 are land/height contours (Minor to Major)
>  0x23..0x25 are sea/depth " "
> 
> Ticker
> 
> On Thu, 2023-03-02 at 08:52 +, Gerd Petermann wrote:
> > Hi Vadim,
> > 
> > I see code in mkgmap to handle the statement with Elevation=m or
> > Elevation=M, but it is only used for the line types 0x20 .. 0x22.
> > Do you have a good reason to use line type 0x25 instead?
> > 
> > Gerd
> > 
> > 
> > 
> > Von: mkgmap-dev
> >  > boun...@lists.mkgmap.org.uk>> im Auftrag
> > von Vadim Karpov >
> > Gesendet: Mittwoch, 1. März 2023 13:00
> > An:
> > mkgmap-dev@lists.mkgmap.org.uk > >
> > Betreff: [mkgmap-dev] The "Elevation=M" in the header of the polish
> > .MP files does not work
> > 
> > Good afternoon !
> > 
> > I am using the latest version of MkGMap and trying to create a
> > depth
> > chart with isolines (types 0x24, 0x25).
> > 
> > The problem is that the compiler interprets the depth specified in
> > Meters as in Feet.
> > The result is independent of the presence or value of the
> > "Elevation=M" parameter.
> > 
> > And I didn't find an alternative command line option. :(
> > 
> > So how can I tell the compiler to treat all numerical depth and
> > height values in an .MP file as meters and not feet?
> > 
> > Thanks for the advice.
> > 
> > PS: cGpsMapper works fine with "Elevation=M" of course.
> > PPS: Example of polylyne defs:
> > 
> > [POLYLINE]
> > Type=0x02500
> > Label=21
> > EndLevel=3
> > Data0=(47.13926351703,-122.560520313), ...
> > [END]
> > 
> > [POLYLINE]
> > Type=0x02500
> > Label=12
> > EndLevel=3
> > Data0=(47.12784640003,-122.562501059), ...
> > [END]
> > 
> > --
> > Vadim Karpov
> > ___
> > mkgmap-dev mailing list
> > mkgmap-dev@lists.mkgmap.org.uk<
> > /compose?To=mkgmap%2d...@lists.mkgmap.org.uk>
> > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> 
> --
> Vadim Karpov
> Отправлено из Почты Mail.ru
> 
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work

2023-03-02 Thread Gerd Petermann
Hi all,

OK, I see no problems to change this method  in GType.java:
public static boolean isContourLine(MapLine line) {
return line.getType() >= 0x20 && line.getType() <= 0x22 && 
!(line instanceof MapShape);
}

All I have to do is to change 0x22 to 0x25, right?

Gerd


Von: mkgmap-dev  im Auftrag von Vadim 
Karpov 
Gesendet: Donnerstag, 2. März 2023 14:38
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP 
files does not work

Hi

Yes.

Types 0x23.0x24.0x25 are used to create bathymetric maps.

Information from the MPCTypes.txt file (TypViewer application):

0x02000=Contour Lines/MINOR_CONTOUR/Minor land-based contour line/Non NT
0x02100=Contour Lines/INT_CONTOUR/Intermediate contour (should be used for 
about every 5th contour line)/Non NT
0x02200=Contour Lines/MAJOR_CONTOUR/Major contour (should be used for about 
every 10th contour line)/Non NT

0x02300=Contour Lines/MINOR_BATHY_CONTOUR/Minor bathymetric, or depth, 
contour/Non NT
0x02400=Contour Lines/INT_BATHY_CONTOUR/Intermediate bathymetric, or depth, 
contour (should be used for about every 5th contour line)/Non NT
0x02500=Contour Lines/MAJOR_BATHY_CONTOUR/Major bathymetric, or depth, contour 
(should be used for about every 10th contour line)/Non NT

Четверг, 2 марта 2023, 12:01 +03:00 от Ticker Berkin :

Hi

My understanding of the default Garmin usage is that
 0x20..0x22 are land/height contours (Minor to Major)
 0x23..0x25 are sea/depth " "

Ticker

On Thu, 2023-03-02 at 08:52 +, Gerd Petermann wrote:
> Hi Vadim,
>
> I see code in mkgmap to handle the statement with Elevation=m or
> Elevation=M, but it is only used for the line types 0x20 .. 0x22.
> Do you have a good reason to use line type 0x25 instead?
>
> Gerd
>
>
> 
> Von: mkgmap-dev 
> >
>  im Auftrag
> von Vadim Karpov >
> Gesendet: Mittwoch, 1. März 2023 13:00
> An: 
> mkgmap-dev@lists.mkgmap.org.uk
> Betreff: [mkgmap-dev] The "Elevation=M" in the header of the polish
> .MP files does not work
>
> Good afternoon !
>
> I am using the latest version of MkGMap and trying to create a depth
> chart with isolines (types 0x24, 0x25).
>
> The problem is that the compiler interprets the depth specified in
> Meters as in Feet.
> The result is independent of the presence or value of the
> "Elevation=M" parameter.
>
> And I didn't find an alternative command line option. :(
>
> So how can I tell the compiler to treat all numerical depth and
> height values in an .MP file as meters and not feet?
>
> Thanks for the advice.
>
> PS: cGpsMapper works fine with "Elevation=M" of course.
> PPS: Example of polylyne defs:
>
> [POLYLINE]
> Type=0x02500
> Label=21
> EndLevel=3
> Data0=(47.13926351703,-122.560520313), ...
> [END]
>
> [POLYLINE]
> Type=0x02500
> Label=12
> EndLevel=3
> Data0=(47.12784640003,-122.562501059), ...
> [END]
>
> --
> Vadim Karpov
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


--
Vadim Karpov
Отправлено из Почты Mail.ru

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Remove accentiuation

2023-03-02 Thread Gerd Petermann
Hi Karl,

sorry, I have no idea what you try to do. My understanding so far was that the 
apostrophe is added by transliteration which happens after style processing.
Please give us an OSM object that contains the name with the problematic 
characters.

I don't think that you can remove a single apostrophe with the subst statement, 
the current implementation doesn't seem to allow this special character.

Gerd


Von: mkgmap-dev  im Auftrag von 7770 
<7...@foskan.eu>
Gesendet: Sonntag, 26. Februar 2023 18:02
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Remove accentiuation

Hi.
For some reason it seems i am not able to perform this type of change in the
finalize section.

I get:
Error in style: Error: (points:427): Unrecognised command '='

The lines in points finalize style looks like:

name=* {name '${name}'}
# next line to remove ' from names.
name=* {set name='${name|subst:"'=>"}'}
include 'inc/address';

Is this how it is supposed to look?

Regards
Karl


On söndag 1 januari 2023 19:34:19 CET you wrote:
> You can try in stylefile this addidional  line : {set name='${name
>
> |subst:'=>}'} . This action shoult remove the apostrophe.
>
> thomas
>
> Am 01.01.2023 um 18:37 schrieb 7770:
> > Hi and with wishes of a Happy new year.
> >
> > When preparing maps i use the setting
> > --latin1   (same as --code-page=1252)
> >
> > This is good most of the time, since most language specific characters are
> > replaced with plain latin characters. Cyrillic is transliterated to latin.
> >
> > In Ukraininan there is a softening letter (ь), when this is present in a
> > name, it is transliteradet to ' (apostrophe).
> >
> > For example the city Львів becomes L'viv. This in turn makes searches more
> > difficult since one not familar with the language may not know where the
> > accentuation is placed. As a forigner i would not know if it is Lviv or
> > L'viv.
> >
> > Is there some better code page to use to start with (still performing
> > transliteration) or some way to ask mkgmap to remove the apostrophe from
> > the text?
> >
> >
> > Regards
> > Karl
> >
> >
> >
> > ___
> > mkgmap-dev mailing list
> > mkgmap-dev@lists.mkgmap.org.uk
> > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev




___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work

2023-03-02 Thread Ticker Berkin
Hi

My understanding of the default Garmin usage is that
 0x20..0x22 are land/height contours (Minor to Major)
 0x23..0x25 are sea/depth   ""

Ticker
 
On Thu, 2023-03-02 at 08:52 +, Gerd Petermann wrote:
> Hi Vadim,
> 
> I see code in mkgmap to handle the statement with Elevation=m or
> Elevation=M, but it is only used for the line types 0x20 .. 0x22.
> Do you have a good reason to use line type 0x25 instead?
> 
> Gerd
> 
> 
> 
> Von: mkgmap-dev  im Auftrag
> von Vadim Karpov 
> Gesendet: Mittwoch, 1. März 2023 13:00
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: [mkgmap-dev] The "Elevation=M" in the header of the polish
> .MP files does not work
> 
> Good afternoon !
> 
> I am using the latest version of MkGMap and trying to create a depth
> chart with isolines (types 0x24, 0x25).
> 
> The problem is that the compiler interprets the depth specified in
> Meters as in Feet.
> The result is independent of the presence or value of the
> "Elevation=M" parameter.
> 
> And I didn't find an alternative command line option. :(
> 
> So how can I tell the compiler to treat all numerical depth and
> height values in an .MP file as meters and not feet?
> 
> Thanks for the advice.
> 
> PS: cGpsMapper works fine with "Elevation=M" of course.
> PPS: Example of polylyne defs:
> 
> [POLYLINE]
> Type=0x02500
> Label=21
> EndLevel=3
> Data0=(47.13926351703,-122.560520313), ...
> [END]
> 
> [POLYLINE]
> Type=0x02500
> Label=12
> EndLevel=3
> Data0=(47.12784640003,-122.562501059), ...
> [END]
> 
> --
> Vadim Karpov
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files does not work

2023-03-02 Thread Gerd Petermann
Hi Vadim,

I see code in mkgmap to handle the statement with Elevation=m or Elevation=M, 
but it is only used for the line types 0x20 .. 0x22.
Do you have a good reason to use line type 0x25 instead?

Gerd



Von: mkgmap-dev  im Auftrag von Vadim 
Karpov 
Gesendet: Mittwoch, 1. März 2023 13:00
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: [mkgmap-dev] The "Elevation=M" in the header of the polish .MP files 
does not work

Good afternoon !

I am using the latest version of MkGMap and trying to create a depth chart with 
isolines (types 0x24, 0x25).

The problem is that the compiler interprets the depth specified in Meters as in 
Feet.
The result is independent of the presence or value of the "Elevation=M" 
parameter.

And I didn't find an alternative command line option. :(

So how can I tell the compiler to treat all numerical depth and height values 
in an .MP file as meters and not feet?

Thanks for the advice.

PS: cGpsMapper works fine with "Elevation=M" of course.
PPS: Example of polylyne defs:

[POLYLINE]
Type=0x02500
Label=21
EndLevel=3
Data0=(47.13926351703,-122.560520313), ...
[END]

[POLYLINE]
Type=0x02500
Label=12
EndLevel=3
Data0=(47.12784640003,-122.562501059), ...
[END]

--
Vadim Karpov
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] Remove accentiuation

2023-03-02 Thread 7770
Hi.
For some reason it seems i am not able to perform this type of change in the 
finalize section.

I get:
Error in style: Error: (points:427): Unrecognised command '='

The lines in points finalize style looks like:

name=* {name '${name}'}
# next line to remove ' from names.
name=* {set name='${name|subst:"'=>"}'}
include 'inc/address';

Is this how it is supposed to look?

Regards
Karl


On söndag 1 januari 2023 19:34:19 CET you wrote:
> You can try in stylefile this addidional  line : {set name='${name
> 
> |subst:'=>}'} . This action shoult remove the apostrophe.
> 
> thomas
> 
> Am 01.01.2023 um 18:37 schrieb 7770:
> > Hi and with wishes of a Happy new year.
> > 
> > When preparing maps i use the setting
> > --latin1   (same as --code-page=1252)
> > 
> > This is good most of the time, since most language specific characters are
> > replaced with plain latin characters. Cyrillic is transliterated to latin.
> > 
> > In Ukraininan there is a softening letter (ь), when this is present in a
> > name, it is transliteradet to ' (apostrophe).
> > 
> > For example the city Львів becomes L'viv. This in turn makes searches more
> > difficult since one not familar with the language may not know where the
> > accentuation is placed. As a forigner i would not know if it is Lviv or
> > L'viv.
> > 
> > Is there some better code page to use to start with (still performing
> > transliteration) or some way to ask mkgmap to remove the apostrophe from
> > the text?
> > 
> > 
> > Regards
> > Karl
> > 
> > 
> > 
> > ___
> > mkgmap-dev mailing list
> > mkgmap-dev@lists.mkgmap.org.uk
> > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev




___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Remove accentiuation

2023-03-02 Thread 7770
Hi.
Returning to this long-ago question.
For some reason it seems i am not able to perform this type of change in the 
finalize section.

I get:
Error in style: Error: (points:427): Unrecognised command '='

The lines in points finalize style looks like:

name=* {name '${name}'}
# next line to remove ' from names.
name=* {set name='${name|subst:"'=>"}'}
include 'inc/address';

Is this how it is supposed to look?

Regards
Karl


On söndag 1 januari 2023 19:34:19 CET you wrote:
> You can try in stylefile this addidional  line : {set name='${name
> 
> |subst:'=>}'} . This action shoult remove the apostrophe.
> 
> thomas
> 
> Am 01.01.2023 um 18:37 schrieb 7770:
> > Hi and with wishes of a Happy new year.
> > 
> > When preparing maps i use the setting
> > --latin1   (same as --code-page=1252)
> > 
> > This is good most of the time, since most language specific characters are
> > replaced with plain latin characters. Cyrillic is transliterated to latin.
> > 
> > In Ukraininan there is a softening letter (ь), when this is present in a
> > name, it is transliteradet to ' (apostrophe).
> > 
> > For example the city Львів becomes L'viv. This in turn makes searches more
> > difficult since one not familar with the language may not know where the
> > accentuation is placed. As a forigner i would not know if it is Lviv or
> > L'viv.
> > 
> > Is there some better code page to use to start with (still performing
> > transliteration) or some way to ask mkgmap to remove the apostrophe from
> > the text?
> > 
> > 
> > Regards
> > Karl
> > 
> > 
> > 
> > ___
> > mkgmap-dev mailing list
> > mkgmap-dev@lists.mkgmap.org.uk
> > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev




___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev