[mkgmap-dev] A contribution to the vocabulary based on the mkgmap default style and typ files.

Sun Aug 9 13:29:29 BST 2020

I can help you with 0x23 - 2e

"0x23 brazilian"
"0x24 korean"
  "0x25 japanese"
  "0x26 chinese"
  "0x27 trad. chinese"
  "0x28 thai"
  "0x29 arabic"
  "0x2a belarusian"
  "0x2b ukrainian"
  "0x2c moldavian"
  "0x2d montenegrin"
  "0x2e Irish"

r.

Nick

On 09/08/2020 13:09, Randolph J. Herber wrote:
>
> Dear, Sir:
>
> Apparently, I did not make myself sufficiently clear. I apologize. 
> First, I request the codes from 0x23 to 0x2e so that I can assign the 
> correct languages to those codes. Second, and I quote myself: "I 
> arbitrarily assigned codes for the other languages."
>
> I see two uses for the table I provided. First, for someone that does 
> not use a language whose code is 0x01 to 0x22 to use one of the 
> "extra" languages to fill slot 0x00 or, in fact, any of the slots to 
> have a more comfortable language in their Garmin receiver. Second, for 
> some who does not not want to do a language re-assignment, to find 
> translations from a more comfortable language to one of the Garmin 
> "official" languages.
>
> In no way to I contradict your statement: "As far as I know Garmin 
> only uses codes up to 0x2E."
>
> As I said before: "I request consideration: I intend no offense and 
> corrections are welcome."
>
> Sincerely,
> Randolph J. Herber
>
> On 8/9/2020 4:41 AM, nick wrote:
>>
>> Hi
>>
>> I'm interested to learn the source you used for language codes   > 
>> &0x2F  .
>>
>> As far as I know Garmin only uses codes up to 0x2E
>>
>> Regards
>>
>> Nick
>>
>> On 08/08/2020 21:42, Randolph J. Herber wrote:
>>> Hi, all!
>>>
>>> First, note the attached file is in JSON format and is inherently 
>>> UTF-8.
>>>
>>> Second, the file contains four sub-tables: point, line, polygon, and 
>>> language. The first three should be obvious. The language sub-table 
>>> contains the languages presented. I used the extant codes for the 
>>> extant languages mentioned in the mkgmap web documentation. I 
>>> arbitrarily assigned codes for the other languages. Altogether, one 
>>> hundred three languages are presented. I used Google Translate and 
>>> am paying for Google's services here. Therefore, this is 
>>> work-for-hire and I may give them away. Yes, I readily admit some of 
>>> translations are awkward or even incorrect. There, I request 
>>> consideration: I intend no offense and corrections are welcome. I 
>>> tended not to change Eurocentric terms to American terms although in 
>>> some cases I added the equivalent American term. I expanded some of 
>>> the phrases in hopes of improving the machine translations.
>>>
>>> Third, I feel that all urban areas should be treated equivalently 
>>> and I note Ticker Berkin's previous comments on that topic, the 
>>> translations reflect my preferences. I did incorporate Ticker's most 
>>> significant objection which I did find valid. Also, I feel that an 
>>> logarithmic scale is appropriate in this application and that 
>>> 3.2*3.2 is 10.24, which is about 10. This allows a good range of 
>>> population values.
>>>
>>> Fourth, I am working on incorporating this material into the default 
>>> style and typ files, in particular the typ file.
>>>
>>> Thank you,
>>> Randolph J. Herber
>>>
>>>
>>> _______________________________________________
>>> mkgmap-dev mailing list
>>> mkgmap-dev at lists.mkgmap.org.uk
>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200809/db94c259/attachment.html>