On Sun, Feb 08, 2015 at 02:42:56PM +, Gavin Smith wrote:
> On Fri, Feb 6, 2015 at 11:54 PM, Karl Berry wrote:
> > Possibly any xref command inside a multitable should be implicitly
> > handled as if enclosed in @w, to avoid the unable-to-find-the-reference
> > problem.
>
> Here's a possible f
Here's a possible fix.
Cool. I'm all for it, in principle, not that I have any particular
expertise in reviewing it. Barring comments from Patrice, might as well
try it (plus doc + test?)?
BTW, something strange went wrong in the email formatting as sent (I guess):
+if (grep {$_->{
-additional features needed to make @command{texi2html} a replacement
+additional features needed to make @command{texi2any} a replacement
Thanks for the careful reading, but it's written as intended.
Historically, Patrice started with texi2html and enhanced it to be a
replacement for C ma
It seems there is a typo in texinfo.texi (right?), patch
included. Please, CC me if you want to answer.
==
Askar Safin
http://vk.com/safinaskar
Kazan, Russia
--- a/doc/texinfo.texi 2015-02-07 22:41:33.604228200 +
+++ b/doc/texinfo.texi 2015-02-07 23:00:37.764228200 +
@@ -1805,7 +1805,
On Fri, Feb 6, 2015 at 5:11 PM, Gavin Smith wrote:
> I just noticed for the Info output of the following,
>
> @example
> y@c
>
> x
> aaa
> bb
> @end example,
>
> there is no indent for the line with "x" at all. The output looks like
>
> ==
> This is text.info, produ
On Fri, Feb 6, 2015 at 11:54 PM, Karl Berry wrote:
> Possibly any xref command inside a multitable should be implicitly
> handled as if enclosed in @w, to avoid the unable-to-find-the-reference
> problem.
Here's a possible fix.
Index: Plaintext.pm
