Re: pdfeTeX error when compiling lilypond.texi with accents in node names

[Karl Berry]

      2019  ’  RIGHT SINGLE QUOTATION MARK
               [...]
               • this is the preferred character to use for apostrophe

I fail to see how this Unicode definition improved the situation over ',
but whatever, this is what makes the output looks right with today's
fonts, so fine, we should use it.

    We could call the single angle quote a "chevron", 

No.  Besides the reasons you cited, my brain is telling me that chevron
symbols are angled the other way (like a spread-out v).  Not to mention
we don't want to get in trouble with the Big Oil company by that name :).

    As for the "German" quote names, we can:

We've avoided aliases so far.  I don't think we should start now.

As for the names:
 Texinfo      Glyph Unicode  EC   HTML        LaTeX              Adobe
 --------------------------------------------------------------------------
 @lguillemet    «   U+00AB  "13  «  \guillemotleft      guillemotleft
 @rguillemet    »   U+00BB  "14  »  \guillemotright     guillemotright
 @lsguillemet   ‹   U+2039  "0E  ‹ \guilsinglleft      guilsinglleft
 @rsguillemet   ›   U+203A  "0F  › \guilsinglright     guilsinglright

 @quotebase     ‚   U+201A  "0D  ‚  \quotesinglbase     quotesinglbase
 @quotedblbase  „   U+201E  "12  „  \quotedblbase       quotedblbase

I'm thinking that maybe we should just always use the LaTeX/Adobe names?
I'm not sure I see a big advantage to defining new names, even if ours
are better :).  Not adding to the constant name proliferation seems like
better karma ...

    I think we should also define commands for the following glyphs, but

I don't have any special objections, but when is it useful to have the
commands instead of the characters that we have now?

Thanks,
Karl