Are you sure this is a Rev bug? I seem to recall from the original
post that the stack was transferred over ftp or some other internet
file transfer. Did you try to zip it before sending it?
I know some forms of file transfers can corrupt a file when sent over
the internet. It is far less prevalent than it used to be, but that is
why encoding was originally used. Files were converted to internet
friendly characters because internet routers were originally only
designed to pass text based files.
Bob Sneidar
IT Manager
Logos Management
Calvary Chapel CM
On Oct 8, 2008, at 3:39 PM, Bernard Devlin wrote:
Looks like it was bugzilla'd a few years ago:
http://quality.runrev.com/qacenter/show_bug.cgi?id=3681
It's a pity it doesn't work as I'd kinda come to rely on those
unused ascii
characters as delimiters.
Bernard
On Wed, Oct 8, 2008 at 11:32 PM, Bernard Devlin <[EMAIL PROTECTED]>
wrote:
When I want to refer to these non-printable characters in script I
use
numToChar. The place where they got changed was in actual text
stored as
custom properties.
I'm not sure if this should be marked as a bug. I can understand
if my
original characters had ascii values above 127 that macToIso and
isoToMac
might be necessary, but not when the character values are below 127.
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
_______________________________________________
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
