[latexrefman-commits] [SCM] latexrefman updated: r1163 - trunk

Karl Berry INVALID.NOREPLY at gnu.org.ua
Wed Oct 11 18:05:32 CEST 2023


Author: karl
Date: 2023-10-11 16:05:32 +0000 (Wed, 11 Oct 2023)
New Revision: 1163

Modified:
   trunk/ChangeLog
   trunk/Makefile
   trunk/NEWS
   trunk/aspell.en.pws
   trunk/latex2e.texi
Log:
(Ligatures): new node

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog	2023-10-04 16:15:57 UTC (rev 1162)
+++ trunk/ChangeLog	2023-10-11 16:05:32 UTC (rev 1163)
@@ -1,3 +1,7 @@
+2023-10-11  Karl Berry  <karl at freefriends.org>
+
+	* latex2e.texi (Ligatures): new node.
+
 2023-10-04  Karl Berry  <karl at freefriends.org>
 
 	* latex2e.texi (Special characters): new node.

Modified: trunk/Makefile
===================================================================
--- trunk/Makefile	2023-10-04 16:15:57 UTC (rev 1162)
+++ trunk/Makefile	2023-10-11 16:05:32 UTC (rev 1163)
@@ -204,12 +204,12 @@
 # Remove \commandnames to reduce exception list, but not {args} or
 # [args], since they are often words.
 spell spell-en:
-	sed -e 's/\\[a-zA-Z]*//g' latex2e.texi \
+	sed -e 's/\\[a-zA-Z]*//g' -e 's/U+[0-9A-F]\{4\}//' latex2e.texi \
 	| aspell list --mode=texinfo --add-extra-dicts=`pwd`/aspell.en.pws \
         | sort -f -u
 
 # Check for doubled words.
-# http://www.math.utah.edu/~beebe/software/file-tools.html#dw
+# https://www.math.utah.edu/~beebe/software/file-tools.html#dw
 # The first sed expression elides a few @-command lines which cause
 # duplicates; the second expr some text in the middle of lines.
 check-dw:

Modified: trunk/NEWS
===================================================================
--- trunk/NEWS	2023-10-04 16:15:57 UTC (rev 1162)
+++ trunk/NEWS	2023-10-11 16:05:32 UTC (rev 1163)
@@ -11,7 +11,8 @@
 * \thepage for page number representation.
 * \nobreakspace and U+00A0 synonyms for ties.
 * The (simple) \slash command.
-* Brief description of LaTeX's special characters (\ @ @ % $ & _ ^ # ~}.
+* List the standard ligatures in LaTeX (ff fi fl ffi ffl `` '' -- --- `! `?).
+* Describe LaTeX's special characters (\ @ @ % $ & _ ^ # ~}.
 * Briefly mention hilatex and the hitex engine (https://ctan.org/pkg/hitex).
 
 Changes:

Modified: trunk/aspell.en.pws
===================================================================
--- trunk/aspell.en.pws	2023-10-04 16:15:57 UTC (rev 1162)
+++ trunk/aspell.en.pws	2023-10-11 16:05:32 UTC (rev 1163)
@@ -294,3 +294,4 @@
 envname
 un
 documentmetadata
+ffl

Modified: trunk/latex2e.texi
===================================================================
--- trunk/latex2e.texi	2023-10-04 16:15:57 UTC (rev 1162)
+++ trunk/latex2e.texi	2023-10-11 16:05:32 UTC (rev 1163)
@@ -12,7 +12,7 @@
 @c xx random list of a few of the missing items is at the end of this file
 @c xx read through ltnews and l3news for (lots of) things to update.
 @c
- at c xx ctan, distributions, components of TeX
+ at c xx distributions, components of TeX
 @c xx classes and packages: required, additional, useful; oberdiek; fonts
 @c xx merge permuted-index
 @c xx merge latex-manual from savannah
@@ -23,8 +23,8 @@
 @c xx JH explain nfss somewhere
 @c xx JH expand BiBTeX
 @c xx JH expand theorem, AMS math
- at c xx JH something on code listings
 @c xx JH ligatures
+ at c xx \verbatiminput
 @c
 @c xx \NewCommandCopy et al. (Brian Dunn, 21 Dec 2021 06:50:17).
 @c
@@ -580,7 +580,182 @@
 @node Input text
 @section Input text
 
+To a first approximation, most input characters in @LaTeX{} print as
+themselves. But there are exceptions, as discussed in the following
+sections.
 
+ at menu
+* Input encodings::
+* Ligatures::            Combined characters: ff fi fl ffi ffl `` '' -- --- `! `?
+* Special characters::   With special meaning: @code{\ @{ @} % $ & _ ^ # ~}
+ at end menu
+
+ at node Input encodings
+ at subsection Input encodings
+
+ at cindex input encodings
+ at cindex encodings, input
+
+qqq
+
+
+ at node Ligatures
+ at subsection Ligatures
+
+ at cindex ligatures
+
+A @dfn{ligature} combines two or more letters (more generally,
+characters) into a single glyph.  For example, in Latin-based
+typography, the two letters @samp{f} and @samp{i} are often combined
+into the glyph `fi'.  
+
+ at TeX{} supports ligatures automatically. To continue the example, if
+the input has the word @samp{fine}, written as four separate ASCII
+characters, @TeX{} will output the word `fine' (with the default
+fonts).
+
+In traditional @TeX{}, the available ligatures, if any, are defined by
+the current font.  @TeX{} also uses the ligature mechanism to produce
+a few typographical characters which were not available in any
+computer encoding when @TeX{} was invented (or for many years
+afterward).  In the original Computer Modern fonts, the following
+input character sequences are defined to lead to ligatures, as shown:
+
+ at cindex f-ligatures
+ at cindex double quotation marks, as ligatures
+ at cindex quotation marks, as ligatures
+ at cindex en-dash, as ligature
+ at cindex em-dash, as ligature
+ at cindex inverted exclamation mark, as ligature
+ at cindex inverted question mark, as ligature
+ at cindex Spanish exclamation mark, as ligature
+ at cindex Spanish question mark, as ligature
+
+ at table @samp
+ at item ff
+ff
+ at item fi
+fi
+ at item fl
+fl
+ at item ffi
+ffi
+ at item ffl
+ffl
+ at item ``
+`` (left double quotation mark, U+201C)
+ at item ''
+'' (right double quotation mark, U+201D)
+ at item --
+-- (en-dash, U+2013)
+ at item ---
+--- (em-dash, U+2014)
+ at item !`
+!` (inverted exclamation mark, U+00A1)
+ at item ?`
+?` (inverted question mark, U+00BF)
+ at end table
+
+Nowadays it's usually possible to directly input the punctuation
+characters as Unicode characters, and @LaTeX{} supports that (see
+previous section).  But even today, it can still often be useful to
+use the ASCII ligature input form; for example, the difference between
+an en-dash and em-dash, as a single glyph, can be all but impossible
+to discern, but the difference between two and three ASCII hyphen
+characters is clear.  Similarly with quotation marks, in some fonts.
+
+Thus, even the engines with native support for UTF-8, namely Lua at TeX{}
+and Xe at TeX{}, also support the ASCII ligature input by default.  They
+also need to do so for compatibility.
+
+ at cindex alphabetic presentation forms Unicode block
+By the way, the f-ligatures are also available in Unicode (the
+``Alphabetic Presentation Forms'' block starting at U+FB00), but it's
+almost never desirable to use them as input characters, since in
+principle it should be up to the typesetter and the current font
+whether to use ligatures.  Also, in practice, using them will
+typically cause searches to fail, that is, a search for the two
+characters @samp{fi} will not be matched by the ligature `fi' at
+U+FB02.
+
+
+ at node Special characters
+ at subsection Special characters: @code{\ @{ @} % $ & _ ^ # ~}
+
+ at anchor{Reserved characters}@c old node name
+ at cindex reserved characters, meaning of
+ at cindex special characters, meaning of
+ at cindex meaning of special characters
+
+Besides ligatures (see previous section), a few individual characters
+have special meaning to @LaTeX{}. They are called @dfn{reserved
+characters} or @dfn{special characters}.  Here they are:
+
+ at table @samp
+ at item \
+ at findex \ @r{character}, meaning of
+ at cindex backslash, meaning of
+Introduces a command name, as seen throughout this manual.
+
+ at item @{
+ at itemx @}
+ at findex @{ @r{character}, meaning of
+ at findex @} @r{character}, meaning of
+ at cindex left brace, meaning of
+ at cindex right brace, meaning of
+ at cindex braces, meaning of
+ at cindex curly braces, meaning of
+Delimits a required argument to a command or a level of grouping, as
+seen throughout this manual.
+
+ at item % 
+ at findex % @r{character}, meaning of
+ at cindex percent character, meaning of
+Starts a comment; the @samp{%} and all remaining characters on the
+current line are ignored.
+
+ at item $
+ at findex $ @r{character}, meaning of
+ at cindex dollar sign character, meaning of
+Starts and ends math mode (@pxref{Math formulas}).
+
+ at item &
+ at findex & @r{character}, meaning of
+ at cindex ampersand character, meaning of
+Separates cells in a table (@pxref{tabular}).
+
+ at item _ 
+ at itemx ^
+ at findex _ @r{character}, meaning of
+ at findex ^ @r{character}, meaning of
+ at cindex underscore character, meaning of
+ at cindex hat character, meaning of
+ at cindex caret character, meaning of
+Introduce a subscript or superscript in math (@pxref{Subscripts &
+superscripts}); they produce an error outside math mode.
+As a little-used special feature, two superscript characters in a row
+can introduce special notation for an arbitrary character;
+ at pxref{Input text}.
+
+ at item # 
+ at findex # @r{character}, meaning of
+ at cindex number sign character (@code{#}), meaning of
+ at cindex sharp character (@code{#}), meaning of
+ at cindex hash character (@code{#}), meaning of
+Stands for arguments in a macro definition (@pxref{\newcommand &
+\renewcommand}).
+
+ at item ~ 
+ at findex ~ @r{character}, meaning of
+ at cindex tilde character, meaning of
+Produces a nonbreakable interword space (@pxref{~}).
+
+ at end table
+
+ at xref{Printing special characters}, for how to typeset these
+characters when you need them literally.
+
+
 @node @LaTeX{} command syntax
 @section @LaTeX{} command syntax
 
@@ -673,83 +848,6 @@
 @end example 
 
 
- at node Special characters
- at section Special characters: @code{\ @{ @} % $ & _ ^ # ~}
-
- at anchor{Reserved characters}@c old node name
- at cindex reserved characters, meaning of
- at cindex special characters, meaning of
- at cindex meaning of special characters
-
-Most input characters in @LaTeX{} print as themselves (to a first
-approximation; @pxref{Input text}), but a few have a special
-meaning to @LaTeX{}. They are called @dfn{reserved characters} or
- at dfn{special characters}.  Here they are:
-
- at table @samp
- at item \
- at findex \ @r{character}, meaning of
- at cindex backslash, meaning of
-Introduces a command name, as seen throughout this manual.
-
- at item @{
- at itemx @}
- at findex @{ @r{character}, meaning of
- at findex @} @r{character}, meaning of
- at cindex left brace, meaning of
- at cindex right brace, meaning of
- at cindex braces, meaning of
- at cindex curly braces, meaning of
-Delimits a required argument to a command, as seen throughout this manual.
-
- at item % 
- at findex % @r{character}, meaning of
- at cindex percent character, meaning of
-Starts a comment; the @samp{%} and all remaining characters on the
-current line are ignored.
-
- at item $
- at findex $ @r{character}, meaning of
- at cindex dollar sign character, meaning of
-Starts and ends math mode (@pxref{Math formulas}).
-
- at item &
- at findex & @r{character}, meaning of
- at cindex ampersand character, meaning of
-Separates cells in a table (@pxref{tabular}).
-
- at item _ 
- at itemx ^
- at findex _ @r{character}, meaning of
- at findex ^ @r{character}, meaning of
- at cindex underscore character, meaning of
- at cindex hat character, meaning of
- at cindex caret character, meaning of
-Introduce a subscript or superscript in math (@pxref{Subscripts &
-superscripts}); they produce an error outside math mode.
-As a little-used special feature, two superscript characters in a row
-can introduce special notation for an arbitrary character;
- at pxref{Input text}.
-
- at item # 
- at findex # @r{character}, meaning of
- at cindex number sign character (@code{#}), meaning of
- at cindex sharp character (@code{#}), meaning of
- at cindex hash character (@code{#}), meaning of
-Stands for arguments in a macro definition (@pxref{\newcommand &
-\renewcommand}).
-
- at item ~ 
- at findex ~ @r{character}, meaning of
- at cindex tilde character, meaning of
-Produces a nonbreakable interword space (@pxref{~}).
-
- at end table
-
- at xref{Printing special characters}, for how to typeset these
-characters when you need them literally.
-
-
 @node \DocumentMetadata
 @section @code{\DocumentMetadata}: Producing tagged PDF output
 
@@ -7172,8 +7270,10 @@
          end;
 @end example
 
- at PkgIndex{algorithm2e} @PkgIndex{listings} @PkgIndex{minted}
+ at PkgIndex{algorithm2e}
 @PkgIndex{fancyvrb}
+ at PkgIndex{listings}
+ at PkgIndex{minted}
 @noindent
 This example is just for illustration of the environment.  To actually
 typeset computer code in typewriter like this, a verbatim environment
@@ -8149,11 +8249,11 @@
 
 @PkgIndex{listings}
 @PkgIndex{minted}
-One common use of verbatim input is to typeset computer code.  There are
-packages that are an improvement the @code{verbatim} environment.  For
-instance, one improvement is to allow the verbatim inclusion of external
-files, or parts of those files.  Such packages include @package{listings},
-and @package{minted}.
+One common use of verbatim input is to typeset computer code.  Some
+packages offer many features not provided by the @code{verbatim}
+environment; two of the most popular are @package{listings} and
+ at package{minted}.  For example, they are capable of pretty-printing,
+line numbering, and selecting parts of files for a continuing listing.
 
 @PkgIndex{fancyvrb}
 @PkgIndex{verbatimbox}
@@ -8160,10 +8260,13 @@
 A package that provides many more options for verbatim environments is
 @package{fancyvrb}.  Another is @package{verbatimbox}.
 
-For a list of all the relevant packages, see CTAN (@pxref{CTAN}).
+For a list of all the relevant packages, see CTAN (@pxref{CTAN}),
+particularly the topics @code{listing}
+(@url{https://ctan.org/topic/listing}) and @code{verbatim}
+(@url{https://ctan.org/topic/verbatim}).
 
 @menu
-* \verb::       The macro form of the @code{verbatim} environment.
+* \verb::  The macro form of the @code{verbatim} environment.
 @end menu
 
 
@@ -8223,11 +8326,6 @@
 is a better option than the @code{\verb} command, since
 it allows line breaks.
 
- at PkgIndex{listings}
- at PkgIndex{minted}
-For computer code there are many packages with advantages over
- at code{\verb}.  One is @package{listings}, another is @package{minted}.
-
 @PkgIndex{cprotect}
 You cannot use @code{\verb} in the argument to a macro, for instance in
 the argument to a @code{\section}.  It is not a question of @code{\verb}



More information about the latexrefman-commits mailing list.