texlive[50157] Master/texmf-dist/doc/dvipdfmx: update documents for

[commits+kakuto at tug.org]

Revision: 50157
          http://tug.org/svn/texlive?view=revision&revision=50157
Author:   kakuto
Date:     2019-02-28 01:49:33 +0100 (Thu, 28 Feb 2019)
Log Message:
-----------
update documents for [x]dvipdfmx

Modified Paths:
--------------
    trunk/Master/texmf-dist/doc/dvipdfmx/dvipdfmx.pdf
    trunk/Master/texmf-dist/doc/dvipdfmx/dvipdfmx.tex

Modified: trunk/Master/texmf-dist/doc/dvipdfmx/dvipdfmx.pdf
===================================================================
(Binary files differ)

Modified: trunk/Master/texmf-dist/doc/dvipdfmx/dvipdfmx.tex
===================================================================
--- trunk/Master/texmf-dist/doc/dvipdfmx/dvipdfmx.tex	2019-02-28 00:46:48 UTC (rev 50156)
+++ trunk/Master/texmf-dist/doc/dvipdfmx/dvipdfmx.tex	2019-02-28 00:49:33 UTC (rev 50157)
@@ -102,7 +102,7 @@
   \begin{raggedleft}
     {\Huge\bfseries The Dvipdfmx User's Manual}\\[\baselineskip]
     \Large The Dvipdfmx Project Team\\
-    August 30, 2018\par
+    December 23, 2018\par
   \end{raggedleft}
 \end{titlepage}
 
@@ -262,7 +262,7 @@
 \XeTeX\ users
 normally do not invoke the \dvipdfmx\ command directly. To control the
 behavior of \dvipdfmx, please consider using the \code{dvipdfmx:config}
-special explained in the section of ``\hyperref[SEC:specials]{Specials}.''
+special explained in the section of ``\hyperref[SEC:specials]{Specials}''.
 Some part of this document is irrelevant for \XeTeX\ users.
 
 \subsection{p\TeX}
@@ -404,7 +404,7 @@
 
 CJK fonts usually contain several thousands of glyphs. For using such fonts
 with (original) \TeX, which can only handle 8-bit encodings, it is necessary to
-split a font into several ``subfonts''. Subfont Definition File (SFD)
+split a font into several \keyword{subfonts}. The Subfont Definition File (SFD)
 specify the way how those fonts are split into subfonts. \dvipdfmx\ uses SFD
 files to convert a set of subfonts back to a single font.
 
@@ -967,7 +967,7 @@
 mandatory and a dictionary object, following the filename, which is to be added
 to the stream dictionary is optional.
 
-For example, to incorporate XMP Metadata stored from the file \code{test.xmp},
+For example, to incorporate XMP Metadata from a file \code{test.xmp},
 \begin{lstlisting}
 \special{pdf:fstream @xmp (test.xmp) <<
     /Type    /Metadata
@@ -1031,7 +1031,7 @@
 pdf:mapfile foo.map
 \end{lstlisting}
 
-\subsubsection{Specifying The Output PDF Version}
+\subsubsection{Specifying Output PDF Version}
 
 \code{pdf:majorversion} and \code{pdf:minorversion} specials can be used to
 specify major and minor version of output PDF.
@@ -1039,6 +1039,21 @@
 pdf:minorversion 3
 \end{lstlisting}
 
+Please note that this command must appear on the first page,
+otherwise it will be ignored.
+
+\subsubsection{Custom File Identifiers}
+
+\newfeature{Addition in \TeX\ Live 2019}
+
+A custom file identifier (the \code{ID} entry in the trailer dictionary)
+can be specified via \code{pdf:trailerid} special as
+\begin{lstlisting}
+pdf:trailerid [(0123456789abcdef) (0123456789abcdef)]
+\end{lstlisting}
+An array of two 16-byte PDF string objects must be supplied as
+a file identifier. This special command must appear on the first page.
+
 \subsubsection{Encryption}
 
 To protect output PDF with encryption, use \code{pdf:encrypt} special
@@ -1130,7 +1145,7 @@
 
 If the name of conversion CMap contains one of the keywords RKSJ, \lnum{B5}, GBK, and KSC,
 PDF string objects are treated specially when they are parsed. A two byte sequence
-starting with the first byte's high bit set is treated ''as is'' so that
+starting with the first byte's high bit set is treated ``as is'' so that
 the \code{0x5c} byte appears in the second byte is not treated as an escape sequence.
 This behavior is not compliant to the PDF specification.
 
@@ -1139,7 +1154,7 @@
 This section shows several examples of special command usage.
 It is intended to be a hint for advanced users, so uninterested users can safely skip
 this section. In many cases, using \dvipdfmx\ PDF specials requires knowledge on PDF.
-Please refer to Adobe's ''PDF Reference''\cite{ADOBE}.
+Please refer to Adobe's ``PDF Reference''\cite{ADOBE}.
 
 \subsubsection{Annotations}
 
@@ -1714,7 +1729,7 @@
 \end{lstlisting}
 
 For information on the Adobe Glyph List and PostScript CMap Resources, see,
-the section \ref{SEC:auxfiles}, ``Auxiliary Files.''
+the section \ref{SEC:auxfiles}, ``Auxiliary Files''.
 
 \subsection{Extended Syntax and Options}
 
@@ -1945,7 +1960,7 @@
 when creating a document can be recorded.%
 \footnote{See,
 ``\href{http://www.microsoft.com/typography/otspec/os2.htm}{OpenType Specification:
-OS/2 -- OS/2 and Windows Metrics Table}''.}
+OS/2 -- OS/2 and Windows Metrics Table}''}.
 \dvipdfmx\ uses this information to decide whether font embedding is permitted.
 
 This font licensing information is indicated by the flag called \code{fsType}
@@ -2174,7 +2189,7 @@
 %\renewcommand{\refname}{Further Reading}
 \renewcommand{\bibname}{Further Reading}
 \begin{thebibliography}{99}
-\bibitem{DVIPDFM}  ''\href{http://mirrors.ctan.org/dviware/dvipdfm/dvipdfm.pdf}%
+\bibitem{DVIPDFM} ``\href{http://mirrors.ctan.org/dviware/dvipdfm/dvipdfm.pdf}%
 {Dvipdfm User's Manual}'' written by Mark~A.~Wicks.
 \bibitem{ADOBE} Adobe's PDF References and a free copy of
 \lnum{ISO 32000-1:2008} standard are available from
@@ -2184,7 +2199,7 @@
 site:
 ``\href{http://www.microsoft.com/en-us/Typography/OpenTypeSpecification.aspx}%
 {OpenType Specification}''.
-\bibitem{PNGSPEC} ''\href{https://www.w3.org/TR/2003/REC-PNG-20031110/}%
+\bibitem{PNGSPEC} ``\href{https://www.w3.org/TR/2003/REC-PNG-20031110/}%
 {Portable Network Graphics (PNG) Specification (Second Edition)}''.
 \bibitem{CHOF} An article regarding DVI specials: Jin-Hwan Cho,
 ``\href{http://www.tug.org/TUGboat/tb30-1/tb94cho.pdf}{DVI specials for PDF generation}'',