[fpc-devel] [PATCH] XMLCFG AnsiString<>DOMString conversion

Dariusz Mazur darekm at emadar.com
Thu Nov 4 16:55:22 CET 2010

  W dniu 2010-11-03 23:50, Sergei Gorelkin pisze:
> darekm at emadar.com пишет:
>> When I using xmlCfg unit i found problem with storing literals in
>> arbitrary code page. XMLCfg perform automatic conversion with omit some
>> chars.
>> I've change it to use utf8string instead of. Maybe this patch will be
>> interesting.
> Such patch will make all existing config files with non-ascii data 
> unreadable.

Today also. All nonasci charracter are translate to '?' during reading 
(implicit conversion widestring>ansistring).
On other side in XML should not be not asci char

> In the meantime, I wrote the xmlconf unit exactly to avoid this 
> problem. So if you need Unicode configs, you should switch to xmlconf. 
> Calls to Utf8Encode/Decode will be still necessary because 
> xmlconf.TXMLConfig has WideString parameters, but it won't strip any 
> non-ascii data.

XMLCfg is enought to me,
but then you should add note that this unit is depreciated


More information about the fpc-devel mailing list