> The UTF-8 encoding is IMO best choice. I sent you my class that reads > ANSI as well as UTF-8 INI files (with or without BOM for best backwards > compatibility), it writes however allways UTF-8, if you do not use > characters above #127 UTF-8 is ASCII compatible and those files > could still be read by ICSv6.
Your class is nice and works well as far as I've seen. Thanks. I have another concern: It would be very handy if the same class could read the existing ini files (that seems to be the case) AND write them if if possible. This would tremendly help those using many Delphi versions and using simple ansi values. The issue I try to explain is examplified by this: Assume an ini file storing a filename. Assume the filename is "François.txt" (notice the cedil which is the correct way to write my firstname). When used with you class, such an ini file can be read without problem but as soon as it is written, then "ç" is converted to UTF8 and is no more readable by the standard TIniFile. This is a loss which could be avoided. That's what I'm trying to say. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
