On Sun, Jul 24, 2016 at 3:05 PM, Shon Edwards sre.1966@gmail.com wrote:
Hadn't thought of that; that's a wonderful idea. We live in a worldwide Unicode world now. Some of my radios can be programmed in Japanese, others in European languages. MS started to enable Windows and apps for Unicode over 15 years ago. No reason to not go along now. Thx.
The thing is, Chirp is all unicode and always has been. The trouble is when interfacing with external things. The example fix was for RepeaterBook, where they are sending ISO-8859-1 encoded strings. We convert those to unicode for use in Chirp. Likewise, if a radio is storing a Japanese or European character in an encoding other than unicode, we need to convert it to unicode when read by Chirp. My hunch is that the problem with Windows is the same--the encoding of the home folder path is not unicode, so we must convert it. However, being a Linux dev I'm not familiar with what encoding Windows uses or what conversion is needed.
Tom KD7LXL