Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: MSXML/UTF8 and special characters < 32

From: Marvin Smit <marvin.smit@-----.--->
To: NULL
Date: 8/2/2005 11:53:00 AM
Hi,

and if you want to preserve the exact data as you put in, you'll have
to change the 'non allowed' characters into entities. (e.g. &#18;) (Or
like previously said, Base64 encode it)

Hope this helps,

Marvin Smit.

On Mon, 01 Aug 2005 20:30:49 +0200, "Julian F. Reschke"
<julian.reschke@n...> wrote:

>dblock wrote:
>> Thanks for your reply.
>> 
>> I have a store that I don't control (MAPI) and generate XML in some
>> schema. It encounters special characters (eg. 0x12). My question is:
>> what should I do?
>> 
>> a) Parse every single string and strip special characters?
>
>Yes.
>
>> b) Parse every single string and manually add CDATA whenever I see one
>> of special characters?
>
>That won't help. The set of allowable characters inside CDATA is the same.
>
>> c) Something else?
>
>Depends on your requirements. If you have data that is binary in nature, 
>you may want to base64-encode it. If it's textual data, there's really 
>no compelling reason to have these control characters inside (what is 
>the 0x12 supposed to mean?).
>
>Best regards, Julian



transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent