Re: non web_version of web.texi ?
On Mon, Jul 06, 2020 at 11:26:46AM +0200, Han-Wen Nienhuys wrote:
> Just for clarity, I'm not against having web.texi as an info file or
> PDF file. It's just that I want to get rid of the special casing of
> web_version, which (when switched) off produces a doc with less links.
Ah sorry, it's been a while. It looks like web_version is
essentially:
if web_version
LilyPond looks amazing, for example
@uref{examples.html#Classical-Music, classical music}
@uref{examples.html#Complex-Notation, complex notation},
else
LilyPond looks amazing and can display classical music.
endif
Do the @uref lines look reasonable in info and pdf output?
It's possible that I just assumed that it wouldn't work, and added
an unnecessary "fix".
(Come to think of it, it might be possible to replace those lines
with simple @ref{}s.)
if web_version
@divIf{homepage-sidebar}
... links to download and manuals page...
@html
... some kind of javascript...
@end html
endif
I added the latter in e343a09657b87891893a4cca13e6c1a3d775f34f,
probably because the pdf looked weird, but I can't recall the
exact circumstances. Unfortunately the commit messages don't
explain much, as you've probably noticed. :(
Sorry I couldn't help more,
- Graham
Re: non web_version of web.texi ?
On Sun, Jul 5, 2020 at 11:54 PM Graham Percival wrote: > > 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). Just for clarity, I'm not against having web.texi as an info file or PDF file. It's just that I want to get rid of the special casing of web_version, which (when switched) off produces a doc with less links. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
PATCHES - Countdown for July 6th
Hello, Here is the current patch countdown list. The next countdown will be on July 8th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !222 extract_texi_filenames: print read files - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/222 !215 Fix negative spacing when stacking stencils - Jonas Hahnfeld https://gitlab.com/lilypond/lilypond/-/merge_requests/215 !214 Music_iterator cleanup - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/214 !209 DOC: Changes to the documentation on using Make with LilyPond - Fr. Samuel Springuel https://gitlab.com/lilypond/lilypond/-/merge_requests/209 Countdown: !224 Quote_iterator: use C++11 default member initialization - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/224 !221 aclocal: use include for the in-place build too - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/221 !220 Add Ghostscript commands to debug message if `-dgs-api=#f` - Masamichi Hosoda https://gitlab.com/lilypond/lilypond/-/merge_requests/220 !219 Return SCM_UNSPECIFIED rather than SCM_UNDEFINED - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/219 !218 Fix `-dgs-never-embed-fonts` - Masamichi Hosoda https://gitlab.com/lilypond/lilypond/-/merge_requests/218 !217 Stepmake: Fix uninstall process - Michael Käppler https://gitlab.com/lilypond/lilypond/-/merge_requests/217 Review: !226 Fix autogen.sh CFLAGS="foo bar" - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/226 New: No patches in New at this time. Waiting: !223 Clean up and annotate postprocess_html.py - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/223 !204 Move parallel processing to lilypond-book - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/204 !202 Fix xrefs in learning manual - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/202 !200 Add snippet translations - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/200 *** Regards, James
Re: [lilypond-book] @format environments
Am 06.07.2020 um 07:24 schrieb Werner LEMBERG: please see the attached files for a test case, [...] Thanks, looks good. Thanks for your feedback! 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. Ok, will test this, too. If no differences show up, I will file in a MR. Cheers, Michael
