diff options
Diffstat (limited to 'Master/texmf-dist/source/latex/toptesi/toptesi.dtx')
-rw-r--r-- | Master/texmf-dist/source/latex/toptesi/toptesi.dtx | 62 |
1 files changed, 41 insertions, 21 deletions
diff --git a/Master/texmf-dist/source/latex/toptesi/toptesi.dtx b/Master/texmf-dist/source/latex/toptesi/toptesi.dtx index 956b0a358be..8da3fa99462 100644 --- a/Master/texmf-dist/source/latex/toptesi/toptesi.dtx +++ b/Master/texmf-dist/source/latex/toptesi/toptesi.dtx @@ -107,7 +107,7 @@ lines of the file for how-to information. %<topcmn>\ProvidesPackage{topcoman}[% %<topfrn>\ProvidesPackage{topfront}[% %<*driver,class,topsty,topcmn,topfrn> -2015/12/06 v.5.90 +2015/12/18 v.5.91 %<class>Class for typesetting university theses] %<topsty>Extension for toptesi.cls] %<topcmn>Additional commands for the TOPtesi bundle] @@ -671,12 +671,13 @@ lines of the file for how-to information. % of \XeLaTeX, because the typesetting engine in this case cannot directly % produce a PDF formatted output file. Nevertheless even a PDF produced with % \XeLaTeX\ can be made PDF/A compliant; even better, \LuaLaTeX, whose source -% file is practically the same as that of \XeLaTeX, may produce a PDF/A -% compliant output file if the user forces a little bit the compilation. +% file is practically the same as that of \XeLaTeX, may directly produce a PDF/A +% compliant output file if the user uses a little patch described further on. +% The patch is integrated into TOPtesi, and the user might be interested only +% if s/he used a different class to typeset some of the included files. % -% More details are give in the Italian documentation contained in files -% \texttt{toptesi\discretionary{-}{}{-}it-pdftex}, |toptesi-it-xetex|, and -% |toptesi-it-luatex|. +% More details are given in the Italian documentation contained in files +% \texttt{toptesi\discretionary{-}{}{-}it-pdftex}. % % Politecnico di Torino as well as many other Italian and foreign universities % are moving towards archiving theses in electronic format, specifically in the @@ -705,12 +706,12 @@ lines of the file for how-to information. % information, such as the keywords that ease up library searches. % % Since version 1.40, the program \texttt{pdflatex} is capable of producing -% PDF/A-1b conforming files, provided that some attention is put into the +% PDF/A-1b compliant files, provided that some attention is put into the % manipulation of the source file of the thesis. With the distribution of % the 2008 version of the \TeX\ system, the executable \texttt{pdflatex} has % version number 1.40.9 (or higher) and is capable of producing PDF/A-1b files. % -% The particular attention needed to avoid problems with the PDF/A certification +% The particular attention needed to avoid problems with the PDF/A compliance % is summarised as follows: % \begin{enumerate} % \item The preliminary essential requirement is that the \texttt{pdflatex} @@ -725,15 +726,26 @@ lines of the file for how-to information. % into a PS file; at this point you have lost the possibility of exploiting % the internal commands of |pdflatex| version 1.40.9 or later. You can still % produce a PDF/A final document, but you have to transform it by means of -% |ghostscript|; read the |ghostscript| (version 8.61 or later) documentation -% file |ps2pdf.html| in order to find out how to produce the correct PS to -% PDF/A transformation. A procedure similar to this one is available when +% |ghostscript|; read the |ghostscript| (version 9.16 or later) documentation +% file |ps2pdf.html| in order to find out how to produce the correct +% PS-to-PDF/A transformation. A procedure similar to this one is available when % the thesis is typeset by means of \XeLaTeX, and produces valid results % provided some caution is exercised when using fonts. The documentation in % Italian describes several methods to transform a non compliant PDF/A file % into a compliant one, and how to correct the ``imperfections'' that forbid % any valid transformation. % +% \item As said before, \prog{lualatex} is not fully compatible with package +% \pack{pdfx}, because in spite of having a typesetting engine that has +% a strong resemblance with \prog{pdftex} it does not contain all its +% primitives; in particular it misses the \cs{pdfmdfivesum} primitive. In +% order to supply a patch it is necessary to load the package \pack{pdftexcmds} +% that defines some macros that emulate the missing \prog{pdftex} primitives +% by means of macros. This patch is already integrated into TOPtesi, so when +% the user typesets his/her thesis with \prog{LuaLaTeX}, non ``undefined +% control sequence'' errors show up, and their functionality is preserved by +% means of the above patch. +% % \item Your up-to-date complete \TeX\ distribution should contain the package % \textsf{pdfx}; if it does not, upgrade your \TeX\ system complete % distribution. @@ -749,8 +761,8 @@ lines of the file for how-to information. % \Title{Experiments in Trichotetratomy} % \Author{John Smith} % \end{verbatim} -% Keywords require a specific XML style format that can be examined in the -% package documentation. +% The keyword list requires a specific format that can be examined +% in the package documentation. % % \item Some mathematical symbol commands obtained from the standard \LaTeX\ % set-up and the standard mathematical fonts require some patching that is @@ -758,7 +770,7 @@ lines of the file for how-to information. % that with other fonts similar patches might be requested. The UNICODE % math fonts used by \XeLaTeX\ do not require any patch, but unfortunately % its PDF byproduct is not PDF/A compliant (it must be converted by means -% of \prog{ghostscript}). +% of \prog{ghostscript}). With \LuaLaTeX\ there are no problems with fonts. % % \item Use only PNG and JPEG images with RGB color profiles. % @@ -793,9 +805,10 @@ lines of the file for how-to information. % strong chances that if you follow the general recommendations shown here % and in the document |toptesi-it-xetex.pdf| file, the output file will be % PDF/A compliant. +% % \item If you really have to typeset your document with \prog{xelatex} because % you have to use Opentype fonts or you have to manage languages in a -% different way from what you can di with |babel|, then prefer using +% different way from what you can do with |babel|, then prefer using % \prog{lualatex}, even if you have to force the compilation; formally % \LuaLaTeX\ and package \pack{pdfx} are incompatible (by the end of 2015), % but if at the first error you force the continuation of the compilation @@ -815,8 +828,8 @@ lines of the file for how-to information. % in the free nature of the \prog{pdflatex}, \prog{xelatex}, and \prog{lualatex} % programs, that, on the opposite, according to my experience have a very high % rate of success in producing PDF/A compliant documents. If you stick to the -% default \TeX\ system Type~1 256-glyph, or to the UNICODE encoded otf or ttf -% fonts and use this patched version of \texttt{TOPtesi} you should be able +% default \TeX\ system Type~1 256-glyph fonts, or to the UNICODE encoded otf +% or ttf fonts and use this patched version of \texttt{TOPtesi} you should be able % to avoid most problems. % % \StopEventually{} ^^A Bibliography? @@ -951,7 +964,13 @@ Read documentation toptesi-it-*.pdf, because package pdfx has changed}} % inserting the university logo(s); if the user forgets that this package has % already been loaded nothing dramatic happens, because the |\usepackage| % and |\RequirePackage| macros perform the necessary tests in order to avoid -% reloading the same packages again and again. +% reloading the same packages again and again. In order to produce PDF/A +% compliant files the necessary patches are very simple, but must be done +% directly into a personal copy of the \pack{pdfx} package; see the Italian +% documentation about this point. This notice is done here because this would +% have been a convenient point to introduce the initial single patch I +% found; but this patch by itself is not sufficient. +% % \begin{macrocode} \RequirePackage{graphicx} \RequirePackage{etoolbox} @@ -2316,7 +2335,8 @@ Skipping any redefinition\MessageBreak}% \setlength\interno{\dimexpr\paperwidth/7}}{} \newcommand\logosede[2][\interno]{\def\@logosede{#2}\TPT@logoheight=#1\relax -\ifcsvoid{@logosede}{\sbox{\TPT@logobox}{}}{\begin{lrbox}{\TPT@logobox}\expandafter\fillup@TCP@logobox\@logosede,!}} +\ifcsvoid{@logosede}{\sbox{\TPT@logobox}{}}{\begin{lrbox}{\TPT@logobox}% +\expandafter\fillup@TCP@logobox\@logosede,!}} \def\fillup@TCP@logobox#1,#2!{% \ifblank{#1}{\end{lrbox}\ifdim\wd\TPT@logobox>\textwidth @@ -2357,8 +2377,8 @@ Skipping any redefinition\MessageBreak}% % \Item[CycleName] ``ciclo'' in, say, ``cycle'' % \Item[NomePrimoTomo] ``Tomo primo'' in, say, ``First volume'' % \Item[NomeSecondoTomo] ``Tomo secondo'' in, say, ``Second volume'' -% \item[NomeTerzoTomo] ``Tomo terzo'' in, say, ``Third volume'' -% \item[NomeQuartoTomo] ``Tomo quarto'' in, say, ``Fourth volume'' +% \Item[NomeTerzoTomo] ``Tomo terzo'' in, say, ``Third volume'' +% \Item[NomeQuartoTomo] ``Tomo quarto'' in, say, ``Fourth volume'' % \end{description} % In the above description the first string is generally the default one, % while the second string is just an example of the corresponding string |