Why don't we go UTF-8 ?

I tried it on my working copy, and it seems to work :

In short, I use Linux Ubuntu 18.04 LTS and my java version is 10.0.2, and my locale is fr_FR.UTF-8

I edit my XML files in UTF-8 with gvim editor.

First, I had to delete Xbootclasspath option of java command in build.sh file from the build tools in order to be able to build the doc with my java version.

Then, I replaced all occurence of "ISO-8859-1" by "UTF-8" in following files :

manual/style/manual.en.xsl
manual/style/manual.fr.xsl
manual/style/xsl/util/designations.xml
manual/style/xsl/list_for_prettify.xsl
manual/style/xsl/convmap.xsl
manual/style/lang/fr.xml
manual/style/lang/en.xml
manual/style/latex/latex.xsl

Yet, man pages are correctly generated, and there are no more HTML entities in html files.

UTF-8 could be used for all langages (some use it already - ja, tr)



Le 25/09/2018 à 10:10, Joe Orton a écrit :
On Mon, Sep 24, 2018 at 08:45:02PM +0200, Christophe JAILLET wrote:
If java 9+, then have a look at 
https://lists.apache.org/thread.html/039a5815481ac297931cd08e759a90388a620eb6ea7aaecfcf97457f@%3Cdocs.httpd.apache.org%3E

The issue with man pages is reported (with a possible work-around at the
end), as well as the output of entities in the generated files.
I have Java 8 only (OpenJDK 1.8.0_181-b15).  Yes, the man pages are
definitely unusable when composed entirely of HTML entities ;)

What is expected in the manual/*.html.XX files, entities or ISO-8859-1
characters?  AFAICT either should be fine, the ISO-8859-1 characters
look correct to me everywhere I checked, and the HTML files have

<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"
/>

so I don't see why we can't use ISO-8859-1 characters there?

Can we fudge build.sh to fail with Java 9 if that is what is breaking
everything at the moment, and rely on people with Java 8 to regenerate
the docs?

Regards, Joe


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


Reply via email to