lilypond-devel
[Top][All Lists]
Advanced

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

Re: [PATCH] Fix issue with @qq{}


From: Reinhold Kainhofer
Subject: Re: [PATCH] Fix issue with @qq{}
Date: Sun, 10 Aug 2008 18:33:02 +0200
User-agent: KMail/1.9.9

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Sonntag, 10. August 2008 schrieb Reinhold Kainhofer:
> Am Sonntag, 10. August 2008 schrieb Patrick McCarty:
> > The latest commit (by Carl) introduced two @qq{} macros, which are not
> > recognized in scm/documentation-generate.scm.  This patch permits a
> > successful compilation of the IR and Info files in the event @qq{}
> > is used in doc strings.
>
> Why don't you use the @q and @qq definititions from macros.itely:
>
> @c to get decent quotes in `foo' and ``foo''
> @macro q{TEXT}
> @address@hidden
> @end macro
>
> @macro qq{TEXT}
> @address@hidden
> @end macro
>
> This works also with PDF, info etc., which the current version does not (it
> actually completely removes the quote from the pdf file!)

And here's the corresponding patch. I also realized that in the IR we don't 
need glossary refs (which were not consistently defined anyway), so I removed 
them too. Plus, some @refs were missing their fifth argument, which we 
already fixed a while ago in macros.texi.

Okay to push to master? I'm already using it in dev/texi2html

Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, 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)

iD8DBQFInxhHTqjEwhXvPN0RAkYtAJ9GNktMuI5x0MvWdTmUIAWdgoS0HQCfS7q9
T0/vR5cvI8t1H53O1DcMWgY=
=kdZL
-----END PGP SIGNATURE-----

Attachment: documentation-generate.patch
Description: Text Data


reply via email to

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