Oregon 300

[tlchuan]

006-D1053-60.bin
006-D1053-64.bin
006-D1053-65.bin
006-D1053-67.bin

Brother fancheng & Little_frog where to load the above files in oregon ? TQ

[tlchuan]

any one Know how to add chinese font can you please show how to do it step by step here thank you.

[loramore]

I found this forum on google, and was wondering what your opinions would be on my situation.

I am currently living in a homestay in Japan, and my hostmom wants to buy a GPS. The Garmin sports line in Japan only has the Colorado model (and it's about $1000). So, she would like an Oregon purchased off US Amazon.

How hard would it be to adapt? For example downloading Japanese maps (she wants it for when she goes mountain climbing) Japan amazon has software for purchase, but would this work?

and then the Japanese language (I found the language topic on this forum, so maybe that's do able).

Thanks in advance for any suggestions. I understand that this forum is for Malaysia & Singapore, but I thought I would try.

[tlchuan]

As far as i know US Oregon don't come with Japanese language. only Oregon Taiwan units has japenese.

[JJ007]

this is a similar to what I face last year when visited japan. I have an US based Oregon 300. the key issue of these US based device is that they do not support other non-Roman native language fonts for manu display, as well as map display.

I have no problem at the end by using English version of japan map provided by uud, and with default "freiendier' (for me) English menu for the device control. as a Japanese, I believe she prefered all in Japanese

some of us here have tried the tweak by copying equilvalent language fonts from nuvi series to Oregon, however, at the end, we may be able to make part (or may be all) menu to be dispalyed in that language font we want to see, however the basic issue is not resolved, how to have proper input in Chinese pinyin, or Japanese?

so unless she want to pick up english, otherwise US (english) based Oregon is not a good choice for her

not sure other situ here has any breakthru so far??

[samra]

This topic is rather old. But now I still have question, so please, correct me if you know, thank you!.

I think, the problem we have now is displaying new fonts other than latein in our Garmin Oregon. As I know the best standard for character coding is UTF-8, for character like Chinese, Japanese there will be several bytes for 1 character (start byte 1..10xxx and following bytes 10xxx), while the most latein languages or those using old 8-bit-codepages like 1253, 1254 have 8 bits enough for their coding. So the problem is the device will display very differently for characters having code in range 128-255 when it uses different codepages. So if the device uses only new codepage 65001 (UTF-8), I believe, this display problem will no more exist.

I don't know, if the compiler cgpsmapper has an option for compiling maps in codepage 65001??

I think, it would be better, if Garmin could separate the display for strange fonts from setting a new keyboard for a new language, i.e. different codes (setting) for these two, and we could change it manually (in *.gtt).

[JJ007]

This topic is rather old. But now I still have question, so please, correct me if you know, thank you!.

I think, the problem we have now is displaying new fonts other than latein in our Garmin Oregon. As I know the best standard for character coding is UTF-8, for character like Chinese, Japanese there will be several bytes for 1 character (start byte 1..10xxx and following bytes 10xxx), while the most latein languages or those using old 8-bit-codepages like 1253, 1254 have 8 bits enough for their coding. So the problem is the device will display very differently for characters having code in range 128-255 when it uses different codepages. So if the device uses only new codepage 65001 (UTF-8), I believe, this display problem will no more exist.

I don't know, if the compiler cgpsmapper has an option for compiling maps in codepage 65001??

I think, it would be better, if Garmin could separate the display for strange fonts from setting a new keyboard for a new language, i.e. different codes (setting) for these two, and we could change it manually (in *.gtt).

interesting observation and comments ...

in fact our 'needs' are in 2 folds, those who want full substitution of non-Roman fonts for both display as well as inputs, and those who just want to have a good/ (correct!) display of non-Roman fonts in menu layout, and most importantly, the maps and POIs.

for the 1st type of users, better get a 'local' set (Taiwan for Chinese font IME and display, Japan for Japanese ...)

for the 2nd type of users, which are the majority of us, has tried by 'replacing' the default fonts files (BIN files), as a results, the menu display wasn't right. So it is interesting enough to pursue further how it can be done without re-investing, believe me, you will probably want to see 西门盯 rather than XiMenTin in your map, right?

[FF255]

This is quite old topic. I am a new comer to this forum. And I recently purchased an Oregon 450 in US and try to bring it back to China for using in China. Is there anybody here had the experience that the great trick you guys here found also applied to Oregon 450? Thanks a lot!