-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Montag, 31. März 2008 schrieb Graham Percival:
> > Graham (that's one of our Lilypond documentation team), which one is
> > better for lilypond?
>
> Umm. As I understand it, we need to rewrite something like this:
> @warning{each note is relative to the previous note in
> the input, not relative to the @code{c''} in the initial
> @code{\\relative} command.}
>
> into this:
> @warning{each note is relative to the previous note in
> the input, not relative to the @code{c''} in the initial
> @[EMAIL PROTECTED] command.}
>
> ?
Exactly, either @[EMAIL PROTECTED] or @[EMAIL PROTECTED]
> Well, if it needs to be done, we can do it. It makes the docs
> slightly harder to work with, but that's still better than having
> incorrect output.
>
> This only applies to @code{} that appears inside @warning{}, or
> other macros, right?
This applies to all arguments of custom-defined macros (i.e. everything inside
@warning, @q, @notation, etc.)
> We have over a thousand "@code{\foo}"
> strings inside the docs, and I'd really rather not rewrite them
> all.
If they work now: Why fix a running system?
@code is not a macro, but part of the texinfo spec. The problem only appears
with self-defined macros, where the arguments expansion is broken.
> Reinhold, could you modify macros.itely and tutorial.itely (search
> for "FIXME") accordingly, as well as writing-texinfo.txt (search
> for "warning", and add @bs{} to the list of commands).
So, should we use @bs{} or @value{backslash}?
Does this problem really appear only once in our whole documentation? There's
only that one FIXME in tutorial, and @value{backslash} is never used at
all...
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)
iD8DBQFH8UsgTqjEwhXvPN0RAhp/AJ45niWabCwwKo6PH/MmS06+1oGDWACg3g3Y
yJQOjmS8/otKWeq0tph6KzI=
=Xo6V
-----END PGP SIGNATURE-----
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
