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

["lsla post cz" <lsla post cz>]

> I assume you meant gnome-pilot should be modified, to add charset
> support to gnome-pilot.
> 

Exactly. Sorry for my English. I tried to say that if the support would
remain in pilot-link it must be rewritten anyway.


> > 6) The code in pilot link can be easily replaced by the GLib function
> > g_convert() removing pilot-link dependency on iconv.
> 
> I'm not sure I follow you here: you don't want to put g_convert() into
> gnome-pilot!  iconv is okay in pilot-link because it's in glibc, not
> glib.  pilot-link has no glib dependency, and that isn't going to

I want this:

1) not to call convert_* from gnome-pilot or evolution; this makes
convert_* obsolete

2) instead call g_convert() from gnome_pilot 

3) evolution plugins will call gnome_pilot to make conversion for them,
not pilot-link
 
> change, so it isn't going to get g_convert.  Anyway, g_convert uses
> iconv under the hood so you're not removing a dependency.

I mean pilot-link dependency. 

>   Maybe I
> misread you, and you mean to quit using the pilot-link conversion, and
> use g_convert within the gnome-pilot code.  That would be good.
> 

Exactly.

> However, I think you're right that the pilot-link charset support was
> put in specifically for the benefit of gnome-pilot.  That doesn't mean
> that removing it is a good idea or even necessary: probably marking it
> deprecated is less likely to annoy people wanting to upgrade pilot-link
> without breaking evolution/gnome-pilot.

Yes. I agree. I must not break any dependency, someone can upgrade just
the pilot-link or just evolution. 


> > I am just experimenting with this. I can set charset in config file and
> > copy from/to pilot works fine. I have problems with synchronizing
> > records, still. After I remove the bugs, I will send the patch here, and
> > also to pilot-link and evolution lists for considering.

> The applet could check that the supplied string is supported by
> g_convert().
> 

I think that an uneditable combo box is perfect for this. The charset
combo in capplet will be populated from a predefined list of encodings
taken from libiconv docs. (Otherwise an user will have to remember exact
spelling eg: iso8859-2, iso-8859-2, Iso8859.2 ).


Best Regards

Ladislav