-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 20. Juli 2008 schrieb John Mandereau:
> On 2008/07/19 21:19 +0200, Reinhold Kainhofer wrote:
> > Okay, I've now added the script buildscripts/extract_texi_filenames.py to
> > create that list (tab-separated file with entries
> > NODENAME\tF
On Sun, 20 Jul 2008 23:22:45 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Looks pretty good in general; a few minor suggestions in attached
> patch.
Thanks, applied.
> Also, I'd still like to change the heading, "Input syntax" to
> something else. My current favourite is "Other notation"
Looks pretty good in general; a few minor suggestions in attached patch.
Also, I'd still like to change the heading, "Input syntax" to something
else. My current favourite is "Other notation" as this follows nicely after
the first two sections, rounding things off and providing a catch-all for
I think I've finished LM 1 Introduction -- in particular LM 1.2
About the documentation.
Could people check it out, make sure that what I've written there
matches with their idea of the doc organization, check that I
haven't missed anything, etc?
http://kainhofer.com/~lilypond/Documentation/user/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 20. Juli 2008 schrieb Reinhold Kainhofer:
> Am Sonntag, 20. Juli 2008 schrieb Trevor Daniels:
> > As I can't build the docs 'properly' under Windows I use texi2html to
> > check for errors, but it seems it doesn't flag up unmatched braces l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 20. Juli 2008 schrieb Trevor Daniels:
> As I can't build the docs 'properly' under Windows I use texi2html to check
> for errors, but it seems it doesn't flag up unmatched braces like the error
> you just fixed:
>
> For example, if a @nota
Sorry for breaking the doc build again, Neil, and thanks for fixing it.
As I can't build the docs 'properly' under Windows I use texi2html to check
for errors, but it seems it doesn't flag up unmatched braces like the error
you just fixed:
For example, if a @notation{rinforzando} dynamic mark
On Sun, 20 Jul 2008 10:33:18 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> please note however that this doesn't solve the issue John and
> Reinhold raised a few months ago: for the sake of consistency,
> whatever we're gonna do should involve *both* the website and the docs
> as a "gran
2008/7/19 Graham Percival <[EMAIL PROTECTED]>:
> Valentin, will you have 5 hours next week to handle this? Talk to
> people on -user, weigh ideas, and modify (I think!)
> Documentation/texinfo.css accordingly?
OK, will do.
please note however that this doesn't solve the issue John and
Reinhold
On Sun, 20 Jul 2008 09:02:56 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> I use this snippet in NR 3.3.3 Text encoding. There's no real need
> to display the lily code here, but it would be nice to continue to
> show the lily output, which displays just fine in pdf. Are you
> willing to l
Graham
I use this snippet in NR 3.3.3 Text encoding. There's no real need to
display the lily code here, but it would be nice to continue to show the
lily output, which displays just fine in pdf. Are you willing to let me
drop verbatim here (with a suitable comment, of course)?
Trevor
---
11 matches
Mail list logo
