Well the good news (I suppose) is that base64Decode seems to ignore the carriage returns in the encoded string. The bad news (for me) is that it means my intermittence issue had nothing to do with the carriage returns.
Bob S > On Apr 25, 2024, at 8:09 AM, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Whaaaaa???? THAT may be why I was getting intermittent success with a socket > based file transfer utility I developed! I wonder what base64Decode does with > a base64Encoded string if you remove the carriage returns first? I’m going to > have to research that. > > Bob S > > >> On Apr 25, 2024, at 7:57 AM, Andreas Bergendal via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> The problem may be that base64 encoding inserts line breaks after every 76 >> chars (a remnant from terminal monitor width restrictions, apparently). >> I ran into this a while ago, and cleaning the encoded string with “replace >> cr with empty in tString” solved it for me. >> I don’t think any textEncode/Decode should be needed after that (Python is >> a different animal after all… :) >> >> /Andreas >> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
