Hi Adam,
You might want to do a search of the mailing list archives, because I
remember a previous discussion about this and it related to how XML schema
specifies Base64 should work:
http://marc.theaimsgroup.com/?l=xerces-c-dev&w=2&r=1&s=base64&q=b
This may or may not be relevant...
Dave
|---------+--------------------------->
| | "Adam Heinz" |
| | <[EMAIL PROTECTED]|
| | .com> |
| | |
| | 10/21/2003 01:26|
| | PM |
| | Please respond |
| | to xerces-c-dev |
|---------+--------------------------->
>--------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: <[EMAIL PROTECTED]>
|
| cc: (bcc: David N Bertoni/Cambridge/IBM)
|
| Subject: base64 encoding
|
>--------------------------------------------------------------------------------------------------------------------------------|
Has anyone attempted to use Xerces' Base64 output with another Base64
encoder? I have a Visual Basic project which is forcing me to use
Microsoft's CAPICOM Base64 encoding, and I'm getting some strange results.
I can take CAPICOM-encoded output and successfully decode it with Xerces,
but not vice versa. For a test, I encoded the same bitmap with both Xerces
and CAPICOM, and the Base64 text differs. However, if I decode both
CAPICOM-encoded and Xerces-encoded Base64 with Xerces, the resulting binary
files are identical. I haven't really attempted to understand the Base64
algorithm beyond the basic 3-to-4 mapping. How much flexibility is in the
standard? Recommendations on how to get CAPICOM to ingest my
Xerces-encoded output is beyond the purview of this list, but any
recommendations on tools to validate the Base64, etc?
Adam Heinz
Development Consultant
Exstream Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
