On Mittwoch, 8. Januar 2020 22:33:19 CET Christophe JAILLET wrote: > Hi Eric, > > I was just about to remind @dev about this known issue. > > Yes, interested to dig further, but honestly, I lack time since several > months. > If I recollect correctly: > - there is still some corner issues with saxon. (and a few patches > already in trunk, waiting for 2.4.x) > - it is not possible to handle both saxon and xalan, because of some > incompatible syntax > > The main issue about entities generated with latest java in that it > breaks man pages. > > As pointed out by Lucien, using UTF-8 is a solution that has already > been used for the French, and Spanish if I remember correctly. > > However, I think that there could still be an issue with man pages > generation. > With the latest java, it is just garbage, but using UTF-8 in man.en.xsl > seems to work. > > How-ever I'm not sure that the UTF-8 "trick" would work in all build > targets (chm, zip, war, latex which are certainly used by no one but > still available). I also don't know if they are broken or still of any > use.
chm and zip I'd keep (they should be in use), war can certainly be killed. The chm format cannot handle UTF-8 though. If you'd ask me, I'd rather kill XML/XSLT entirely, as the promises both for Java and XML/XSLT clearly don't hold anymore. However this also requires time and effort... Cheers, nd -- Flhacs wird im Usenet grundsätzlich alsfhc geschrieben. Schreibt man lafhsc nicht slfach, so ist das schlichtweg hclafs. Hingegen darf man rihctig ruhig rhitcgi schreiben, weil eine shcalfe Schreibweise bei irhictg nicht als shflac angesehen wird. -- Hajo Pflüger in dnq --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
