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

[John Mandereau]

Le jeudi 26 juillet 2007 à 20:32 +0300, Oleg Katsitadze a écrit :
> On Thu, Jul 26, 2007 at 09:21:04AM +0200, John Mandereau wrote:
> > A related improvement would be adding a command like
> > @thinspace to insert a thin unbreakable space.
> 
> This should be easy to add.  This will make @dmn{} unnecessary, but
> whatever.  The question is, what should @thinspace produce in HTML and
> Info outputs?
> 
> As for Info, I guess we can omit the space.  This seems ok for
> guillemets and abbreviations like `p.123' (page 123).  Furthermore,
> @dmn{} omits the space, too.

Ommitting a space in Info would be weird for French typography:
@thinspace should be used before an exclamation or question mark and a
right guillemet, and after a left guillemet.  When the thin space is
unavailable, a plain or unbreakable space is generally used instead.


> As for HTML, there is a "hair space" (&#x200A), but it seems not to be
> widely supported by browsers:
> 
>   
> http://en.wikipedia.org/wiki/Space_%28punctuation%29#Space_characters_and_digital_typography
> 
> So maybe we should omit it in HTML, too.

I don't think so; why not use " "?  We already use it in LilyPond
HTML manual. " " is unbreakable in Mozilla Firefox.


> Finally, there is a thin space in UNICODE (U+200A).  Should we use it
> in Info output if encoding is UTF-8?

IMHO yes.

Cheers,
John