The transliteration is for sure done in mkgmap and not in the garmin
unit. But don't ask me details, where and how it happens.
Claudius Henrichs schrieb:
Currently if the name-tag is written in persian or arabic script on a garmin
device it ends up transliterated into latin script. I am not
On Tue, May 18, 2010 at 07:39:54PM +0200, Johann Gail wrote:
The transliteration is for sure done in mkgmap and not in the garmin
unit. But don't ask me details, where and how it happens.
Right. If someone could supply some details, I could submit some
patches. It would be nice to translate
El 18/05/10 20:23, Marko Mäkelä escribió:
On Tue, May 18, 2010 at 07:39:54PM +0200, Johann Gail wrote:
The transliteration is for sure done in mkgmap and not in the garmin
unit. But don't ask me details, where and how it happens.
Right. If someone could supply some details, I could
I think Roman numbers should be displayed as upper case roman number, at
least when they are part of a ref or name. If you have always seen a
street name as, say Juan XXIII it may be difficult to recognize it as
Juan 23. For dates it could be better to translate into Arabic numbers
as
The string to encode is ½ (1/2 as single character). This is used as
housenumber in Wuerzburg:
http://www.openstreetmap.org/?lat=49.801248lon=9.927579zoom=18
To solve this I increased the byte buffer provided in encodeText by 1.
But I'm not sure if this is the right solution.
The maximum
On 17/05/10 11:50, Claudius Henrichs wrote:
Currently if the name-tag is written in persian or arabic script on a garmin
device it ends up transliterated into latin script. I am not sure if garmin
is doing this internally or mkgmap. Can any developer clear this up?
I am asking because this
There is also something strange about the Russian encoding. The letter
я is translated into â, while I believe the correct transliteration
would be ya or ja, at least at the end of a word. But I can live
with the â, at least it looks like a and is easy to recognize.
You can transliterate
