[latexrefman-commits] [SCM] latexrefman updated: r777 - trunk
vincentb1 at gnu.org.ua
vincentb1 at gnu.org.ua
Mon Mar 30 12:20:37 CEST 2020
Author: vincentb1
Date: 2020-03-30 13:20:37 +0300 (Mon, 30 Mar 2020)
New Revision: 777
Modified:
trunk/ChangeLog
trunk/latex2e-fr.texi
trunk/latex2e.texi
Log:
Various fixes + ?\194?\171?\194?\160command?\194?\160?\194?\187 ?\226?\134?\146 ?\194?\171?\194?\160macro?\194?\160?\194?\187 when expansion only is talked about.
* latex2e-fr.texi (\write): ?\194?\171?\194?\160master?\194?\160?\194?\187 ?\226?\134?\146 ?\194?\171?\194?\160root?\194?\160?\194?\187 for consistency.
* latex2e.texi (\endinput): clarify ?\194?\171?\194?\160during mailing?\194?\160?\194?\187.
(Table of contents etc.): Move package index reference to the
concerned paragaph.
(\openin & \openout): Typoes.
(\read): ?\194?\171?\194?\160\file?\194?\160?\194?\187 ?\226?\134?\146 ?\194?\171?\194?\160\recipient file?\194?\160?\194?\187
(\write): ?\194?\171?\194?\160 at code{?\226?\128?\166}?\194?\160?\194?\187 ?\226?\134?\146 ?\194?\171?\194?\160 at var{?\226?\128?\166}?\194?\160?\194?\187.
(\write): typo.
(\write): ?\194?\171?\194?\160command?\194?\160?\194?\187 ?\226?\134?\146 ?\194?\171?\194?\160macro?\194?\160?\194?\187, well when talking about
expansion, it is certainly better to use the word ?\194?\171?\194?\160macro?\194?\160?\194?\187 than
the word ?\194?\171?\194?\160command?\194?\160?\194?\187.
(\write): ?\194?\171?\194?\160master?\194?\160?\194?\187 ?\226?\134?\146 ?\194?\171?\194?\160root?\194?\160?\194?\187 for consistency.
(\message): ?\194?\171?\194?\160 at code{?\226?\128?\166}?\194?\160?\194?\187 ?\226?\134?\146 ?\194?\171?\194?\160 at var{?\226?\128?\166}?\194?\160?\194?\187.
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2020-03-30 10:04:33 UTC (rev 776)
+++ trunk/ChangeLog 2020-03-30 10:20:37 UTC (rev 777)
@@ -1,5 +1,22 @@
2020-03-30 Vincent Belaïche <vincentb1 at users.sourceforge.net>
+ * latex2e-fr.texi (\write): « master » → « root » for consistency.
+
+ * latex2e.texi (\endinput): clarify « during mailing ».
+ (Table of contents etc.): Move package index reference to the
+ concerned paragaph.
+ (\openin & \openout): Typoes.
+ (\read): « \file » → « \recipient file »
+ (\write): « @code{…} » → « @var{…} ».
+ (\write): typo.
+ (\write): « command » → « macro », well when talking about
+ expansion, it is certainly better to use the word « macro » than
+ the word « command ».
+ (\write): « master » → « root » for consistency.
+ (\message): « @code{…} » → « @var{…} ».
+
+2020-03-30 Vincent Belaïche <vincentb1 at users.sourceforge.net>
+
* latex2e-fr.texi (\makeatletter & \makeatother): Update translation.
2020-03-30 Vincent Belaïche <vincentb1 at users.sourceforge.net>
Modified: trunk/latex2e-fr.texi
===================================================================
--- trunk/latex2e-fr.texi 2020-03-30 10:04:33 UTC (rev 776)
+++ trunk/latex2e-fr.texi 2020-03-30 10:20:37 UTC (rev 777)
@@ -14182,7 +14182,7 @@
(@pxref{@TeX{} engines}).
On écrit dans le fichier @file{.aux} courant qui est associé au fichier
-principal ou au fichier inclus courant, en utilisant
+racine ou au fichier inclus courant, en utilisant
@code{\write\@@auxout@{@var{chaîne}@}}. On écrit vers le fichier
@file{.aux} principal en utilisant
@code{\write\@@mainaux@{@var{chaîne}@}}.
@@ -14267,7 +14267,7 @@
commande telle que @code{\include@{../filename@}} puisque @LaTeX{} va
essayer d'ouvrir @file{../filename.aux}. La solution la plus simple est
de placer les fichiers inclus dans le même répertoire que le fichier
-principal, ou dans des sous-répertoire.
+racine, ou dans des sous-répertoire.
@PkgIndex{answers}
Un cas usuel dans lequel des auteurs tentent d'écrire dans un fichier
Modified: trunk/latex2e.texi
===================================================================
--- trunk/latex2e.texi 2020-03-30 10:04:33 UTC (rev 776)
+++ trunk/latex2e.texi 2020-03-30 10:20:37 UTC (rev 777)
@@ -17914,12 +17914,13 @@
@end example
This can be useful for putting documentation or comments at the end of a
-file, or for avoiding junk characters that can be added during mailing.
-It is also useful for debugging: one strategy to localize errors is to
-put @code{\endinput} halfway through the included file and see if the
-error disappears. Now, knowing which half contains the error, moving
- at code{\endinput} to halfway through that area further narrows down the
-location. This process rapidly finds the offending line.
+file, or for avoiding junk characters that can be added if the file is
+transmitted in the body of an email. It is also useful for debugging:
+one strategy to localize errors is to put @code{\endinput} halfway
+through the included file and see if the error disappears. Now, knowing
+which half contains the error, moving @code{\endinput} to halfway
+through that area further narrows down the location. This process
+rapidly finds the offending line.
After reading @code{\endinput}, @LaTeX{} continues to read to the end of
the line, so something can follow this command and be read nonetheless.
@@ -18227,8 +18228,6 @@
contents commands; for instance, these work with information stored in
@file{.lof} and @file{.lot} files.
- at PkgIndex{babel}
- at PkgIndex{polyglossia}
To change the header for the table of contents page do something like
the first line here.
@@ -18239,6 +18238,8 @@
@end example
@noindent
+ at PkgIndex{babel}
+ at PkgIndex{polyglossia}
Similarly, the other two lines will do the other two.
Internationalization packages such as @file{babel} or @file{polyglossia}
will change the headers depending on the chosen base language.
@@ -19560,7 +19561,7 @@
the ten digits, along with underscore and dash, and in particular with
no dot or space.
-For @code{openin}, if @TeX{} cannot find the file then it does not give
+For @code{\openin}, if @TeX{} cannot find the file then it does not give
an error. It just considers that the stream is not open (test for this
with @code{\ifeof}; one recourse is the command
@code{\InputIfFileExists}, @pxref{Class and package commands}). If you
@@ -19591,7 +19592,7 @@
@example
\newread\recipientfile
\openin\recipientfile=email
-\read\file to\email
+\read\recipientfile to\email
\typeout@{Email address: \email@}
\closein\recipientfile
@end example
@@ -19730,7 +19731,7 @@
\write at var{number}@{@var{string}@}
@end example
-Write @code{string} to the log file, to the terminal, or to a file
+Write @var{string} to the log file, to the terminal, or to a file
opened by @code{\openout}. For instance, @code{\write6} writes to text
stream number at tie{}6.
@@ -19750,7 +19751,7 @@
@noindent
The @code{\newwrite} allocates a stream number, giving it a symbolic
-names to make life easier, so that @code{test
+name to make life easier, so that @code{test
\newwrite\myfile\the\myfile} produces something like @samp{test 3}.
Then @code{\openout} associates the stream number with the given file
name. With that, @code{\write3} puts the string in the file.
@@ -19770,7 +19771,7 @@
In Lua at TeX{}, instead of 16 output streams there are 256
(@pxref{@TeX{} engines}).
-Write to the current @file{.aux} file, which is associated with the main
+Write to the current @file{.aux} file, which is associated with the root
file or with the current include file, using
@code{\write\@@auxout@{@var{string}@}}. Write to the main @file{.aux}
file using @code{\write\@@mainaux@{@var{string}@}}.
@@ -19788,16 +19789,16 @@
\protected@@write\@@auxout@{@}@{@var{string}@}
@end example
-With the first, @LaTeX{} writes @var{string} to the file. Any commands
-in @var{string} will be expanded (just as in @code{\edef} so that to
+With the first, @LaTeX{} writes @var{string} to the file. Any macros in
+ at var{string} will be expanded (just as in @code{\edef} so that to
prevent expansion you should use @code{\noexpand} or a @code{toks},
except that you should use @code{#} instead of @code{##}). With the
second, @var{string} is stored on the current list of things (as a
@TeX{} ``whatsit'') and kept until the page is shipped out and likewise
-the commands are unexpanded until shipout. The third,
+the macros are unexpanded until shipout. The third,
@code{\protected@@write}, is like the second except that you can use
- at code{\protect} on fragile commands. The extra first argument allows you
-to locally insert extra definitions to make more commands be safe or
+ at code{\protect} on fragile macros. The extra first argument allows you
+to locally insert extra definitions to make more macros be safe or
have special definition during the write.
Here @var{string} contains a control sequence.
@@ -19847,12 +19848,12 @@
error when trying to use commands such as @code{\include@{../filename@}}
because @LaTeX{} will try to open @file{../filename.aux}. The simplest
solution is to put the included files in the same directory as the
-master file, or in subdirectories.
+root file, or in subdirectories.
@PkgIndex{answers}
A common case where authors want to write a file not already provided by
@LaTeX{} is for answers to exercises, or some other situation where you
-want to write out verbatim, without expanding the commands. CTAN has a
+want to write out verbatim, without expanding the macros. CTAN has a
number of packages for this; one is @file{answers}.
@menu
@@ -19873,7 +19874,7 @@
\message@{@var{string}@}
@end example
-Write @code{string} to the log file and the terminal.
+Write @var{string} to the log file and the terminal.
Typically, @LaTeX{} authors use @code{\typeout} (@pxref{\typeout}). It
allows you to use @code{\protect} on any fragile commands in
More information about the latexrefman-commits
mailing list.