texinfo-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

branch master updated: Update texinfo/doc/customization_api.texi


From: Patrice Dumas
Subject: branch master updated: Update texinfo/doc/customization_api.texi
Date: Mon, 15 Aug 2022 04:20:56 -0400

This is an automated email from the git hooks/post-receive script.

pertusus pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new 3292e4680f Update texinfo/doc/customization_api.texi
3292e4680f is described below

commit 3292e4680fde9b86f0bff5d888e8c60ae2413bb7
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Mon Aug 15 10:20:31 2022 +0200

    Update texinfo/doc/customization_api.texi
---
 doc/customization_api.texi | 29 +++++++++++++++--------------
 1 file changed, 15 insertions(+), 14 deletions(-)

diff --git a/doc/customization_api.texi b/doc/customization_api.texi
index 4baff3998b..2dc7fa1dec 100644
--- a/doc/customization_api.texi
+++ b/doc/customization_api.texi
@@ -1569,19 +1569,20 @@ For example:
 $converter->set_conf('footnotestyle', 'separate');
 @end example
 
-Some customization variables, in particular some customization variables
-associated with @@-commands, can be reset to the value they had before starting
-the conversion.  For example, they are reset in order to obtain their value
-before the conversion.  Also when their value at the end of the preambule or
-at the end of the document is needed, and 
-there are no @@-commands at those locations in the Texinfo manual.  If a value
-set by @code{set_conf} is intended to be found when the customization variable
-value is reset, @code{set_conf} should be called early.  For example, when 
called from
-a user-defined function called at different stage, it should be called in
-the @samp{setup} stage (@pxref{Init File Calling at Different Stages}).
+Some customization variables, in particular those associated with @@-commands,
+can be reset to the value they had before starting the conversion.  For
+example, they are reset in order to obtain their value before the conversion.
+Thet are also reset to the value they had before starting the conversion when
+their value at the end of the preambule or at the end of the document is
+needed, but there are no @@-commands at those locations in the Texinfo manual.
+If a value set by @code{set_conf} is intended to be found when the
+customization variable value is reset, @code{set_conf} should be called early.
+For example, when called from a user-defined function called at different
+stage, it should be called in the @samp{setup} stage (@pxref{Init File Calling
+at Different Stages}).
 
 The values set in converter with @code{set_conf} will not override command-line
-set customization variables, nor variables set in init files.  This is the
+set customization variables, nor variables set early in init files.  This is 
the
 expected behaviour, in particular when the values are set from the document.
 In the rare cases when overriding the customization would be needed, the
 @code{force_conf} functions can be used:
@@ -1608,9 +1609,9 @@ command-line and init file information.
 
 The main method to get information from the converter is @code{get_info}:
 
-@defun @var{$converter}->get_info ($info)
-Return information on @var{$info}.
-@end defun
+@deftypefun @var{$info} @var{$converter}->get_info (@var{$item})
+Return information on @var{$item}.
+@end deftypefun
 
 The available information is about:
 @table @code



reply via email to

[Prev in Thread] Current Thread [Next in Thread]