Thanks for the info. But why do you need the ASCII and UTF-7 encoding at all? Provided the text contained non-ASCII chars they would be replaced by the default fail char "?", why not just save with default ANSI encoding, the first 128 chars are always the same, in any codepage. Also I've never seen a UTF-7 encoded text file so far, UTF-7 is usually only used with 7-bit internet protocols such as email or news.
It's a file save dialog and it looked fancy to allow the user to save as ASCII, UTF8, UTF7 etc. I agree that the use is questionable but I leave it to the user to decide what format (s)he needs or likes. Default I use UTF16 in fact.
-- 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
