Re: XML-INTO & embedded blanks

Answering my own query - it is WAD. I have never noticed that although I understand why it is being done.

I've dealt with literally hundreds of people's questions on using XML-INTO and this has never been an issue.

I think an RFE is needed to add a trim option to preserve internal blanks. Biggest issue, and I suspect the reason this is done in the first place, is how to handle other embedded whitespace characters such as carriage return, line-feed, tabs, etc. My feeling is that "real" spaces should be retained and anything else stripped.

As to handling it - I'd just add the none option and preform the trimming yourself. Moving into XML-SAX if you already have this basically working is going to require a lot more effort than simply adding a group of x = %Trim(x) operations.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 9, 2018, at 4:56 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

By default, XML-INTO reduces consecutive embedded blanks to a single blank (ridiculous behavior IMHO). For this reason, I have to disable trimming, so I'm on my own for leading and trailing whitespace.

Are my only options iterating thru my DS array and trimming manually, or switch to XML-SAX?


TIA
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD