>> It appears the OS API code is not reading the 3 UTF8 BOM bytes >> correctly if there are only 3 byte before the section name. >> > > That's what I mean, don't rely on the API in this case since all > this stuff is undocumented. Better use a class that handles > file access natively. > The class can fix the issue checking for the presence of the EOL after the BOM, and add it if needed, but all this are just suggestion, you guys decide ;-)
-- 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
