Le vendredi 25 décembre 2009 à 14:57 +, Graham Percival a écrit :
> I was wondering if I was wrong about texinfo. It's been known to
> happen.
Texinfo is not a well-defined language, it's defined only by what the
formatters support and to some extent by Texinfo manual, so it's
practically imp
On Fri, Dec 25, 2009 at 03:54:06PM +0100, John Mandereau wrote:
> Le vendredi 25 décembre 2009 à 14:29 +, Graham Percival a écrit :
> > > ..but see Texi2HTML warnings if "@insertcopying{}" is used.
> >
> > I know about those warnings.
>
> Then, why
Le vendredi 25 décembre 2009 à 14:29 +, Graham Percival a écrit :
> > ..but see Texi2HTML warnings if "@insertcopying{}" is used.
>
> I know about those warnings.
Then, why the mao do you waste our time with this thread? :-)
> I guess that in this case, it doesn
I mean, it's not /required/ for arguments without any macros, but...?
>
> ..but see Texi2HTML warnings if "@insertcopying{}" is used.
I know about those warnings. I've known about them for 6 months.
They seem to be harmless, so I've been waiting for somebody to
work
2HTML warnings if "@insertcopying{}" is used.
Best,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
commit 6c1cdaa331972442a8fd62d98da5adebfaa9a17b
I thought that texinfo macros were supposed to have a {} after them --
I mean, it's not /required/ for arguments without any macros, but...?
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-deve
