Re: problematic node name characters

[Patrice Dumas]

On Tue, Aug 13, 2013 at 10:11:11PM +0000, Karl Berry wrote:
> 
> Am I wrong in thinking that not all occurrences of the problematic
> characters are problematic?  I feel like I have browsed Info files whose
> nodes have an occasional period or colon and it worked.  But maybe I am
> wrong.  And maybe a comma that is not followed by a space (since the
> commas on Node: lines always have a space after)?

I don't know for sure, I match on a comma, not on comma with space. 
For menu entries and cross-refs, I should have only warned for cases
that will cause trouble for sure.

> BTW, I imagine problems with Info index entries (containing colons) are
> similar.  People have *really* hated the warnings about those, so I
> wouldn't want to enable that by default.  Sometimes there is no rational
> way to substitute anything else.

I have done nothing for index entries (both index and node name) and 
listoffloats entries for now.  Do you want the same warnings as in
menus?

>     > 3) There could be an option to turn off that particular warning, so
>     > people who don't want to change their documents don't have to.
> 
>     Maybe this could be a customization variable?  
> 
> Agreed, that's a better idea.

What should it be?  For now the warnings are always on when doing
plaintext or Info.

-- 
Pat