[Top][All Lists]

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

Re: Warn about invalid node names

From: Eli Zaretskii
Subject: Re: Warn about invalid node names
Date: Tue, 13 Aug 2013 05:42:15 +0300

> Date: Mon, 12 Aug 2013 22:18:24 +0200
> From: Patrice Dumas <address@hidden>
> On Mon, Aug 12, 2013 at 10:21:38PM +0300, Eli Zaretskii wrote:
> > 
> > Those were warnings about questionable Texinfo practices that might
> > not be 100% in line with the language definition, but which produce
> > perfectly valid output.  Thus, those warnings could be considered
> > unhelpful, at least from some perspective.
> Maybe, but that was not my point, my point was thaat there were indeed
> users who did not like warnings.

Correction: users don't like unhelpful warnings.

> > The warning is about the Texinfo source.  Even if the user does not
> > produce Info at the moment, the Texinfo sources are invalid and should
> > be fixed.  There's nothing format-specific here.
> I may be missing something here, but I think that the issue is the
> production of invalid node names for Info readers.  The Texinfo source
> could be perfectly correct in such cases.  It wouldn't affect HTML,
> DocBook or TeX output.  In general, if node names with problematic
> characters are protected, for example with @asis{} (in menus, on @node
> lines, better use @comma{}), there won't be any issue at the Texinfo
> source level, but node names may be invalid for Info readers.

If the node names are invalid for Info, they are by definition
invalid, and need to be fixed at the Texinfo level.

Texinfo is a language that supports all of its output formats; if one
of those outputs is broken by a node name, the node name must be

reply via email to

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