Thanks Jeffrey,
but do you or anyone else have any idea about my second question? I still
have no idea why the parser splits my content into three character parts...
sorry if this is a stupid question, but I have no explaination for it.
Holger
Hi Holger,
I will take a look at this, it is quite possible a bug.
Thanks for reporting this,
Jeffrey Rodriguez
IBM Silicon Valley Lab
PDA
>From: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: base64 encoded content
>Date: Thu, 8 Feb 2001 16:24:41 +0100
>
>
>
>Hi,
>
>I'm using the Base64 class to encode and decode binary data in xml files
>and encountered some strange things I hope someone can explain.
>
>If I'm encoding a byte array with a size of 33552 bytes I get an array of
>the length 44736, which seems correct to me. Decoding it returns an array
>with 33553 bytes - one more than the original byte array. This looks like
a
>bug, am I right? If I'm right, does anyone has fixed it already?
>
>The second strange effect occurs while parsing the xml document with the
>encoded data. The document looks like that:
>
> <content>/KJjndlkh/lhjnlkj...</content>
>
>The SAX parser splits my content into three parts, invoking the
>"characters" method three times. Am I doing something wrong?
>
>Thanks for any idea!
>Holger
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
