On 23-Apr-07, at 8:28 AM, Arnaud Nicolet wrote: > Le 23 avr. 07 à 16:17 Soir, [EMAIL PROTECTED] a écrit: > >> Well, it's not too complicated -- GetSaveInfo returns binary data, >> which could happen to include whatever delimiter your text file uses >> (including line feeds, Chr(0)'s, spaces, tabs, or anything else). In >> addition, it almost certainly will not be any sort of valid UTF-8 >> data, >> so if you were to treat it as a string of text, it would cause any >> text >> processing to abort. So, you pass it through EncodeBase64, and now >> you >> have nice well-behaved ASCII text that can be treated as such. > > It's not always obvious that the EncodeBase64 function converts non- > printable characters to ASCII characters. In my opinion, I thought > they were either stripped or kept unchanged.
Stripping them would destroy the original data Not encoding them would mean they could potentially be ruined by anything that did not handle characters with their high bit set (this used to be a real problem on the internet) It takes 8 bit data and makes it 7 bit and ensures that all the data only uses valid ASCII character codes _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
