Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Validation XSLT using XSLT 1.0

From: "James Fuller" <james.fuller.2007@--------->
To:
Date: 7/3/2008 8:41:00 AM
you might want to see if schematron is a better 'starting point' for
these kinds of validating stylesheets as well.

hth, Jim Fuller

On Thu, Jul 3, 2008 at 10:33 AM, Michael Ludwig <mlu@xxxxxxxxxxxxx> wrote:
> Abel Braaksma schrieb:
>>
>> Michael Ludwig wrote:
>>>
>>>> 3. How to find non-ascii characters in the XML file and report an
>>>> error using XSLT.
>>>
>>> Don't use XSLT for this. Add the following XML declaration to your
>>> input documents:
>>>
>>>    <?xml version="1.0" encoding="us-ascii"?>
>>>
>>> This will ensure the document won't get parsed unless it is pure
>>> ASCII.
>>
>> Yet may still contain higher characters, which then will be escaped
>> using numerical entity references... So, though the file will be
>> US-ASCII, the contents does not necessarily fit in US-ASCII and still
>> get parsed well.
>
> That's true. I was lumping together the notions of character set and
> character encoding.
>
> From the OP's specification, however, it's not entirely clear which one
> is the requirement here. Unless you suppose he'd have written "seven-bit
> clean bytes" instead of "non-ascii characters" had he wanted to talk
> about bytes instead of characters.
>
> Michael Ludwig


transparent
Print
Mail
Like It
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