RE: XMLSAX procedure parameter length

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Scott,

The PDF has been encoded using base64 encoding.  According to our web group, 
who is supplying the XML file, this is supposed to be a standard practice for 
sending non-text objects using XML.  We've been told that the encoding and 
decoding should be part of any standard XML parser.

I've been working on doing the parsing myself in RPG since we only want a few 
tags but the PDF isn't converting correctly.  Some of the characters ('[' for 
example) aren't converting properly.   We're also losing some characters.  I'm 
hoping that the SAX parser will recognize the encoded PDF and handle the 
decoding for me.  I am wondering if I may still have a conversion issue with 
the output but I won't know until I try.

My latest attempts at the conversion involve using iconv() and some examples of 
yours I found in the archives.  Right now it's returning 0 for bytes converted 
and I'm trying to figure out why.  If you know where I can find better 
documentation than what's in the information center I'd really appreciate it.

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott Klement
Sent: Friday, November 19, 2004 3:55 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: XMLSAX procedure parameter length



> The XML file I am working with has an embedded PDF file that is over
> 100K bytes long.

It has a PDF file embedded inside XML tags?  What happens if there's a <
or > character in the PDF data?  What if there's a non-text character in
the PDF data?  Or is the whole thing encoded so that it's legal?

It would be possible to use eXpat for this -- though my wrapper procedures
are similarly limited to 32k, if you use eXpat directly, there'd be no
limit.

It's a thought, anyway..


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.