lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Conversion of apostrophe in texi to PDF (was Re: Typos in LM)


From: Trevor Daniels
Subject: Re: Conversion of apostrophe in texi to PDF (was Re: Typos in LM)
Date: Wed, 15 Oct 2008 22:59:22 +0100


Reinhold Kainhofer wrote Wednesday, October 15, 2008 5:33 PM
Am Mittwoch, 15. Oktober 2008 schrieb Jonathan Kulp:
Reinhold Kainhofer wrote:
> It seems that texi2pdf replaces all single quotes by a smart right > quote. > Even if you use it inside @code{c'}, you'll not get a ' but a curved > one
> :(

I don't see how this is true,

It is true ;-)

though, because there are many examples of
single quotes in the .pdf learning manual (for example) that are *not*
smart quotes.  Look at section 2.1.1 on page 11, for example, where c'
e' g' e' appear with nice straight single quotes.

yes, that's because these examples do not use @code{...}, but rather
@example
....
@end example
blocks. Inside @example, smart quotes are note used, but all quotes inside
@code{..} ARE replaced by smart quotes, if there is an alphabetic character
before the quote.

See for example all the code blocks in the running text of section 2.1.4 in
the LM (p. 18 of the PDF).

All these bad examples have @code nested within another
construct, either @w or @warning.  There is one example
containing a straight code after an alphabetic character that
is not within another macro, and it remains straight.  It is
in 2.5.4 Absolute note names, second para, second sentence.
The source is:

"A @code{c'} will always mean middle C, a
@code{b} will always ..."

This quote remains straight in the pdf.

There's another example.  In 3.4.1 Soprano and cello
we have in the source:

"Remember to rename both
instances of all these names -- both the initial definition (the
@code{melody = \relative c' @{ } part) and the name's use (in the
@code{\score} section)."

The quote on c' also remains straight in the pdf.

So I'm guessing it is the double nesting that
causes the replacement.

I shall change one of the bad examples and push
to git origin/master to check.

Trevor





reply via email to

[Prev in Thread] Current Thread [Next in Thread]