[chirp_users] Issue with Umlauts
tom at tomh.us
Mon May 18 08:08:01 PDT 2015
On Mon, May 18, 2015 at 2:55 AM, Christian Hilgers
<christian.dg7pc at gmail.com> wrote:
> I tested chirp 0.4.1 on Debian Jessie with my Kenwood TH-F7e via USB-serial
> Adapter and a serial-RIG Cable.
> It worked very well and I could read and write data from and to the
0.4.1 is long out of date. Best to use the daily build, currently
> It failed while reading Frequency Names like Düsseldorf or others with
> Umlauts. I am running UTF8 on my box.
How did the failure manifest? The only issue I know of with umlauts is
when used in a Windows user name (and subsequently the home directory
path), Chirp fails to run. This is a tough one, because the Chirp code
does all the right things for UTF-8 support. We're thinking it's a
PyGTK issue (which Chirp depends on).
Each radio has a specific character set that it will accept for
frequency names. Many radios define this in the manual which Chirp
developers can reference to implement identical support. If the
character set is not printed in the manual, it's a bit of a guessing
game which characters the radio will support. Sometimes we get it
wrong. FWIW, I'm not aware of any radio that supports UTF-8 in the
frequency names, but extended ASCII is relatively common. Here's the
full list of what Chirp implements for each radio:
If something here differs from what the radio supports, let us know.
More information about the chirp_users