Just replying to myself (in case anyone wants to know how this was resolved). I went through the keys of the array and ran macToIso() on each one. After checking that the appropriate delimiters were now ascii 30 and 29, I then ran the code and it worked. I'm glad I don't have to come up with a new mechanism, but still puzzled as to what happened. I hope that since the stack's charset is "iso" (since it was built on Windows originally), when I try to run it as a Windows standalone there won't be any translation problems again.
Bernard On Wed, Oct 8, 2008 at 11:04 PM, Bernard Devlin <[EMAIL PROTECTED]> wrote: > I have a stack where I use some non-printable ascii chars as delimiters > (specifically, ascii 30 and 29). This stack worked fine on the Windows and > Linux versions of 3.0 (well, until they crashed or went berserk, but > everyone's tired of that story). However, when I moved the stack over to OS > X (ppc), the application stopped working. Upon investigation it turned out > that the delimiters had swapped - they were now ascii 222 and 218. > > Is that to be expected? Nothing else in the stacks seems amiss, and I'm > puzzled by this. I had seen some strange behaviour copying them between > platforms. When copied by scp, the stacks were "corrupted", but copied fine > by ftp binary. When copied by ftp as ascii, opening them crashed Rev 3.0 on > OS X. > > It's not a big deal, but I suppose it might be a gotcha worth noting for > anyone else who uses non-printable ascii chars as delimiters. > > Bernard > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
