Re: xml file with invalid characters at the start of the stream file

Yes! Byte order marks exist in two versions: Little Endian (say Intel
Processors and Big Endian, say Power i processors). Search on
Wikipedia what Endiannes is, that is an indication of how the bytes must be
treated by software written for those types of processors. It has to do
with the ordering of bytes in stream files.

JS



El mar, 19 nov 2024 a las 19:20, Don Brown via MIDRANGE-L (<
midrange-l@xxxxxxxxxxxxxxxxxx>) escribió:

I am sure I have seen this question asked before but searching has not
found it.

We are using httpapi to retrieve a list of files that is returned in xml

The xml file saved to the ifs has the following leading characters that
then results into xml-into failing.

<?xml version="1.0" encoding="utf-8"?>

In case these characters get corrupted in the email / forum they are hex
x'EFBBBF'

A valid xml file must start with a < so we can't just blank these
characters out.

And xml-into does not allow a substring that I have found.

So if I can't stop the invalid characters how would I shift the contents
of the stream file left by 3 characters or I expect there is a better
option ?

Thank you to any suggestions or examples.

Cheers

Don



--
This email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email, MSD
cannot accept responsibility for any loss or damage arising from the use of
this email or attachments..

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.