Re: non-XML characters (e.g. #1) from Dave Pawson on 2022-01-04 (public-ixml@w3.org from January 2022)

From: Dave Pawson <dave.pawson@gmail.com>
Date: Tue, 4 Jan 2022 10:49:19 +0000
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>, ixml <public-ixml@w3.org>
Message-ID: <CAEncD4f5cJPi2K8UNZ7+EhjSNqDJ-w6n_vLaD8V4_6URcEEsew@mail.gmail.com>

On Tue, 4 Jan 2022 at 10:44, Steven Pemberton <steven.pemberton@cwi.nl> wrote:
>
> > > The obvious way to do
> > > this is to mark the relevant terminals as hidden, as in Steven’s example
> > >
> > > -[#0 - #1F]
> >
> > And if the user a) has such input contained within the input and b)
> > has no such rule in the grammar?
>
> Either a) The parse fails because the ixml doesn't properly describe the input or b) The XML fails because the ixml doesn't properly describe the output.
> Steven

From a system perspective, the error is in the ixml application to my
data. This response passes the error
downstream to the xml process?
   Strikes me as a bit Teflon shoulders?

regards



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

Received on Tuesday, 4 January 2022 10:50:43 UTC