Re: Can I add the charset parameter to the pilot device configuration?

[Matt Davey <mcdavey mrao cam ac uk>]

On Mon, 2004-11-08 at 16:00, lsla post cz wrote:
> I started from the gnome-pilot list because the changes to the
> pilot-link are trivial and absolutely harmless. (the code is already
> there, I will just add a function which sets the charset. If you do not
> call the function, it works as always.)

I suggested pilot-link-devel because we have a chicken and egg
situation.  We can't release a gnome-pilot with charset support until it
is added to pilot-link.  It sounds like it might be feasible to get
changes in before the next release of pilot-link, in which case I think
that should be your focus.

> On the other hand, the changes to gnome-pilot are much more complicated.

Depends what you're used to coding.  I'd have thought populating and
adding a new combo box and adding a line to the config file is pretty
trivial compared to dealing with the logic of which charsets are
supported by iconv, what the mapping is from the iconv id's to the
PalmOS charset ids, which code is responsible for ensuring a compatible
charset, what to do when characters can't be converted, etc.

> > Ideally the charset
> > encoding is something that should be picked up from the palm device
> > directly. 
> 
> Great idea. But I am not sure this can be always done. The default value
> in the applet should not be "CP1252" but "Pick up from the device".

Sadly, I don't think this is possible, so the default should be CP1252
and the GUI should show "default".

See
http://www.palmos.com/dev/support/docs/protein_books/PortingPalmApps/PalmLocale.html
for example.

Matt