On Monday, December 1, 2003, at 03:19 PM, Alex Rice wrote:
Would base64 encoding the content before compressing it be a suitable workaround for the char set issues?
Base64 would not help. It's not before compression that is the issue. The stuff I'm encrypting already has a less-than 127 numToChar() value restriction. If you look at the text of the compressed data you will see many ascii characters that numToChar() higher than 127. These chars read differently on different Systems. Even if you macToISO() the chars they end up changing the decompress process on different platforms.
Is there a bugzilla # I can read to get up to speed on this bug?
I only found one and it said it was resolved. I think this might be a feature request kind of an issue.
mb
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
