[turba] Character encoding in exported address book

[Jan Schneider]

Zitat von Otto Stolz <Otto.Stolz at uni-konstanz.de>:

> Hello,
>
> my installation: Horde 3.1.3, Imp H3 (4.1.3), Turba H3 (2.1.3);
> excerpts from the configuration can be found below.
>
> From the »Import/Export Adress Books« screen, I can export my
> personal addressbook in four different formats:
> - Comma separated values,
> - Comma separated values (Microsoft Outlook),
> - Tab separated values,
> - vCard,
>
> The three list formats are exported in UTF-8 (with a leading BOM),

Actually in the encoding that is used for the interface. But that's  
UTF-8 in most cases.

> whilst the vCard format is exported in ASCII (with UTF-8/quoted-printable
> encoding of non-ASCII characters).
>
> Now, the import form has a selection widget titled »Select the charset
> of the source file«, with ISO 8859-1 as its default.
>
> I'd rather have UTF-8 as the default, or no selection at all, so my users
> have less oportunity to make errors and besiege our help desk.
>
> Questions:
> - Is it wise to abandon the selection of the import encoding, altogether,
>   or are there indeed notebooks with other encodings in the wild?

Of course there are. Most application export in the "native" encoding.  
If your users import from any external application, chances are high  
that the data is latin1 encoded.

> - How can I set UTF-8 as the default encoding?

Change the import template.

> - How can I remove the charset selection widget from the import form?

Change the import template.

> - If the answer on my 1st question is "that depends", would it be
>   possible to have the charset selection widget adapt itself to the
>   choice made in the »format of the source file« widget?

Yes, sure, it could be hidden if vCard is selected.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/