[latex3-commits] [git/LaTeX3-latex3-l3build] master: Clarification of how to check the PDF produced by the build system. (6c86352)
Joseph Wright
joseph.wright at morningstar2.co.uk
Thu Dec 13 11:17:41 CET 2018
Repository : https://github.com/latex3/l3build
On branch : master
Link : https://github.com/latex3/l3build/commit/6c863527c4e8e5e871e55142eaac4c8483cfd5ec
>---------------------------------------------------------------
commit 6c863527c4e8e5e871e55142eaac4c8483cfd5ec
Author: Zunbeltz Izaola <zunbeltz at gmail.com>
Date: Thu Dec 13 10:55:49 2018 +0100
Clarification of how to check the PDF produced by the build system.
>---------------------------------------------------------------
6c863527c4e8e5e871e55142eaac4c8483cfd5ec
l3build.dtx | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/l3build.dtx b/l3build.dtx
index b4b13bf..ff3ebf7 100644
--- a/l3build.dtx
+++ b/l3build.dtx
@@ -1145,11 +1145,16 @@
% \item Removal of blank lines
% \end{itemize}
%
+% After this normalization takes place, the file can not usually be rendered
+% properly. To check if the build system has produced a correct PDF, the
+% pre-normalization PDF can be found in the \texttt{build} folder.
+%
% To allow platform-independence, PDF-based tests must use only Type~1 or
% OpenType fonts: Type3 fonts are system-dependent. PDF files are
% engine-specific, thus one |.tpf| file should be stored per engine to be
% tested.
%
+%
% \section{Release-focussed features}
%
% \subsection{Automatic tagging}
More information about the latex3-commits
mailing list