Re: [lilypond-book] @format environments
> please see the attached files for a test case, [...] Thanks, looks good. > What I did not test, however, was texi2html-1.82. Well, it will take some time until we can move on to a newer version, so this has to be tested, too. > So I would vote to make > > @noindent > [Version string if needed] > @verbatim > ... > @end verbatim This is OK with me. Thanks for working on this! Werner
Re: non web_version of web.texi ?
Graham Percival writes: > On Sun, Jul 05, 2020 at 10:38:50PM +0200, Han-Wen Nienhuys wrote: >> is there any other function of web.texi besides producing the >> lilypond.org website? I would like to get rid of the "-D web_version" >> distinction, that is making web_version always be true for the web >> document. Is there any reason to not do this? > > IIRC there was an argument that all lilypond docs should be > available via info(1) and pdfs, and some parts of the website > qualified as "docs". The general intro to our manuals, for > example. Related commits: > ac3d9e3f836a56977ca09f89e7ffcfc189711743 > a060fc94b65dbc25a7e1ec20f2f79a58036a2546 > (general.texi was later renamed to web.texi) > > The argument on the mailing list was probably in 2009, although > just possibly it was late 2008 instead. I think that my original > idea was to just produce the html, while the person(s) who wanted > to have all docs available offline where you, Jan, John Mandereau, > and/or David Kastrup. (It was definitely an emacs user!) I am frequently using the Info files to look up stuff in the index and/or do full text searches as it so much more convenient and faster than messing with the HTML. Once I have found the stuff, I tend to do a web search for some longer phrase in order to point people to the corresponding online HTML. Emacs' LilyPond mode is pretty disgraceful compared to what Frescobaldi does (even though I taught it a better Midi input mode), so the argument that the Info files are a natural companion to Emacs' editing modes really does not have all that much weight: people would not change to using Emacs just for working with LilyPond. > A few months later, I was glad that I lost that argument, as it > provided a "starting point" to the dozen or so pdf manuals. > > I'm not aware of the current state & usage of lilypond docs, so I > have no position on whether it's worth keeping the "full offline > capability". If there's a serious desire to make web.texi > HTML-only, then it might even be worth adding that to the tarball > of pdfs (if those are still being distributed). > > Cheers, > - Graham > > -- David Kastrup
Re: non web_version of web.texi ?
On Sun, Jul 05, 2020 at 10:38:50PM +0200, Han-Wen Nienhuys wrote: > is there any other function of web.texi besides producing the > lilypond.org website? I would like to get rid of the "-D web_version" > distinction, that is making web_version always be true for the web > document. Is there any reason to not do this? IIRC there was an argument that all lilypond docs should be available via info(1) and pdfs, and some parts of the website qualified as "docs". The general intro to our manuals, for example. Related commits: ac3d9e3f836a56977ca09f89e7ffcfc189711743 a060fc94b65dbc25a7e1ec20f2f79a58036a2546 (general.texi was later renamed to web.texi) The argument on the mailing list was probably in 2009, although just possibly it was late 2008 instead. I think that my original idea was to just produce the html, while the person(s) who wanted to have all docs available offline where you, Jan, John Mandereau, and/or David Kastrup. (It was definitely an emacs user!) A few months later, I was glad that I lost that argument, as it provided a "starting point" to the dozen or so pdf manuals. I'm not aware of the current state & usage of lilypond docs, so I have no position on whether it's worth keeping the "full offline capability". If there's a serious desire to make web.texi HTML-only, then it might even be worth adding that to the tarball of pdfs (if those are still being distributed). Cheers, - Graham
non web_version of web.texi ?
Hi there, is there any other function of web.texi besides producing the lilypond.org website? I would like to get rid of the "-D web_version" distinction, that is making web_version always be true for the web document. Is there any reason to not do this? -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
