>>>It does, Dar... when compressed userProperty data is involved.
Is userProperty what I know as custom property?
Yes... terminology error... oops.
/H
On Saturday, October 4, 2003, at 11:05 AM, [EMAIL PROTECTED]
wrote:
>> It does, Dar... when compressed userProperty data is involved.
SFAIK under all circumstances. The workaround (if memory serves) is to
store base64Encode(compress(tData)) in a userProperty instead, but
there is no space savi
>>> Next, I'll find out that stack encryption will destroy binary data.
>> It does, Dar... when compressed userProperty data is involved.
> Thanks for the warning.
>
> Uh, I'm a little confused this morning. Under what conditions does
> this occur?
>
> I know mcencrypt() loses info on binary da
On Saturday, October 4, 2003, at 02:06 AM, [EMAIL PROTECTED]
wrote:
> Next, I'll find out that stack encryption will destroy binary data.
It does, Dar... when compressed userProperty data is involved.
Thanks for the warning.
Uh, I'm a little confused this morning. Under what conditions does
t
> Next, I'll find out that stack encryption will destroy binary data.
It does, Dar... when compressed userProperty data is involved.
/H
On Friday, October 3, 2003, at 02:45 PM, J. Landman Gay wrote:
I may be mis-remembering, but I thought character conversions were now
done on custom properties as well as on fields. Or was I dreaming > that?
I hope that's not the case- then there would be no safe place to put
binary data in sta
On Friday, October 3, 2003, at 03:15 PM, J. Landman Gay wrote:
It won't work for me. In re: your other note, there are no nulls and
the lines are not long; it is just plain ascii. So I don't think the
problem is with the source text, especially since I can reproduce the
problem no matter what I
On Friday, October 3, 2003, at 02:45 PM, J. Landman Gay wrote:
I may be mis-remembering, but I thought character conversions were now
done on custom properties as well as on fields. Or was I dreaming > that?
From the dictionary entry for ISOToMac():
Revolution automatically translates text in fi
On Friday, October 3, 2003, at 02:45 PM, J. Landman Gay wrote:
I may be mis-remembering, but I thought character conversions were now
done on custom properties as well as on fields. Or was I dreaming > that?
Yikes!
Does this mean all binary data in a stack will have to be base64 or
hex? This i
On 10/3/03 3:20 PM, Dar Scott wrote:
On Friday, October 3, 2003, at 01:14 PM, J. Landman Gay wrote:
I don't want to maintain separate stacks for each platform. Any idea
how to get around this problem? I thought compression was supposed to
work the same way on all plaforms.
Me, too.
There is
On 10/3/03 3:13 PM, Jeanne A. E. DeVoto wrote:
At 2:14 PM -0500 10/3/2003, J. Landman Gay wrote:
The data decompresses fine on whatever platform did the compression.
But when the data is compressed on Windows, it won't decompress when
the stack is copied to a Mac. When the data is compressed on
On 10/3/03 3:13 PM, Jeanne A. E. DeVoto wrote:
At 2:14 PM -0500 10/3/2003, J. Landman Gay wrote:
The data decompresses fine on whatever platform did the compression.
But when the data is compressed on Windows, it won't decompress when
the stack is copied to a Mac. When the data is compressed on
On Friday, October 3, 2003, at 01:14 PM, J. Landman Gay wrote:
To save disk space, I run it through compress() and put the compressed
data back into the field before saving the stack.
A field can lose data that contains a null or has "lines" too long.
...and what Jeanne said.
Dar Scott
___
On Friday, October 3, 2003, at 01:14 PM, J. Landman Gay wrote:
I don't want to maintain separate stacks for each platform. Any idea
how to get around this problem? I thought compression was supposed to
work the same way on all plaforms.
Me, too.
There is a decompression bug for OS X & Revolutio
At 2:14 PM -0500 10/3/2003, J. Landman Gay wrote:
The data decompresses fine on whatever platform did the compression.
But when the data is compressed on Windows, it won't decompress when
the stack is copied to a Mac. When the data is compressed on a Mac,
it won't decompress when the stack is co
This has come up on the list before, but I didn't find a solution in the
archives.
I have a field with a lot of data in it. To save disk space, I run it
through compress() and put the compressed data back into the field
before saving the stack. When the stack opens, it uses decompress() to
ext
16 matches
Mail list logo
