index.html.in

Somebody should redo the index.html.in page. (the main doc page) - 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 they get the nice cross-references) - is everything linked to? I like ha

Re: Uses of @ref for xrefs in our docs

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 manual: > > changing-defaults.itely:@ref{Top,Internals > Reference,,lilypond-internals}. introduction.itely:@re

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

On 8/10/08 2:44 PM, "Patrick McCarty" <[EMAIL PROTECTED]> wrote: > On Sun, Aug 10, 2008 at 1:09 PM, Carl Sorensen <[EMAIL PROTECTED]> wrote: > >> I think @qq{} is the appropriate use here; it's used to identify a Scheme >> string. I'm glad that some patch is being prepared. > > Ah, okay. It's

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

On Sun, Aug 10, 2008 at 1:09 PM, Carl Sorensen <[EMAIL PROTECTED]> wrote: > > I apologize for this mistake. I discovered it and removed the @qq{} in my > local docs; I didn't think I had pushed that patch. I'm sorry. I'll try to > avoid > this problem in the future. No problem. > I think @qq{}

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

On Sun, Aug 10, 2008 at 9:33 AM, Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > 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 argume

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

Patrick McCarty gmail.com> writes: > > 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. I apologize for this

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

On Sun, Aug 10, 2008 at 06:33:02PM +0200, Reinhold Kainhofer wrote: > > > > 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} > > @[EMAIL PROTECTED] > > @end macro > > > > @macro qq{TEXT} > > @[EMAIL PROTECTED]

Uses of @ref for xrefs in our docs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There are currently four spots, where an explicit @ref is used for a cross-reference to a different manual: changing-defaults.itely:@ref{Top,Internals Reference,,lilypond-internals}. introduction.itely:@ref{Top,Music glossary,,music-glossary}: introd

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

-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 perm

Re: post-GDP doc team

Reinhold Kainhofer wrote Saturday, August 09, 2008 1:11 PM Am Montag, 28. Juli 2008 schrieb Graham Percival: On Sun, 27 Jul 2008 19:56:30 -0600 > Once I push changes to chords.itely, what triggers a new GDP build? Me logging into kainhofer.com and running: updatedocs.sh &> doclog.txt I genera

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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

Broken link rewriting in snippets

Hi John, 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" also matches this regexp, so internal links

[PATCH] Fix issue with @qq{}

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. That being said, I think @qq{} is supposed to be used for literal qu

Re: [PATCHES] Connected again but without Git pushing

John, you wrote Saturday, August 09, 2008 5:44 PM 2008/8/8 Trevor Daniels <[EMAIL PROTECTED]>: OK John - five patches pushed. Thank you Trevor! For next time you apply Git patches, you may want to try 'git am 000x-zzz', which preserves authoring info and create a commit automatically. Ah,