OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: DOCBOOK-APPS: HTML entities (XSL stylesheet 1.39)


----- Original Message -----
From: "Jirka Kosek" <jirka@kosek.cz>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <docbook-apps@lists.oasis-open.org>
Sent: Friday, June 01, 2001 7:24 PM
Subject: Re: DOCBOOK-APPS: HTML entities (XSL stylesheet 1.39)


> Robert Collins wrote:
> >
> > Validating the generated HTML with a faq article, I get the
following:
> >
> > onsgmls -wmin-tag -s cygwin-xfree-faq.html
> > onsgmls:cygwin-xfree-faq.html:337:112:E: "X2018" is not a function
name
> > onsgmls:cygwin-xfree-faq.html:340:40:E: "X2019" is not a function
name
> > onsgmls:cygwin-xfree-faq.html:365:60:E: "X2018" is not a function
name
> > onsgmls:cygwin-xfree-faq.html:365:274:E: "X2019" is not a function
name
> >
> > If I read the HTML 4.01 spec correctly, this is because html expects
> > &lsquo;
> > not
> > &#x2018;
>
> Both variants are correct.

Ahh. Well that's interesting - (o)nsgmls with the HTML DTD (don't have
the version offhand) is returning an error.

> > As far as I can tell this is coming from the common/en.xml
localisation
> > file (overriding dingbat.characters didn't fix it.
> > However, as en.xml covers more than just html, I was wondering about
the
> > best approach to fix this?
>
> Just ignore these messages from parser. If you generate this HTML from
> DocBook, you could trust to stylesheet, additional parsing is not
> necessary IMHO.

Well, if additional parsing isn't needed... why the error? Specifically
there have been errors in Docbook generated output in the past, such as
<div> entries inside <p> entries and the like that result in malformed
html. While that's not a big issue, xhtml is only a small step from
html, but the documents must be well formed.

Secondly, to make a website accessible you need it to render reasonably
on the widest range of browsers, and for text to speech programs
well-formed HTML is essential, as they are more likely to be sensitive
to mistakes that visual browsers.

Rob



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC