-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Donnerstag, 23. Oktober 2008 schrieb Karl Berry: > > @[EMAIL PROTECTED] code inside w: c'}} produces a curly quote > > @[EMAIL PROTECTED] w inside code: c'}} produces a straigth quote > > Sigh. I don't have a good answer for you. The cause is the catcodes > being set at the "wrong" time (in this case), which is a fundamental > attribute of TeX. Can you just use the form you want?
for the @[EMAIL PROTECTED] we already changed it as a workaround. However, we have some @[EMAIL PROTECTED] (that macro is defined as in the sample file of my first mail) and we apparently cannot change this... > I am scared of this change. For one thing, if we're not running e-tex, > it will cause a temp file to be written and read on every @code (and > similar) command. That seems incredibly painful. Yes, that doesn't sound like a proper solution :( > Maybe we could make ` and ' active all the time, like " and other > characters are now. It is actually active all the time by default, but we need to deactivate it completely, since ' is the octave indicator for note pitches and thus must not appear as a curly quote! In particular, in standard music notation used practivally everywhere (and thus also in LilyPond) c' or do' is the note an octave up from c or do and c'' or do'' is the note an further octave up. The problem only shows when we try to disable curly quotes altogether. Cheers, Reinhold - -- - ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJAMKXTqjEwhXvPN0RAl/bAJ9r7eQL5RchMZJydG7lMi0O0eABFACfVMs6 iJHzxqEWb7i5OnKZDWUB8EU= =p3Ue -----END PGP SIGNATURE-----