[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
branch master updated: * tp/Texinfo/Convert/LaTeX.pm: move the nesting c
From: |
Patrice Dumas |
Subject: |
branch master updated: * tp/Texinfo/Convert/LaTeX.pm: move the nesting command issue way it has already been discussed |
Date: |
Tue, 26 Jul 2022 09:27:31 -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 49c223afee * tp/Texinfo/Convert/LaTeX.pm: move the nesting command
issue way it has already been discussed
49c223afee is described below
commit 49c223afee91cf88403442f72aa4f72c41c05c99
Author: Patrice Dumas <pertusus@free.fr>
AuthorDate: Tue Jul 26 15:26:19 2022 +0200
* tp/Texinfo/Convert/LaTeX.pm: move the nesting command issue way it has
already been discussed
---
tp/Texinfo/Convert/LaTeX.pm | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/tp/Texinfo/Convert/LaTeX.pm b/tp/Texinfo/Convert/LaTeX.pm
index 7e4d119331..fb1289bd63 100644
--- a/tp/Texinfo/Convert/LaTeX.pm
+++ b/tp/Texinfo/Convert/LaTeX.pm
@@ -62,10 +62,6 @@
# argument produces slanted typewriter (which is quite counter intuitive,
# by the way).
#
-# In Texinfo TeX, @code{@slanted{slanted in code}} and
-# @slanted{@code{code in slanted}} are different, @slanted{@code{code in
slanted}}
-# is not slanted. This has consequences in for @code formatting in @def*.
-#
# There is something about form feeds to do. There is some processing of form
# feeds right now, which simply amounts to keeping them in ignorable spaces
# (and with another condition that may not be relevant for LaTeX as the code
@@ -181,6 +177,14 @@
#
# index entry between @table and first @item causes an empty \item[] to be
# output.
+#
+# In Texinfo TeX, @code{@slanted{slanted in code}} and
+# @slanted{@code{code in slanted}} are different,
+# @slanted{@code{code in slanted}} is not slanted.
+# According to Karl, we should not try to specify what nested style commands
+# should be formatted as. So this should probably not be considered
+# as an issue, at least until we get user reports.
+# https://lists.gnu.org/archive/html/bug-texinfo/2006-06/msg00030.html
package Texinfo::Convert::LaTeX;
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- branch master updated: * tp/Texinfo/Convert/LaTeX.pm: move the nesting command issue way it has already been discussed,
Patrice Dumas <=