---
I do reproduce this on my Debian machine when building the PDF
documentation. As Michael says after double-checking it's indepdent of
whether using build parallelism.
This patch makes the doc build run to completion, but in the resulting
pdf file non-ASCII characters aren't present. The build prints on the
terminal lots of messages like
Character U+F3 (รณ) not in font 'phvr7t'
As a result, the non-English files are going to be irritating at a
minimum; the badness may range all the way up to "unusable" if you
aren't good at guessing words with letters missing.
This will require further attention from someone who will plumb the
depths of a2x, I fear.
docs/src/Submakefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/src/Submakefile b/docs/src/Submakefile
index f8adda1..9750ea6 100644
--- a/docs/src/Submakefile
+++ b/docs/src/Submakefile
@@ -342,7 +342,7 @@ A2X = a2x --xsltproc-opts "--stringparam toc.section.depth
3 \
--asciidoc-opts "-f $(DOC_SRCDIR)/docbook.conf -f
$(DOC_SRCDIR)/asciidoc-dont-replace-arrows.conf" \
--dblatex-opts "-P doc.publisher.show=0 -P latex.output.revhistory=0
-s $(DOC_SRCDIR)/emc2.sty \
-P
latex.hyperparam=colorlinks,linkcolor=blue,filecolor=blue,urlcolor=blue,citecolor=blue
\
- -P latex.encoding=utf8"
+ -P latex.encoding=utf8x"
ifeq ($(TRIVIAL_BUILD),no)
-include $(patsubst %.txt, depends/%.d, $(DOC_SRCS_TXT))
--
1.7.10.4
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
