On Sat, Sep 29, 2018 at 3:03 AM Christophe JAILLET <christophe.jail...@wanadoo.fr> wrote: > > Hi, > > There is a bug in the Xalan, the XSLT 1.0 engine we are using, that > prevents our doc building tool chain to generate correct documentation. > > By not correct, I mean: > - ISO-8859-1 non ASCII characters are replaced again by their HTML > entities equivalent (in the French doc for example) > - breaks the man pages generation > > A possible workaround is to use UTF-8 instead of ISO-8859-1. > The only drawback I see, is that some html files will be slightly bigger > and a bit less readable because of the use of entities. This is not a > that big problem. >
I feel foolish but I just realized a few things that should have been obvious: - you have to run `extraclean` to reliably see results when you change anything - the churn that bites me and recently Mike is about links from languages we choose to use non-utf8 for linking to languages we choose to utf-8 for -- This means the "java11" behavior is more correct Are there any known breaks for using utf-8 for English? Can we take that baby step safely and add something to the docs-build build to verify some key output files look correct? Maybe blocking old java with e.g. -source that will blow up? --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org For additional commands, e-mail: docs-h...@httpd.apache.org
