opensync-devel

[Opensync-devel] xmlEscapeEntities : char out of range

[deloptes <del...@ya...>]

this is the other thing that is bugging me.

there is QString.toLatin1() pretty often in the code, but I am not a big fan
of old 8bit encoding done in Latin1, so what kind of encoding should I use
UTF-8?

regards

Re: [Opensync-devel] xmlEscapeEntities : char out of range

[Daniel G. <go...@b1...>]

On Friday, October 29, 2010 09:51:25 am deloptes wrote:
> there is QString.toLatin1() pretty often in the code, but I am not a big
> fan of old 8bit encoding done in Latin1, so what kind of encoding should I
> use UTF-8?

Yes, please use in xmlformat utf8.

Best Regards,
Daniel

-- 
Daniel Gollub
Linux Consultant & Developer
Tel.: +49-160 47 73 970 
Mail: go...@b1...

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

Re: [Opensync-devel] xmlEscapeEntities : char out of range

[deloptes <del...@ya...>]

Daniel Gollub wrote:

> On Friday, October 29, 2010 09:51:25 am deloptes wrote:
>> there is QString.toLatin1() pretty often in the code, but I am not a big
>> fan of old 8bit encoding done in Latin1, so what kind of encoding should
>> I use UTF-8?
> 
> Yes, please use in xmlformat utf8.
> 
> Best Regards,
> Daniel
> 

thanks. I think I know what's the problem.
akonadi-sync had an error and exported empty data so file-sync created empty
files which reported in the next sync are breaking in xml - cool :-).

my question however was if when storing data into osync_data obj I should
use QSring.toUtf8() instead toLatin1. This means how the bytestream should
be formated when stored with set_data, respectively if using utf8 for
reading and dealing with hashes.

I'm not sure if it makes difference, but it should as the bytestream, stored
in char* should be constant, so 

thanks