Reference Citations - HerongYang.com - v2.91, by Dr. Herong Yang
Sending log to Geocaching.com (Garmin Oregon 750)
'Opening UTF-16BE Text Files' tutorial was cited in a geocaching.com article in 2020.
The Opening UTF-16BE Text Files tutorial was cited in a geocaching.com article in 2020.
Subject: Sending log to Geocaching.com (Garmin Oregon 750) Date: Jan 4, 2020 Author: By Raiden38 Source: https://forums.geocaching.com/GC/index.php?/topic /354644-sending-log-to-geocachingcom-garmin-oregon-750/ ... > Actually, the geocache_visits.txt file is ALMOST a simple text file. It may > appear so in a simple text editor like Notepad and will just have some odd > spaces showing in > Wordpad, but do NOT try to edit one with a simple text > editor I went back to a conversation with Raine in 2008 when geocache_visits first roamed the earth. It was officially decreed to be UTF-16. (I didn't get a vote. Windows digs UTF-16, but the rest of the computing world largely considers it a mistake.) Most of the better text editors (not word processors) allow you to control the character set if they can't automatically detect it. I don't remember if it's big or little endian (and that ambiguity is on of the problems with UTF-16) but it should be pass fail to try either setting. The difference is whether a latin 'A' is encoded as bytes 0x00 0x41 or 0x41 0x00. It looks like Notepad can be set to work with either one: http://www.herongyang.com/Unicode/Notepad-Open-UTF-16BE-Text-File.html
Table of Contents