Re: Warn about invalid node names

[Patrice Dumas]

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.

> Here we are talking about issues that produce bad Info output, one
> that causes Info readers to barf.  That's an entirely different ball
> game.  I can hardly see how people could be opposed to warnings that,
> if disregarded, will yield invalid output.

One reason I see is that it is an issue that is specific to the Info
output.

> 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.

-- 
Pat