[latexrefman-commits] r365 - in /trunk: ChangeLog aspell.en.pws latex2e.texi

[karl at domain.hid]

Author: karl
Date: Fri Jun 19 18:16:36 2015
New Revision: 365

URL: http://svn.gna.org/viewcvs/latexrefman?rev=365&view=rev
Log:
mention geometry package and xdv files

Modified:
    trunk/ChangeLog
    trunk/aspell.en.pws
    trunk/latex2e.texi

Modified: trunk/ChangeLog
URL: http://svn.gna.org/viewcvs/latexrefman/trunk/ChangeLog?rev=365&r1=364&r2=365&view=diff
==============================================================================
--- trunk/ChangeLog	(original)
+++ trunk/ChangeLog	Fri Jun 19 18:16:36 2015
@@ -1,3 +1,13 @@
+2015-06-19  Karl Berry  <karl at domain.hid>
+
+	* latex2e.texi (Document class options): mention the geometry package.
+	(@TeX{} engines) <xelatex>: mention xdv files.
+	(\newcommand & \renewcommand): reorder examples; still in process.
+
+2015-06-18  Karl Berry  <karl at domain.hid>
+
+	* latex2e.texi (\newsavebox): wording.
+
 2015-06-17  Karl Berry  <karl at domain.hid>
 
 	* latex2e.texi (\newfont): put obsolete note earlier.

Modified: trunk/aspell.en.pws
URL: http://svn.gna.org/viewcvs/latexrefman/trunk/aspell.en.pws?rev=365&r1=364&r2=365&view=diff
==============================================================================
--- trunk/aspell.en.pws	(original)
+++ trunk/aspell.en.pws	Fri Jun 19 18:16:36 2015
@@ -62,3 +62,4 @@
 Avant
 Garde
 fd
+xdv

Modified: trunk/latex2e.texi
URL: http://svn.gna.org/viewcvs/latexrefman/trunk/latex2e.texi?rev=365&r1=364&r2=365&view=diff
==============================================================================
--- trunk/latex2e.texi	(original)
+++ trunk/latex2e.texi	Fri Jun 19 18:16:36 2015
@@ -395,12 +395,19 @@
 @item xelatex
 @findex xelatex @r{command}
 @cindex Xe at domain.hid{}
+ at findex .xdv @r{file}
+ at findex xdvipdfmx
 If @LaTeX{} is invoked with the system command @command{xelatex}, the
 Xe at domain.hid{} engine is run (@url{http://tug.org/xetex}).  Like Lua at domain.hid{},
-Xe at domain.hid{} also natively supports UTF-8 Unicode and TrueType and
-OpenType fonts, though the implementation is completely different,
-mainly using external libraries instead of internal code.  Xe at domain.hid{}
-produces a @file{.pdf} file as output; it does not support DVI output.
+Xe at domain.hid{} natively supports UTF-8 Unicode and TrueType and OpenType
+fonts, though the implementation is completely different, mainly using
+external libraries instead of internal code.  Xe at domain.hid{} produces a
+ at file{.pdf} file as output; it does not support DVI output.
+
+Internally, Xe at domain.hid{} creates an @code{.xdv} file, a variant of DVI,
+and translates that to PDF using the (@code{x})@code{dvipdfmx}
+program, but this process is automatic.  The @code{.xdv} file is only
+useful for debugging.
 
 @end table
 
@@ -530,11 +537,16 @@
 a4paper a5paper b5paper executivepaper legalpaper letterpaper
 @end example
 
-When using one of the engines pdf at domain.hid{}, lualatex, or xelatex
-(@pxref{@TeX{} engines}), options other than @code{letterpaper} set the
-print area but you must also set the physical paper size.  One way to do
-that is to put @code{\pdfpagewidth=\paperwidth} and
- at domain.hid} in your document's preamble.
+ at findex \pdfpagewidth
+ at findex \pdfpageheight
+ at cindex @code{geometry} package
+When using one of the engines pdf at domain.hid{}, Lua at domain.hid{}, or Xe at domain.hid{}
+(@pxref{@TeX{} engines}), options other than @code{letterpaper} set
+the print area but you must also set the physical paper size.  One way
+to do that is to put @code{\pdfpagewidth=\paperwidth} and
+ at code{\pdfpageheight=\paperheight} in your document's preamble.  The
+ at code{geometry} package provides flexible ways of setting the print
+area and physical page size.
 
 @findex draft @r{option}
 @findex final @r{option}
@@ -3937,47 +3949,47 @@
 will swallow that space.  The solution is to type @code{@{@}} after the
 command and before the space.
 
+A simple example of defining a new command:
+ at code{\newcommand at domain.hid Hef at domain.hid@}} causes the abbreviation
+ at code{\JH} to be replaced by the longer text.
+
+Redefining a command is basically the same:
+ at code{\renewcommand at domain.hid QED@}@}}.
+
+Here's a command definition that uses arguments:
+
+ at example
+\newcommand at domain.hid@}@}
+ at end example
+
+ at noindent Then, @code{\defreference at domain.hid@}} will expand to
+something like @samp{Definition~3.14}.
+
+An example with two arguments:
+ at code{\newcommand at domain.hid@}} is invoked as
+ at code{\nbym at domain.hid@}}.
+
+An example with optional arguments:
+
+ at example
+\newcommand at domain.hid or Madam]@{Dear #1:@}
+ at end example
+
+ at noindent Then, @code{\salutation} gives @samp{Dear Sir or Madam:} while
+ at code{\salutation[John]} gives @samp{Dear John:}.  And
+ at code{\salutation[]} gives @samp{Dear :}.
+
 The braces around @var{defn} do not delimit the scope of the result of
 expanding @var{defn}.  So @code{\newcommand at domain.hid #1@}}
 is wrong since in the sentence
 
-A simple example of defining a new command:
- at domain.hid Hef at domain.hid@}} causes the abbreviation
- at domain.hid} to be replaced by the longer text.
-
-Redefining a command is basically the same:
- at domain.hid QED@}@}}.
-
-Here's a command definition that uses arguments:
-
- at domain.hid
-\newcommand at domain.hid@}@}
- at domain.hid example
-
- at domain.hid Then, @code{\defreference at domain.hid@}} will expand to
-something like @samp{Definition~3.14}.
-
-An example with two arguments:
- at domain.hid@}} is invoked as
- at domain.hid@}}.
-
-An example with optional arguments:
-
- at domain.hid
-\newcommand at domain.hid or Madam]@{Dear #1:@}
- at domain.hid example
-
- at domain.hid
-Then, @code{\salutation} gives @samp{Dear Sir or Madam:} while
- at domain.hid]} gives @samp{Dear John:}.  And
- at domain.hid[]} gives @samp{Dear :}.
-
 @example
 The \shipname at domain.hid@} met the \shipname at domain.hid@}.
 @end example
 
-the words @samp{met the} will be in italics.  An extra pair of braces
- at domain.hid #1@}@}} fixes it.
+ at noindent the words @samp{met the} will incorrectly be in italics.  An
+extra pair of braces @code{\newcommand at domain.hid #1@}@}}
+fixes it.
 
 
 @node \providecommand 
@@ -4058,18 +4070,19 @@
 @section @code{\newsavebox}
 
 @findex \newsavebox
-
-Allocate a bin for holding a box.  Synopsis:
+ at cindex box, saving
+
+Allocate a ``bin'' for holding a box.  Synopsis:
 
 @example
 \newsavebox at domain.hid}@}
 @end example
 
-Defines @code{\@var{cmd}} to refer to a new bin for storing boxes.  Such
-a box is for holding typeset material, to use multiple times
-(@pxref{Boxes}) or to measure or manipulate.  The name @code{\@var{cmd}}
-is a command name so it must start with a backslash (@samp{\}), and must
-not be already defined.
+Defines @code{\@var{cmd}} to refer to a new bin for storing boxes.
+Such a box is for holding typeset material, to use multiple times
+(@pxref{Boxes}) or to measure or manipulate.  The name
+ at code{\@var{cmd}} must start with a backslash (@samp{\}), and must not
+be already defined.
 
 The allocation of a box is global.  This command is fragile
 (@pxref{\protect}).