Broken build: Documentation mistake

[Páli Gábor János]

2015-06-15 23:39 GMT+02:00 Páli Gábor János <pali.gabor at gmail.com>:
> The best result I was able to achive is that I passed the -P
> 'latex.unicode.use=1' flag to dblatex so it could build the PS file.

So, would you mind if I added this flag for dblatex, so it would at
least unbreak the build for me?  That is, consider the following
patch:

--- a/mk/config.mk.in
+++ b/mk/config.mk.in
@@ -731,7 +731,7 @@ BUILD_DOCBOOK_PS         = @BUILD_DOCBOOK_PS@
 BUILD_DOCBOOK_PDF        = @BUILD_DOCBOOK_PDF@
 DBLATEX                  = @DblatexCmd@
 # filename.as.url=0 is needed with dblatex 0.3.4 (#7486)
-DBLATEX_OPTS             = -P 'filename.as.url=0'
+DBLATEX_OPTS             = -P 'filename.as.url=0' -P 'latex.unicode.use=1'
 XSLTPROC                 = @XsltprocCmd@
 XMLLINT                  = @XmllintCmd@
 HAVE_DOCBOOK_XSL        = @HAVE_DOCBOOK_XSL@

I have not yet given up the hope to understand the exact causes, but
this could serve as an interim solution for me until I can solve it --
unless if it breaks something on Ubuntu.

> Note that this way the PS file is generated, but when I checked the
> table in 7.3.1, it had the entity codes in place of the Unicode
> symbols.  May I see the build logs of yours somewhere?

In the meantime, I tried to look up some logs for the referenced
Phabricator builds, but unfortunately they are not run in verbose
mode, so I cannot exactly tell if the PS/PDF versions of the User's
Guide are built or not at all.  (Though, the configure output
indicates that they are.)

Note that the HTML version builds just fine for me as well, as dblatex
simply puts the corresponding Unicode codes right into the generated
files.  The problem is with LaTeX because it cannot handle those codes
-- after studying the sources of both dblatex, passivetex, the latex
ucs package, and the DocBook XML 4.5 entities, I could not yet get how
it is able to work on your system.  That is why it would be good to
see a detailed build log as a reference.