Thread: City Navigator Middle East & Northern Africa NT 2013.40

Originally Posted by smokefree

GMapTool info shows codepage 1256 (Arabic). However, the map shows on both my nüvi's 200 and 350 in Latin writing as if codepage 1252 is used...??

This map as like other multilingual map use both codepage. If device support a local codepage the map shows in this codepage. If not a map shows in Latin. Both of you devices do not support Arabic codepage. So it is OK!

P.S. In new device a shown codepage is depended from selected Locale. Also the map have the identifier in part-number that is corresponding with record in Locales.xml. In this case: D242310AG027 in map header vs next record in Locales.xml:

<Mapping>
<ID>G027</ID>
<LocaleName>الشرق الأوسط</LocaleName>
</Mapping>

P.S.1. Some Garmin programs do not have a such proper behavior and they read a data with local codepage but shows it in unreadable view because device is not have support for local codepage. For this case we need patch a codepage in map file manually.

Originally Posted by smokefree

Are there instructions here at Noeman how to create such a patch?

I have the next my reverse engineering:

Offset in LBL section - 0x0aa, Size - 2 byte, Codepage - 0xe4 0x04 = 1252
Offset in MDR section - 0x015, Size - 2 byte, Codepage - 0xe4 0x04 = 1252
Offset in SRT section - 0x02D -> Read offset for The Character Lookup Table -> Goto offset for The Character Lookup Table-> Move to 6 byte for CodePage
Offset in TRF section - 0x027, Size - 2 byte, Codepage - 0xe4 0x04 = 1252
Offset in TYP section - 0x015, Size - 2 byte, Codepage - 0xe4 0x04 = 1252

I use script for WinHex below. It is not perfect but it is work:

[hide]http://www64.zippyshare.com/v/16928928/file.html[/hide]

attached
[Only registered and activated users can see links. ]