[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond-book on windows

From: David Kastrup
Subject: Re: lilypond-book on windows
Date: Thu, 12 Jan 2012 19:00:27 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux)

Reinhold Kainhofer <address@hidden> writes:

> On 12/01/2012 09:06, David Kastrup wrote:
>> "Trevor Daniels" <address@hidden> writes:
>>> Trevor Daniels wrote Wednesday, January 11, 2012 6:49 PM
>>>> To carry things to their logical conclusion I'm installing MikTeX to
>>>> see if it is possible to make Reinhold's code work as intended on
>>>> Windows.  Even if it does, I could not recommend downloading
>>>> 167Mbytes of MikTeX just to pick up these values automatically.
>>> Well, MikTex contains texi2dvi.exe, so I renamed this to texi2pdf.exe
>>> and added its directory to the MinGW path.
>> You need a TeX distribution anyway to create PDF from lytex files.  And
>> if you are not creating print copy there is no point in figuring out a
>> line width as it would deliver a result without any meaning (except if
>> for some reason you want notes in HTML use the same line breaks as in
>> print).  So if lilypond-book fails when creating HTML documentation
>> without a TeX distribution, this is a deficiency not just in Windows.
> Exactly, and as I said, it is supposed to work without texi2pdf (and/or
> a working TeX installation) available.
> However, even for HTML we need some kind of line width so that we can
> line-break all lilypond snippets.

That line width should be based on a pixel width (1024 is probably
reasonably).  It is nonsensical to have it based on a paper size.

> The default fallback value (which roughly corresponds to A4 with some
> margins) is an acceptable default value, so things should look okay in
> any case.

I don't think that we should "fall back".  When generating HTML, we
should not consider paper widths at all.

If lilypond-book calls texi2pdf in the course of generating HTML, that
is a bug.

> The problem is just that the subprocess module needs msvcrt on
> Windows, but that python as provided by lilypond does not ship that
> module. I would rather see this as a packaging problem, or am I seeing
> something wrong?

Sure, that too.  lilypond-book needs to figure out the paper width when
generating PDF via TeX.  Whatever is needed for that is needed.  But for
the HTML docs, nothing from the TeX toolchain should be required.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]