diff options
author | Arnold D. Robbins <arnold@skeeve.com> | 2019-10-06 03:35:40 -0600 |
---|---|---|
committer | Arnold D. Robbins <arnold@skeeve.com> | 2019-10-06 03:35:40 -0600 |
commit | 376c0184c2e0998a9c5000f7f5c8d37fb1a338d7 (patch) | |
tree | 0d402dc19b9a8a0c7eebfb2440254a0bf86cf315 | |
parent | c5104f9f926b793234bde9cb05508b818ed9f9aa (diff) | |
download | egawk-376c0184c2e0998a9c5000f7f5c8d37fb1a338d7.tar.gz egawk-376c0184c2e0998a9c5000f7f5c8d37fb1a338d7.tar.bz2 egawk-376c0184c2e0998a9c5000f7f5c8d37fb1a338d7.zip |
Update Italian translation.
-rw-r--r-- | doc/it/ChangeLog | 5 | ||||
-rw-r--r-- | doc/it/gawktexi.in | 168 | ||||
-rw-r--r-- | doc/it/texinfo.tex | 233 |
3 files changed, 208 insertions, 198 deletions
diff --git a/doc/it/ChangeLog b/doc/it/ChangeLog index 4a704418..27bd5569 100644 --- a/doc/it/ChangeLog +++ b/doc/it/ChangeLog @@ -1,3 +1,8 @@ +2019-10-05 Antonio Giovanni Colombo <azc100@gmail.com> + + * gawktexi.in: Updated. + * texinfo.tex: Updated. + 2019-10-02 Antonio Giovanni Colombo <azc100@gmail.com> * gawktexi.in: Updated. diff --git a/doc/it/gawktexi.in b/doc/it/gawktexi.in index 115ef1ee..0b255d43 100644 --- a/doc/it/gawktexi.in +++ b/doc/it/gawktexi.in @@ -3481,7 +3481,7 @@ Stampare la lunghezza della riga in input pi@`u lunga: @example @group awk '@{ if (length($0) > max) max = length($0) @} -END @{ print max @}' data + END @{ print max @}' data @end group @end example @@ -3706,7 +3706,7 @@ stante o una regola isolata, come: @example awk '/12/ @{ print $0 @} -/21/ @{ print $0 @}' mail-list inventory-shipped + /21/ @{ print $0 @}' mail-list inventory-shipped @end example @cindex @command{gawk} @subentry ritorno a capo @@ -5191,7 +5191,7 @@ Iniziamo con due @dfn{script} @command{awk} (banali), che chiameremo @example BEGIN @{ -print "Questo @`e lo script test1." + print "Questo @`e lo script test1." @} @end example @@ -5201,7 +5201,7 @@ e questo @`e @file{test2}: @example @@include "test1" BEGIN @{ -print "Questo @`e lo script test2." + print "Questo @`e lo script test2." @} @end example @@ -5233,7 +5233,7 @@ I file da includere possono essere nidificati; p.es., dato un terzo @group @@include "test2" BEGIN @{ -print "Questo @`e lo script test3." + print "Questo @`e lo script test3." @} @end group @end example @@ -5446,7 +5446,7 @@ oppure: @example awk '@{ sum += $1 @} -END @{ print sum @}' data + END @{ print sum @}' data @end example @noindent @@ -7059,7 +7059,7 @@ Per esempio: @example awk 'BEGIN @{ RS = "u" @} -@{ print $0 @}' mail-list + @{ print $0 @}' mail-list @end example @noindent @@ -7583,9 +7583,9 @@ Per esempio: @example if ($(NF+1) != "") -print "non @`e possibile" + print "non @`e possibile" else -print "@`e tutto normale" + print "@`e tutto normale" @end example @noindent @@ -8264,7 +8264,7 @@ Unix @command{w}. @`E utile per spiegare l'uso di @code{FIELDWIDTHS}: @example @group -10:06pm up 21 days, 14:04, 23 users + 10:06pm up 21 days, 14:04, 23 users User tty login@ idle JCPU PCPU what hzuo ttyV0 8:58pm 9 5 vi p24.tex hzang ttyV3 6:37pm 50 -csh @@ -8285,18 +8285,18 @@ calcolato: @example BEGIN @{ FIELDWIDTHS = "9 6 10 6 7 7 35" @} NR > 2 @{ -inat = $4 -sub(/^ +/, "", inat) # togli spazi prima del valore -if (inat == "") -inat = 0 -if (inat ~ /:/) @{ # hh:mm -split(inat, t, ":") -inat = t[1] * 60 + t[2] -@} -if (inat ~ /days/) -inat *= 24 * 60 * 60 + inat = $4 + sub(/^ +/, "", inat) # togli spazi prima del valore + if (inat == "") + inat = 0 + if (inat ~ /:/) @{ # hh:mm + split(inat, t, ":") + inat = t[1] * 60 + t[2] + @} + if (inat ~ /days/) + inat *= 24 * 60 * 60 -print $1, $2, inat + print $1, $2, inat @} @end example @@ -8431,11 +8431,11 @@ o @code{"FIELDWIDTHS"} se si usa la separazione in campi a larghezza fissa: @example if (PROCINFO["FS"] == "FS") -@var{separazione in campi normale}@dots{} + @var{separazione in campi normale}@dots{} else if (PROCINFO["FS"] == "FIELDWIDTHS") -@var{separazione in campi a larghezza fissa}@dots{} + @var{separazione in campi a larghezza fissa}@dots{} else -@var{separazione dei campi in base al contenuto}@dots{} @ii{(si veda + @var{separazione dei campi in base al contenuto}@dots{} @ii{(si veda @ifnotinfo la @value{SECTION} successiva)} @end ifnotinfo @@ -8523,16 +8523,16 @@ e divide i dati: @c file eg/misc/simple-csv.awk @group BEGIN @{ -FPAT = "([^,]+)|(\"[^\"]+\")" + FPAT = "([^,]+)|(\"[^\"]+\")" @} @end group @group @{ -print "NF = ", NF -for (i = 1; i <= NF; i++) @{ -printf("$%d = <%s>\n", i, $i) -@} + print "NF = ", NF + for (i = 1; i <= NF; i++) @{ + printf("$%d = <%s>\n", i, $i) + @} @} @end group @c endfile @@ -8768,10 +8768,10 @@ Un semplice programma per elaborare questo file @`e il seguente: BEGIN @{ RS = "" ; FS = "\n" @} @{ -print "Il nome @`e:", $1 -print "L'indirizzo @`e:", $2 -print "Citt@`a e Stato sono:", $3 -print "" + print "Il nome @`e:", $1 + print "L'indirizzo @`e:", $2 + print "Citt@`a e Stato sono:", $3 + print "" @} @end example @@ -9066,11 +9066,11 @@ corrente: @example @{ -if ($1 == 10) @{ - getline < "secondary.input" - print -@} else - print + if ($1 == 10) @{ + getline < "secondary.input" + print + @} else + print @} @end example @@ -9111,12 +9111,12 @@ Tale record @`e sostituito dal contenuto del file @example @{ -if (NF == 2 && $1 == "@@include") @{ - while ((getline line < $2) > 0) - print line - close($2) -@} else - print + if (NF == 2 && $1 == "@@include") @{ + while ((getline line < $2) > 0) + print line + close($2) + @} else + print @} @end example @@ -9165,13 +9165,13 @@ costituito da un comando di shell. @example @group @{ -if ($1 == "@@execute") @{ - tmp = substr($0, 10) # Rimuove "@@execute" - while ((tmp | getline) > 0) - print - close(tmp) -@} else - print + if ($1 == "@@execute") @{ + tmp = substr($0, 10) # Rimuove "@@execute" + while ((tmp | getline) > 0) + print + close(tmp) + @} else + print @} @end group @end example @@ -9261,9 +9261,9 @@ stampa: @example BEGIN @{ -"date" | getline current_time -close("date") -print "Report printed on " current_time + "date" | getline current_time + close("date") + print "Report printed on " current_time @} @end example @@ -9429,9 +9429,9 @@ From: Duncan Moore <duncan.moore@@gmx.com> @example BEGIN @{ -system("echo 1 > f") -while ((getline a[++c] < "f") > 0) @{ @} -print c + system("echo 1 > f") + while ((getline a[++c] < "f") > 0) @{ @} + print c @} @end example @@ -9506,9 +9506,9 @@ non riceve alcuna risposta dal server dopo un certo periodo di tempo: Service = "/inet/tcp/0/localhost/daytime" PROCINFO[Service, "READ_TIMEOUT"] = 100 if ((Service |& getline) > 0) -print $0 + print $0 else if (ERRNO != "") -print ERRNO + print ERRNO @end group @end example @@ -9519,7 +9519,7 @@ non pi@`u di cinque secondi: @example PROCINFO["/dev/stdin", "READ_TIMEOUT"] = 5000 while ((getline < "/dev/stdin") > 0) -print $0 + print $0 @end example @command{gawk} termina l'operazione di lettura se l'input non @@ -9557,8 +9557,8 @@ per l'input diventa illimitata. @example PROCINFO[Service, "READ_TIMEOUT"] = 1000 while ((Service |& getline) > 0) @{ -print $0 -PROCINFO[Service, "READ_TIMEOUT"] -= 100 + print $0 + PROCINFO[Service, "READ_TIMEOUT"] -= 100 @} @end example @@ -9932,8 +9932,8 @@ stampate una volta sola: @example awk 'BEGIN @{ print "Mese Contenitori" - print "----- -----------" @} - @{ print $1, $2 @}' inventory-shipped + print "------ ----- --- --" @} + @{ print $1, $2 @}' inventory-shipped @end example @noindent @@ -9956,8 +9956,8 @@ campi: @example @group awk 'BEGIN @{ print "Mese Contenitori" - print "----- -----------" @} - @{ print $1, " ", $2 @}' inventory-shipped + print "------ ----- --- --" @} + @{ print $1, " ", $2 @}' inventory-shipped @end group @end example @@ -10626,8 +10626,8 @@ programma @command{awk}: @example awk 'BEGIN @{ print "Nome Numero" - print "---- ------" @} - @{ printf "%-10s %s\n", $1, $2 @}' mail-list + print " --- - ------ " @} + @{ printf "%-10s %s\n", $1, $2 @}' mail-list @end example L'esempio precedente usa sia l'istruzione @code{print} che l'istruzione @@ -10636,8 +10636,8 @@ risultati usando solo istruzioni @code{printf}: @example awk 'BEGIN @{ printf "%-10s %s\n", "Nome", "Numero" - printf "%-10s %s\n", "----", "------" @} - @{ printf "%-10s %s\n", $1, $2 @}' mail-list + printf "%-10s %s\n", " --- -", " --- --- " @} + @{ printf "%-10s %s\n", $1, $2 @}' mail-list @end example @noindent @@ -10650,9 +10650,9 @@ evidenziare memorizzandola in una variabile, cos@`{@dotless{i}}: @example awk 'BEGIN @{ format = "%-10s %s\n" - printf format, "Nome", "Numero" - printf format, "----", "------" @} - @{ printf format, $1, $2 @}' mail-list + printf format, "Nome", "Numero" + printf format, " --- -", " --- --- " @} + @{ printf format, $1, $2 @}' mail-list @end example @@ -10769,8 +10769,8 @@ alone for now and let's hope no-one notices. @example @group awk '@{ print $1 > "nomi.non.ordinati" -comando = "sort -r > nomi.ordinati" -print $1 | comando @}' mail-list + comando = "sort -r > nomi.ordinati" + print $1 | comando @}' mail-list @end group @end example @@ -11258,12 +11258,12 @@ consideri qualcosa del tipo: @example @{ -@dots{} -comando = ("grep " $1 " /qualche/file | un_mio_programma -q " $3) -while ((comando | getline) > 0) @{ -@var{elabora output di} comando -@} -# qui serve close(comando) + @dots{} + comando = ("grep " $1 " /qualche/file | un_mio_programma -q " $3) + while ((comando | getline) > 0) @{ + @var{elabora output di} comando + @} + # qui serve close(comando) @} @end example @@ -16216,7 +16216,7 @@ dall'implementazione @command{awk} in esecuzione. stringhe (@pxref{Conversione}) quando li si stampa con l'istruzione @code{print}. Funziona passandola - come primo argomento alla funzione @code{sprintf()} +come primo argomento alla funzione @code{sprintf()} (@pxref{Funzioni per stringhe}). Il suo valore di default @`e @code{"%.6g"}. Le prime versioni di @command{awk} usavano @code{OFMT} per specificare il formato da usare per convertire @@ -32194,7 +32194,7 @@ vogliono. @item Punto d'osservazione @cindex @dfn{watchpoint} (debugger) -@cindex punto d'osservazione @subetry(@code{watchpoint}) +@cindex punto d'osservazione @subentry(@code{watchpoint}) @cindex debugger @subentry @code{watchpoint} @cindex debugger @subentry punto d'osservazione Un punto d'osservazione @`e simile a un punto d'interruzione. La differenza @`e @@ -43143,7 +43143,7 @@ di ottimizzazione o la richiesta di generare informazioni per il @dfn{debug}). In alternativa, si possono specificare dei valori a piacere per molte delle variabili di @command{make} sulla riga di comando, come @code{CC} e @code{CFLAGS}, quando - si chiama il programma +si chiama il programma @command{configure}: @example diff --git a/doc/it/texinfo.tex b/doc/it/texinfo.tex index ca05be3f..ff0cc0c0 100644 --- a/doc/it/texinfo.tex +++ b/doc/it/texinfo.tex @@ -1,9 +1,9 @@ % texinfo.tex -- TeX macros to handle Texinfo files. -% +% % Load plain if necessary, i.e., if running under initex. \expandafter\ifx\csname fmtname\endcsname\relax\input plain\fi % -\def\texinfoversion{2019-09-20.22} +\def\texinfoversion{2019-09-24.13} % % Copyright 1985, 1986, 1988, 1990-2019 Free Software Foundation, Inc. % @@ -234,7 +234,7 @@ % @errormsg{MSG}. Do the index-like expansions on MSG, but if things % aren't perfect, it's not the end of the world, being an error message, % after all. -% +% \def\errormsg{\begingroup \indexnofonts \doerrormsg} \def\doerrormsg#1{\errmessage{#1}} @@ -248,7 +248,7 @@ \def\bigbreak{\ifnum\lastpenalty<10000\par\ifdim\lastskip<\bigskipamount \removelastskip\penalty-200\bigskip\fi\fi} -% Output routine +% Output routine % % For a final copy, take out the rectangles @@ -339,9 +339,9 @@ % the output routine. The saved contents are valid until we actually % \shipout a page. % -% (We used to run a short output routine to actually set \topmark and -% \firstmark to the right values, but if this was called with an empty page -% containing whatsits for writing index entries, the whatsits would be thrown +% (We used to run a short output routine to actually set \topmark and +% \firstmark to the right values, but if this was called with an empty page +% containing whatsits for writing index entries, the whatsits would be thrown % away and the index auxiliary file would remain empty.) % \newtoks\savedtopmark @@ -381,7 +381,7 @@ \let\thischapterheading\thischapter \else % \thischapterheading is the same as \thischapter except it is blank - % for the first page of a chapter. This is to prevent the chapter name + % for the first page of a chapter. This is to prevent the chapter name % being shown twice. \def\thischapterheading{}% \fi @@ -464,7 +464,7 @@ }% } -% First remove any @comment, then any @c comment. Pass the result on to +% First remove any @comment, then any @c comment. Pass the result on to % \argcheckspaces. \def\argremovecomment#1\comment#2\ArgTerm{\argremovec #1\c\ArgTerm} \def\argremovec#1\c#2\ArgTerm{\argcheckspaces#1\^^M\ArgTerm} @@ -1101,8 +1101,8 @@ where each line of input produces a line of output.} end end } - % The -2 in the arguments here gives all the input to TeX catcode 12 - % (other) or 10 (space), preventing undefined control sequence errors. See + % The -2 in the arguments here gives all the input to TeX catcode 12 + % (other) or 10 (space), preventing undefined control sequence errors. See % https://lists.gnu.org/archive/html/bug-texinfo/2019-08/msg00031.html % \endgroup @@ -1157,7 +1157,7 @@ where each line of input produces a line of output.} % for display in the outlines, and in other places. Thus, we have to % double any backslashes. Otherwise, a name like "\node" will be % interpreted as a newline (\n), followed by o, d, e. Not good. -% +% % See http://www.ntg.nl/pipermail/ntg-pdftex/2004-July/000654.html and % related messages. The final outcome is that it is up to the TeX user % to double the backslashes and otherwise make the string valid, so @@ -1462,7 +1462,7 @@ output) for that.)} % their "best" equivalent, based on the @documentencoding. Too % much work for too little return. Just use the ASCII equivalents % we use for the index sort strings. - % + % \indexnofonts \setupdatafile % We can have normal brace characters in the PDF outlines, unlike @@ -2746,7 +2746,7 @@ end } % Commands to set the quote options. -% +% \parseargdef\codequoteundirected{% \def\temp{#1}% \ifx\temp\onword @@ -2787,7 +2787,7 @@ end % If we are in a monospaced environment, however, 1) always use \ttsl, % and 2) do not add an italic correction. \def\dosmartslant#1#2{% - \ifusingtt + \ifusingtt {{\ttsl #2}\let\next=\relax}% {\def\next{{#1#2}\futurelet\next\smartitaliccorrection}}% \next @@ -2934,14 +2934,14 @@ end \gdef\codedash{\futurelet\next\codedashfinish} \gdef\codedashfinish{% \normaldash % always output the dash character itself. - % + % % Now, output a discretionary to allow a line break, unless % (a) the next character is a -, or % (b) the preceding character is a -. % E.g., given --posix, we do not want to allow a break after either -. % Given --foo-bar, we do want to allow a break between the - and the b. \ifx\next\codedash \else - \ifx\codedashprev\codedash + \ifx\codedashprev\codedash \else \discretionary{}{}{}\fi \fi % we need the space after the = for the case when \next itself is a @@ -3023,7 +3023,7 @@ end % For pdfTeX and LuaTeX \ifurefurlonlylink % PDF plus option to not display url, show just arg - \unhbox0 + \unhbox0 \else % PDF, normally display both arg and url for consistency, % visibility, if the pdf is eventually used to print, etc. @@ -3036,7 +3036,7 @@ end % For XeTeX \ifurefurlonlylink % PDF plus option to not display url, show just arg - \unhbox0 + \unhbox0 \else % PDF, normally display both arg and url for consistency, % visibility, if the pdf is eventually used to print, etc. @@ -3094,10 +3094,10 @@ end } } -% By default we'll break after the special characters, but some people like to -% break before the special chars, so allow that. Also allow no breaking at +% By default we'll break after the special characters, but some people like to +% break before the special chars, so allow that. Also allow no breaking at % all, for manual control. -% +% \parseargdef\urefbreakstyle{% \def\txiarg{#1}% \ifx\txiarg\wordnone @@ -3115,11 +3115,16 @@ end \def\wordbefore{before} \def\wordnone{none} -% Allow a ragged right output to aid breaking long URL's. Putting stretch in -% between characters of the URL doesn't look good. +% Allow a ragged right output to aid breaking long URL's. There can +% be a break at the \allowbreak with no extra glue (if the existing stretch in +% the line is sufficent), a break at the \penalty100 with extra glue added +% at the end of the line, or no break at all here. +% Changing the value of the penalty and/or the amount of stretch affects how +% preferrable one choice is over the other. \def\urefallowbreak{% - \hskip 0pt plus 4 em\relax \allowbreak + \hskip 0pt plus 4 em\relax + \penalty100 \hskip 0pt plus -4 em\relax } @@ -3319,7 +3324,7 @@ end % @inlinefmt{FMTNAME,PROCESSED-TEXT} and @inlineraw{FMTNAME,RAW-TEXT}. % Ignore unless FMTNAME == tex; then it is like @iftex and @tex, % except specified as a normal braced arg, so no newlines to worry about. -% +% \def\outfmtnametex{tex} % \long\def\inlinefmt#1{\doinlinefmt #1,\finish} @@ -3327,7 +3332,7 @@ end \def\inlinefmtname{#1}% \ifx\inlinefmtname\outfmtnametex \ignorespaces #2\fi } -% +% % @inlinefmtifelse{FMTNAME,THEN-TEXT,ELSE-TEXT} expands THEN-TEXT if % FMTNAME is tex, else ELSE-TEXT. \long\def\inlinefmtifelse#1{\doinlinefmtifelse #1,,,\finish} @@ -3343,7 +3348,7 @@ end % *right* brace they would have to use a command anyway, so they may as % well use a command to get a left brace too. We could re-use the % delimiter character idea from \verb, but it seems like overkill. -% +% \long\def\inlineraw{\tex \doinlineraw} \long\def\doinlineraw#1{\doinlinerawtwo #1,\finish} \def\doinlinerawtwo#1,#2,\finish{% @@ -3620,7 +3625,7 @@ end % for non-CM glyphs. That is ec* for regular text and tc* for the text % companion symbols (LaTeX TS1 encoding). Both are part of the ec % package and follow the same conventions. -% +% \def\ecfont{\etcfont{e}} \def\tcfont{\etcfont{t}} % @@ -3692,7 +3697,7 @@ end after the title page.}}% \def\setshortcontentsaftertitlepage{% \errmessage{@setshortcontentsaftertitlepage has been removed as a Texinfo - command; move your @shortcontents and @contents commands if you + command; move your @shortcontents and @contents commands if you want the contents after the title page.}}% \parseargdef\shorttitlepage{% @@ -3747,7 +3752,7 @@ end % don't worry much about spacing, ragged right. This should be used % inside a \vbox, and fonts need to be set appropriately first. \par should % be specified before the end of the \vbox, since a vbox is a group. -% +% \def\raggedtitlesettings{% \rm \hyphenpenalty=10000 @@ -4370,7 +4375,7 @@ end } % multitable-only commands. -% +% % @headitem starts a heading row, which we typeset in bold. Assignments % have to be global since we are inside the implicit group of an % alignment entry. \everycr below resets \everytab so we don't have to @@ -4689,7 +4694,7 @@ end % Like \expandablevalue, but completely expandable (the \message in the % definition above operates at the execution level of TeX). Used when % writing to auxiliary files, due to the expansion that \write does. -% If flag is undefined, pass through an unexpanded @value command: maybe it +% If flag is undefined, pass through an unexpanded @value command: maybe it % will be set by the time it is read back in. % % NB flag names containing - or _ may not work here. @@ -4713,7 +4718,7 @@ end % @ifset VAR ... @end ifset reads the `...' iff VAR has been defined % with @set. -% +% % To get the special treatment we need for `@end ifset,' we call % \makecond and then redefine. % @@ -4746,7 +4751,7 @@ end % without the @) is in fact defined. We can only feasibly check at the % TeX level, so something like `mathcode' is going to considered % defined even though it is not a Texinfo command. -% +% \makecond{ifcommanddefined} \def\ifcommanddefined{\parsearg{\doifcmddefined{\let\next=\ifcmddefinedfail}}} % @@ -4854,8 +4859,8 @@ end \def\docodeindex#1{\edef\indexname{#1}\parsearg\docodeindexxxx} \def\docodeindexxxx #1{\doind{\indexname}{\code{#1}}} - -% Used for the aux, toc and index files to prevent expansion of Texinfo + +% Used for the aux, toc and index files to prevent expansion of Texinfo % commands. % \def\atdummies{% @@ -5202,7 +5207,7 @@ end } \def\defglyph#1#2{\def#1##1{#2}} % see above - + % #1 is the index name, #2 is the entry text. @@ -5229,7 +5234,7 @@ end \ifx\suffix\indexisfl\def\suffix{f1}\fi % Open the file \immediate\openout\csname#1indfile\endcsname \jobname.\suffix - % Using \immediate above here prevents an object entering into the current + % Using \immediate above here prevents an object entering into the current % box, which could confound checks such as those in \safewhatsit for % preceding skips. \typeout{Writing index file \jobname.\suffix}% @@ -5284,7 +5289,7 @@ end \ifx\segment\isfinish \else % - % Fully expand the segment, throwing away any @sortas directives, and + % Fully expand the segment, throwing away any @sortas directives, and % trim spaces. \edef\trimmed{\segment}% \edef\trimmed{\expandafter\eatspaces\expandafter{\trimmed}}% @@ -5342,12 +5347,12 @@ end % the current value of \escapechar. \def\escapeisbackslash{\escapechar=`\\} -% Use \ in index files by default. texi2dvi didn't support @ as the escape -% character (as it checked for "\entry" in the files, and not "@entry"). When -% the new version of texi2dvi has had a chance to become more prevalent, then -% the escape character can change back to @ again. This should be an easy -% change to make now because both @ and \ are only used as escape characters in -% index files, never standing for themselves. +% Use \ in index files by default. texi2dvi didn't support @ as the escape +% character (as it checked for "\entry" in the files, and not "@entry"). When +% the new version of texi2dvi has had a chance to become more prevalent, then +% the escape character can change back to @ again. This should be an easy +% change to make now because both @ and \ are only used as escape characters in +% index files, never standing for themselves. % \set txiindexescapeisbackslash @@ -5367,7 +5372,7 @@ end \def\}{\rbracechar{}}% \uccode`\~=`\\ \uppercase{\def~{\backslashchar{}}}% % - % Split the entry into primary entry and any subentries, and get the index + % Split the entry into primary entry and any subentries, and get the index % sort key. \splitindexentry\indextext % @@ -5548,18 +5553,18 @@ end \uccode`\~=`\\ \uppercase{\if\noexpand~}\noexpand#1 \expandafter\ifx\csname SETtxiskipindexfileswithbackslash\endcsname\relax \errmessage{% -ERROR: A sorted index file in an obsolete format was skipped. +ERROR: A sorted index file in an obsolete format was skipped. To fix this problem, please upgrade your version of 'texi2dvi' or 'texi2pdf' to that at <https://ftp.gnu.org/gnu/texinfo>. -If you are using an old version of 'texindex' (part of the Texinfo +If you are using an old version of 'texindex' (part of the Texinfo distribution), you may also need to upgrade to a newer version (at least 6.0). You may be able to typeset the index if you run 'texindex \jobname.\indexname' yourself. -You could also try setting the 'txiindexescapeisbackslash' flag by +You could also try setting the 'txiindexescapeisbackslash' flag by running a command like -'texi2dvi -t "@set txiindexescapeisbackslash" \jobname.texi'. If you do +'texi2dvi -t "@set txiindexescapeisbackslash" \jobname.texi'. If you do this, Texinfo will try to use index files in the old format. -If you continue to have problems, deleting the index files and starting again +If you continue to have problems, deleting the index files and starting again might help (with 'rm \jobname.?? \jobname.??s')% }% \else @@ -5628,7 +5633,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % bottom of a column to reduce an increase in inter-line spacing. \nobreak \vskip 0pt plus 5\baselineskip - \penalty -300 + \penalty -300 \vskip 0pt plus -5\baselineskip % % Typeset the initial. Making this add up to a whole number of @@ -5744,7 +5749,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \advance\dimen@ii by 1\dimen@i \ifdim\wd\boxA > \dimen@ii % If the entry doesn't fit in one line \ifdim\dimen@ > 0.8\dimen@ii % due to long index text - % Try to split the text roughly evenly. \dimen@ will be the length of + % Try to split the text roughly evenly. \dimen@ will be the length of % the first line. \dimen@ = 0.7\dimen@ \dimen@ii = \hsize @@ -5952,7 +5957,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \newbox\balancedcolumns \setbox\balancedcolumns=\vbox{shouldnt see this}% % -% Only called for the last of the double column material. \doublecolumnout +% Only called for the last of the double column material. \doublecolumnout % does the others. \def\balancecolumns{% \setbox0 = \vbox{\unvbox\PAGE}% like \box255 but more efficient, see p.120. @@ -5980,7 +5985,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% }% % Now the left column is in box 1, and the right column in box 3. % - % Check whether the left column has come out higher than the page itself. + % Check whether the left column has come out higher than the page itself. % (Note that we have doubled \vsize for the double columns, so % the actual height of the page is 0.5\vsize). \ifdim2\ht1>\vsize @@ -6277,7 +6282,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \let\top\unnumbered % Sections. -% +% \outer\parseargdef\numberedsec{\numhead1{#1}} % normally calls seczzz \def\seczzz#1{% \global\subsecno=0 \global\subsubsecno=0 \global\advance\secno by 1 @@ -6300,7 +6305,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% } % Subsections. -% +% % normally calls numberedsubseczzz: \outer\parseargdef\numberedsubsec{\numhead2{#1}} \def\numberedsubseczzz#1{% @@ -6325,7 +6330,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% } % Subsubsections. -% +% % normally numberedsubsubseczzz: \outer\parseargdef\numberedsubsubsec{\numhead3{#1}} \def\numberedsubsubseczzz#1{% @@ -7383,7 +7388,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % @indentedblock is like @quotation, but indents only on the left and % has no optional argument. -% +% \makedispenvdef{indentedblock}{\indentedblockstart} % \def\indentedblockstart{% @@ -7683,7 +7688,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % @deftypefnnewline on|off says whether the return type of typed functions % are printed on their own line. This affects @deftypefn, @deftypefun, % @deftypeop, and @deftypemethod. -% +% \parseargdef\deftypefnnewline{% \def\temp{#1}% \ifx\temp\onword @@ -7702,8 +7707,8 @@ might help (with 'rm \jobname.?? \jobname.??s')% % \dosubind {index}{topic}{subtopic} % % If SUBTOPIC is present, precede it with a space, and call \doind. -% (At some time during the 20th century, this made a two-level entry in an -% index such as the operation index. Nobody seemed to notice the change in +% (At some time during the 20th century, this made a two-level entry in an +% index such as the operation index. Nobody seemed to notice the change in % behaviour though.) \def\dosubind#1#2#3{% \def\thirdarg{#3}% @@ -7878,7 +7883,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \tclose{\temp}% typeset the return type \ifrettypeownline % put return type on its own line; prohibit line break following: - \hfil\vadjust{\nobreak}\break + \hfil\vadjust{\nobreak}\break \else \space % type on same line, so just followed by a space \fi @@ -8025,7 +8030,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \scantokens{#1@comment}% % % The \comment is to remove the \newlinechar added by \scantokens, and - % can be noticed by \parsearg. Note \c isn't used because this means cedilla + % can be noticed by \parsearg. Note \c isn't used because this means cedilla % in math mode. } @@ -8226,7 +8231,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % list to some hook where the argument is to be expanded. If there are % less than 10 arguments that hook is to be replaced by ##N where N % is the position in that list, that is to say the macro arguments are to be -% defined `a la TeX in the macro body. +% defined `a la TeX in the macro body. % % That gets used by \mbodybackslash (above). % @@ -8257,8 +8262,8 @@ might help (with 'rm \jobname.?? \jobname.??s')% % % Read recursive and nonrecursive macro bodies. (They're different since % rec and nonrec macros end differently.) -% -% We are in \macrobodyctxt, and the \xdef causes backslashshes in the macro +% +% We are in \macrobodyctxt, and the \xdef causes backslashshes in the macro % body to be transformed. % Set \macrobody to the body of the macro, and call \defmacro. % @@ -8292,7 +8297,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % twice the \macarg.BLAH macros does not cost too much processing power. \def\parsemmanyargdef@@#1,{% \if#1;\let\next=\relax - \else + \else \let\next=\parsemmanyargdef@@ \edef\tempb{\eatspaces{#1}}% \expandafter\def\expandafter\tempa @@ -8377,7 +8382,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % Replace arguments by their values in the macro body, and place the result % in macro \@tempa. -% +% \def\macvalstoargs@{% % To do this we use the property that token registers that are \the'ed % within an \edef expand only once. So we are going to place all argument @@ -8401,9 +8406,9 @@ might help (with 'rm \jobname.?? \jobname.??s')% \expandafter\def\expandafter\@tempa\expandafter{\@tempc}% } -% Define the named-macro outside of this group and then close this group. -% -\def\macargexpandinbody@{% +% Define the named-macro outside of this group and then close this group. +% +\def\macargexpandinbody@{% \expandafter \endgroup \macargdeflist@ @@ -8441,7 +8446,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% } % Trailing missing arguments are set to empty. -% +% \def\setemptyargvalues@{% \ifx\paramlist\nilm@ \let\next\macargexpandinbody@ @@ -8518,7 +8523,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \else % at most 9 \ifnum\paramno<10\relax % @MACNAME sets the context for reading the macro argument - % @MACNAME@@ gets the argument, processes backslashes and appends a + % @MACNAME@@ gets the argument, processes backslashes and appends a % comma. % @MACNAME@@@ removes braces surrounding the argument list. % @MACNAME@@@@ scans the macro body with arguments substituted. @@ -8562,11 +8567,11 @@ might help (with 'rm \jobname.?? \jobname.??s')% % Call #1 with a list of tokens #2, with any doubled backslashes in #2 % compressed to one. % -% This implementation works by expansion, and not execution (so we cannot use -% \def or similar). This reduces the risk of this failing in contexts where -% complete expansion is done with no execution (for example, in writing out to +% This implementation works by expansion, and not execution (so we cannot use +% \def or similar). This reduces the risk of this failing in contexts where +% complete expansion is done with no execution (for example, in writing out to % an auxiliary file for an index entry). -% +% % State is kept in the input stream: the argument passed to % @look_ahead, @gobble_and_check_finish and @add_segment is % @@ -8588,11 +8593,11 @@ might help (with 'rm \jobname.?? \jobname.??s')% % #3 - NEXT_TOKEN % #4 used to look ahead % -% If the next token is not a backslash, process the rest of the argument; +% If the next token is not a backslash, process the rest of the argument; % otherwise, remove the next token. @gdef@look_ahead#1!#2#3#4{% @ifx#4\% - @expandafter@gobble_and_check_finish + @expandafter@gobble_and_check_finish @else @expandafter@add_segment @fi#1!{#2}#4#4% @@ -8616,9 +8621,9 @@ might help (with 'rm \jobname.?? \jobname.??s')% % #3 - NEXT_TOKEN % #4 is input stream until next backslash % -% Input stream is either at the start of the argument, or just after a -% backslash sequence, either a lone backslash, or a doubled backslash. -% NEXT_TOKEN contains the first token in the input stream: if it is \finish, +% Input stream is either at the start of the argument, or just after a +% backslash sequence, either a lone backslash, or a doubled backslash. +% NEXT_TOKEN contains the first token in the input stream: if it is \finish, % finish; otherwise, append to ARG_RESULT the segment of the argument up until % the next backslash. PENDING_BACKSLASH contains a backslash to represent % a backslash just before the start of the input stream that has not been @@ -8630,13 +8635,13 @@ might help (with 'rm \jobname.?? \jobname.??s')% % append the pending backslash to the result, followed by the next segment @expandafter@is_fi@look_ahead#1#2#4!{\}@fi % this @fi is discarded by @look_ahead. - % we can't get rid of it with \expandafter because we don't know how + % we can't get rid of it with \expandafter because we don't know how % long #4 is. } % #1 - THE_MACRO % #2 - ARG_RESULT -% #3 discards the res of the conditional in @add_segment, and @is_fi ends the +% #3 discards the res of the conditional in @add_segment, and @is_fi ends the % conditional. @gdef@call_the_macro#1#2!#3@fi{@is_fi #1{#2}} @@ -8648,7 +8653,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % for reading the argument (slightly different in the two cases). Then, % to read the argument, in the whole-line case, it then calls the regular % \parsearg MAC; in the lbrace case, it calls \passargtomacro MAC. -% +% \def\braceorline#1{\let\macnamexxx=#1\futurelet\nchar\braceorlinexxx} \def\braceorlinexxx{% \ifx\nchar\bgroup @@ -8702,7 +8707,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % Used so that the @top node doesn't have to be wrapped in an @ifnottex % conditional. -% \doignore goes to more effort to skip nested conditionals but we don't need +% \doignore goes to more effort to skip nested conditionals but we don't need % that here. \def\omittopnode{% \ifx\lastnode\wordTop @@ -8710,7 +8715,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% } \def\wordTop{Top} -% Until the next @node or @bye command, divert output to a box that is not +% Until the next @node or @bye command, divert output to a box that is not % output. \def\ignorenode{\setbox\dummybox\vbox\bgroup\def\node{\egroup\node}% \ignorenodebye @@ -8777,7 +8782,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % automatically in xrefs, if the third arg is not explicitly specified. % This was provided as a "secret" @set xref-automatic-section-title % variable, now it's official. -% +% \parseargdef\xrefautomaticsectiontitle{% \def\temp{#1}% \ifx\temp\onword @@ -8793,7 +8798,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \fi\fi } -% +% % @xref, @pxref, and @ref generate cross-references. For \xrefX, #1 is % the node name, #2 the name of the Info cross-reference, #3 the printed % node name, #4 the name of the Info file, #5 the name of the printed @@ -8946,24 +8951,24 @@ might help (with 'rm \jobname.?? \jobname.??s')% \fi \else % node/anchor (non-float) references. - % + % % If we use \unhbox to print the node names, TeX does not insert % empty discretionaries after hyphens, which means that it will not % find a line break at a hyphen in a node names. Since some manuals % are best written with fairly long node names, containing hyphens, % this is a loss. Therefore, we give the text of the node name % again, so it is as if TeX is seeing it for the first time. - % + % \ifdim \wd\printedmanualbox > 0pt % Cross-manual reference with a printed manual name. - % + % \crossmanualxref{\cite{\printedmanual\unskip}}% % \else\ifdim \wd\infofilenamebox > 0pt % Cross-manual reference with only an info filename (arg 4), no % printed manual name (arg 5). This is essentially the same as % the case above; we output the filename, since we have nothing else. - % + % \crossmanualxref{\code{\infofilename\unskip}}% % \else @@ -9003,20 +9008,20 @@ might help (with 'rm \jobname.?? \jobname.??s')% \endgroup} % Output a cross-manual xref to #1. Used just above (twice). -% +% % Only include the text "Section ``foo'' in" if the foo is neither % missing or Top. Thus, @xref{,,,foo,The Foo Manual} outputs simply % "see The Foo Manual", the idea being to refer to the whole manual. -% +% % But, this being TeX, we can't easily compare our node name against the % string "Top" while ignoring the possible spaces before and after in % the input. By adding the arbitrary 7sp below, we make it much less % likely that a real node name would have the same width as "Top" (e.g., % in a monospaced font). Hopefully it will never happen in practice. -% +% % For the same basic reason, we retypeset the "Top" at every % reference, since the current font is indeterminate. -% +% \def\crossmanualxref#1{% \setbox\toprefbox = \hbox{Top\kern7sp}% \setbox2 = \hbox{\ignorespaces \printedrefname \unskip \kern7sp}% @@ -9063,7 +9068,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% \fi\fi\fi } -% \refx{NAME}{SUFFIX} - reference a cross-reference string named NAME. SUFFIX +% \refx{NAME}{SUFFIX} - reference a cross-reference string named NAME. SUFFIX % is output afterwards if non-empty. \def\refx#1#2{% \requireauxfile @@ -9095,9 +9100,9 @@ might help (with 'rm \jobname.?? \jobname.??s')% #2% Output the suffix in any case. } -% This is the macro invoked by entries in the aux file. Define a control -% sequence for a cross-reference target (we prepend XR to the control sequence -% name to avoid collisions). The value is the page number. If this is a float +% This is the macro invoked by entries in the aux file. Define a control +% sequence for a cross-reference target (we prepend XR to the control sequence +% name to avoid collisions). The value is the page number. If this is a float % type, we have more work to do. % \def\xrdef#1#2{% @@ -9113,10 +9118,10 @@ might help (with 'rm \jobname.?? \jobname.??s')% \bgroup \expandafter\gdef\csname XR\safexrefname\endcsname{#2}% \egroup - % We put the \gdef inside a group to avoid the definitions building up on - % TeX's save stack, which can cause it to run out of space for aux files with + % We put the \gdef inside a group to avoid the definitions building up on + % TeX's save stack, which can cause it to run out of space for aux files with % thousands of lines. \gdef doesn't use the save stack, but \csname does - % when it defines an unknown control sequence as \relax. + % when it defines an unknown control sequence as \relax. % % Was that xref control sequence that we just defined for a float? \expandafter\iffloat\csname XR\safexrefname\endcsname @@ -9475,7 +9480,7 @@ might help (with 'rm \jobname.?? \jobname.??s')% % \ifimagevmode \medskip % space after a standalone image - \fi + \fi \ifx\centersub\centerV \egroup \fi \endgroup} @@ -10306,7 +10311,7 @@ directory should work if nowhere else does.} \uppercase{.} \endgroup \else - \errhelp = \EMsimple + \errhelp = \EMsimple \errmessage{Unicode character U+#1 not supported, sorry}% \fi \else @@ -10339,7 +10344,7 @@ directory should work if nowhere else does.} \countUTFz = "#1\relax \begingroup \parseXMLCharref - + % Give \u8:... its definition. The sequence of seven \expandafter's % expands after the \gdef three times, e.g. % @@ -10351,7 +10356,7 @@ directory should work if nowhere else does.} \expandafter\expandafter \expandafter\expandafter \expandafter\gdef \UTFviiiTmp{#2}% - % + % \expandafter\ifx\csname uni:#1\endcsname \relax \else \message{Internal error, already defined: #1}% \fi @@ -10390,7 +10395,7 @@ directory should work if nowhere else does.} \divide\countUTFz by 64 \countUTFy = \countUTFz % Save to be the future value of \countUTFz. \multiply\countUTFz by 64 - + % \countUTFz is now \countUTFx with the last 5 bits cleared. Subtract % in order to get the last five bits. \advance\countUTFx by -\countUTFz @@ -10425,7 +10430,7 @@ directory should work if nowhere else does.} % U+0080..U+00FF = https://en.wikipedia.org/wiki/Latin-1_Supplement_(Unicode_block) % U+0100..U+017F = https://en.wikipedia.org/wiki/Latin_Extended-A % U+0180..U+024F = https://en.wikipedia.org/wiki/Latin_Extended-B -% +% % Many of our renditions are less than wonderful, and all the missing % characters are available somewhere. Loading the necessary fonts % awaits user request. We can't truly support Unicode without @@ -11463,9 +11468,9 @@ directory should work if nowhere else does.} \def\texinfochars{% \let< = \activeless \let> = \activegtr - \let~ = \activetilde + \let~ = \activetilde \let^ = \activehat - \markupsetuplqdefault \markupsetuprqdefault + \markupsetuplqdefault \markupsetuprqdefault \let\b = \strong \let\i = \smartitalic % in principle, all other definitions in \tex have to be undone too. |