Masamichi-san? Any idea?
Knut Petersen <address@hidden> writes:
This problems seems to be related to https://codereview.appspot.com/314130043/
The file http://lilypond.org/doc/v2.19/Documentation/notation.pdf seems to be
the intermediate version of notation.pdf.
pdfinfo shows:
Creator: XeTeX output 2018.06.24:1343
Producer: xdvipdfmx (0.7.9)
CreationDate: Sun Jun 24 14:43:19 2018 CEST
'Producer: xdvipdfmx' is unxpected and definitely broken.
The file http://lilypond.org/doc/v2.19/Documentation/notation.de.pdf is the
expected final version of notation.de.pdf
pdfinfo shows:
Creator: XeTeX output 2018.06.24:1347
Producer: GPL Ghostscript 9.21
CreationDate: Sun Jun 24 14:47:40 2018 CEST
ModDate: Sun Jun 24 14:47:40 2018 CEST
The intermediate pdfs should have been processed with extractpdfmark
and ghostscript according to this snippet from texinfo-rules.make:
$(outdir)/%.pdf: $(outdir)/%.texi $(outdir)/version.itexi
$(outdir)/%.pdf.omf $(outdir)/weblinks.itexi | $(OUT_TEXINFO_MANUALS)
ifeq ($(WEB_VERSION),yes)
PDFTEX=$(PDFTEX) PDFLATEX=$(PDFLATEX) $(buildscript-dir)/run-and-check "cd $(outdir);
texi2pdf $(TEXI2PDF_FLAGS) -D web_version -I $(abs-src-dir) $(TEXINFO_PAPERSIZE_OPTION) $(<F) <
/dev/null" "$*.texi2pdf.log"
else
PDFTEX=$(PDFTEX) PDFLATEX=$(PDFLATEX) $(buildscript-dir)/run-and-check "cd $(outdir);
texi2pdf $(TEXI2PDF_FLAGS) -I $(abs-src-dir) $(TEXINFO_PAPERSIZE_OPTION) $(<F) < /dev/null"
"$*.texi2pdf.log"
endif
ifeq ($(USE_EXTRACTPDFMARK),yes)
$(EXTRACTPDFMARK) -o $(outdir)/$*.pdfmark $@
$(GS920) -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -dAutoRotatePages=/None
-sOutputFile=$(outdir)/$*.final.pdf -c "30000000 setvmthreshold" -f
$(top-build-dir)/out-fonts/*.font.ps $(outdir)/$*.pdfmark $@
rm $@
mv $(outdir)/$*.final.pdf $@
endif
Apparently that worked for notation.de.pdf but not for notation.pdf. Why? At
the moment I don't see the reason, maybe it's too late.
@Masamichi: Any idea ?
Any non-pattern rule overriding? Stuff getting copied before being
finished because of bad parallelism? $@ stripping .de. stuff and
similar so that everything is going through the same temporary file (not
likely I guess) At any rate, it doesn't seem to be related to your
recent patches.