Re: [Opensync-users] libwbxml 0.10.9

[Michael B. <mic...@cm...>]

On 01/10/11 12:32, Emanoil Kotsev wrote:
> 
>> The handling of the character set must be fixed because of some 
>> requirements of Android. They use UTF-16 without a default 
>> encoding. This is legal according to the specification but
>> requires that the character set is specified by the transport. This
>> is actually not possible with libwbxml.
> 
> From my work with xerces it is not bad idea to use utf-16. In some
> cases it has more advantages as disadvantages. Why is it not possible
> to set a default charset in libwbxml. Why should one need anything
> else except utf?

The problem is that the specification does not define one default
encoding. The old specifications WBXML 1.0 or so defined UTF-8 but the
new specification WBXML 1.3 defines UTF-8 and UTF-16.

So if there is no character set specified which character set should be
used? libwbxml uses UTF-8 as default because this is compliant with new
and old versions of the specification.

Android uses UTF-16 and does not specify the character set in the WBXML
document. So the user of the library must set the character set via the
interface.

Best regards

Michael
-- 
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 70143          ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 70135          Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB