Re: Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command")

On Mon, 11 Aug 2008 22:43:30 +0200 Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > Although the texinfo manual does not explicitly forbid it, using > backslashes in node names causes problems with both texi2pdf and > texi2html: > > - -) texi2pdf throws an error (I don't know why, because "@" is

Re: index.html.in

On Mon, 11 Aug 2008 18:30:49 +0200 "John Mandereau" <[EMAIL PROTECTED]> wrote: > 2008/8/11 Graham Percival <[EMAIL PROTECTED]>: > > - do we list pdfs on this page itself, or on a separate page? (my > > opinion is for a separate page; we want to encourage users to > > download all pdfs, so that t

Re: index.html.in

On Mon, 11 Aug 2008 19:10:27 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/8/11 Reinhold Kainhofer <[EMAIL PROTECTED]>: > > >> BTW, where are we with the CSS thingy? > > > > You mean the new docs layout? > > No, I mean plain CSS coding, choosing nice colors, gradients and > all :-

Re: index.html.in

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieb John Mandereau: > 2008/8/11 Graham Percival <[EMAIL PROTECTED]>: > > Somebody should redo the index.html.in page. (the main doc page) > > I just did it because I added translation status page, and BTW I could > no lo

Re: Uses of @ref for xrefs in our docs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieb Reinhold Kainhofer: > Am Montag, 11. August 2008 schrieben Sie: > > On Mon, 11 Aug 2008 20:53:09 +0200 > > > > Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > > I fixed it even so that if you do e.g. @rglos{Top}, it

Docs: Using backslashed in node names causes problems with pdf and texi2html ("The \override command")

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Although the texinfo manual does not explicitly forbid it, using backslashes in node names causes problems with both texi2pdf and texi2html: - -) texi2pdf throws an error (I don't know why, because "@" is the command prefix and not "\" ...). We ne

Re: WANTED: Design for documentation (Photoshop power users!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear all, I suppose my last mail sounded too technical (thanks Valentin for pointing this out), so here I'm again with some clarifications: For the new Lilypond documentation we are looking for a good screen design (i.e. a mockup image of how the pa

Re: Uses of @ref for xrefs in our docs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieben Sie: > On Mon, 11 Aug 2008 20:53:09 +0200 > > Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > I fixed it even so that if you do e.g. @rglos{Top}, it will display > > the display name of the manual (i.e. the fifth

Re: Uses of @ref for xrefs in our docs

On Mon, 11 Aug 2008 20:53:09 +0200 Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > I fixed it even so that if you do e.g. @rglos{Top}, it will display > the display name of the manual (i.e. the fifth arguments to ref, > which we define in macros.itexi as "Music Glossary", "Snippets", > "Internals

Re: Uses of @ref for xrefs in our docs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieb Reinhold Kainhofer: > Am Montag, 11. August 2008 schrieb Graham Percival: > > What node name would we use? If we use @rglos{top}, would it > > appear as "Music glossary" (what we want), or "top"? > > Currently with t

Re: More broken links hunting in translations

Le 11.08.2008 18:56, John Mandereau disait : Hi, In the hunting for dead links in our docs, where Reinhold is already well involved :-), we should update docs sections to match those in the English doco, because the current internationalization system relies on the fact that node names are the s

Re: Banter chord naming convention

I am fine with dropping this code. On Mon, Aug 11, 2008 at 8:19 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote: > In responding to Trevor Daniels's review of NR 2.7 Chords, I came across the > fact that the Banter chord naming code is broken -- it will not produce > output for a simple c chord. >

Re: Uses of @ref for xrefs in our docs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieb Reinhold Kainhofer: > Am Montag, 11. August 2008 schrieb Graham Percival: > > On Sun, 10 Aug 2008 18:39:11 +0200 > > > > Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > > There are currently four spots, where an exp

Re: More broken links hunting in translations

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieb John Mandereau: > In the hunting for dead links in our docs, where Reinhold is already > well involved :-), Well, I was just checking what is still broken with texi2html using linkchecker... The current broken link

Re: index.html.in

2008/8/11 Reinhold Kainhofer <[EMAIL PROTECTED]>: >> BTW, where are we with the CSS thingy? > > You mean the new docs layout? No, I mean plain CSS coding, choosing nice colors, gradients and all :-) While we're talking about the toplevel documentation page, maybe we could make its layout more co

Re: -big-page.html for translated files? PDF for IR?

2008/8/11 Reinhold Kainhofer <[EMAIL PROTECTED]>: > I realized that we don't > generate translated -big-page.html files, and also no PDFs of the IR. Is > there a good reason for this, or should we add them to the makefiles? AFAICR, John chose not to have such pages because there was (and still is

More broken links hunting in translations

Hi, In the hunting for dead links in our docs, where Reinhold is already well involved :-), we should update docs sections to match those in the English doco, because the current internationaliation system relise on the fact that node names are the same in all languages, otherwise we end up with a

Re: Broken link rewriting in snippets

2008/8/10 Reinhold Kainhofer <[EMAIL PROTECTED]>: > The www-post script has another bug with link rewriting: For the snippets > pages, it checks and replaces links using the regexp: > r'href="(?:\.\./)?lilypond(|-internals|-learning|-program)' > Unfortunately, "lilypond-snippets-big-page.html

Re: Request for running texi2pdf in quiet mode

2008/8/8 John Mandereau <[EMAIL PROTECTED]>: > 2008/8/6 Reinhold Kainhofer <[EMAIL PROTECTED]>: >> Hrmpf, you are right, it does not print the error message itself, >> only "pdfetex exited with bad status, quitting". So I suppose we cannot >> easily get rid of the excessive output :( > > Yes, we ca

Re: index.html.in

2008/8/11 Graham Percival <[EMAIL PROTECTED]>: > Somebody should redo the index.html.in page. (the main doc page) I just did it because I added translation status page, and BTW I could no longer stand typing lilypond-learning.pdf URL by hand ;-) But consider this as a quick'n'dirty update, I agre

-big-page.html for translated files? PDF for IR?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While doing a check for broken links in the current texi2html-generated docs (which can be found at http://kainhofer.com/~lilypond/texi2html-out/Documentation/index.html and should be father complete, except for some broken images and some broken l

Re: Uses of @ref for xrefs in our docs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieb Graham Percival: > On Sun, 10 Aug 2008 18:39:11 +0200 > > Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > There are currently four spots, where an explicit @ref is used for a > > cross-reference to a different manua

Re: index.html.in

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 11. August 2008 schrieb Valentin Villenave: > 2008/8/11 Graham Percival <[EMAIL PROTECTED]>: > > Somebody should redo the index.html.in page. (the main doc page) > > BTW, where are we with the CSS thingy? You mean the new docs layout? Ther

Banter chord naming convention

In responding to Trevor Daniels's review of NR 2.7 Chords, I came across the fact that the Banter chord naming code is broken -- it will not produce output for a simple c chord. First question: Does anybody know when Banter chord naming quit working? In searching the internet to see more about Ba

Re: index.html.in

2008/8/11 Graham Percival <[EMAIL PROTECTED]>: > Somebody should redo the index.html.in page. (the main doc page) BTW, where are we with the CSS thingy? (Yes, this is pure thread-highjacking :-) Cheers, Valentin ___ lilypond-devel mailing list lilyp