[EMAIL PROTECTED] [EMAIL PROTECTED]
BTW, I'm imagining that we can use this same thing to solve some of our
node-name problem. That is, a menu item displayed as `foo"bar'
referring to a node named
foo"bar:.baz
could be output in info as:
[EMAIL PROTECTED] name="foo\"bar" node="foo\"bar:.baz"[EMAIL PROTECTED] Description.
(Similarly for xrefs, etc.)
This should fix things for periods, colons, and parentheses. Commas
would still be a problem because the @node source line itself relies on
commas for parsing, and introducing a quoting mechanism there would
cause more difficulties (TeX would have to understand it, yuck).
Fortunately, periods and colons are the characters users really need in
node names; complaints about commas are relatively rare.
The actual source of such a menu item will have to be yet another
syntax, perhaps
** "foo\"bar"("foo\"bar:.baz"). Description.
Would using ** to mean "quoted node syntax" cause any problems?
Else we can dream up something else ugly, like
[EMAIL PROTECTED] "foo..."
Whatever is easiest to deal with.
We could just output the source syntax in the Info file, I suppose, but
it seems like an explicit command that separates out the parts would be
a lot easier for info readers to parse.
I'm not burning to implement this right away or anything, but since
we're talking Info extensions, I thought I'd mention it. Any thoughts?
Thanks,
karl
_______________________________________________
Bug-texinfo mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-texinfo
