Jesus Reyes wrote: > > By the way, and taking the fact that xml files are stored always in utf-8 > encoding it's surprising that for example XMLConfig doesn't have a way to set > a value which is already utf-8 encoded. so, any change to add a methods that > take utf-8 encoded strings as arguments?, this way it could ve avoided > unnecesary conversions. > The writer wasn't utf-8 capable at the time of writing TXMLConfig. Even if you add utf-8 methods to TXMLConfig, certain conversions will stay because underlying DOM is WideString-based. After adding utf-8 to the writer, I've chosen to write a new unicode-enabled config class instead of modifying the old one and risk breaking the existing code. The new component is in the xmlconf unit, and it takes WideString arguments.
Regards, Sergei _______________________________________________ Lazarus mailing list [email protected] http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
