[Top][All Lists]

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

Re: GDP: length/page-splitting of subsections

From: Han-Wen Nienhuys
Subject: Re: GDP: length/page-splitting of subsections
Date: Tue, 11 Sep 2007 23:15:42 +0200

2007/9/10, Graham Percival <address@hidden>:
> > At the very least, there are more (and more complex) things you can do
> > with dynamics (in Lilypond), and so that section alone would be long
> > enough to deserve its own HTML page.
> I'd certainly say so... but there's a large element of "the customer is
> always right" here.
> The all-in-one HTML page is **5 megs**.  I'm astounded that so many
> people (ie more than 0) are choosing to download that monster _every
> time_ they want to look something up in the docs.  That's a terrible
> waste of bandwidth, especially if you consider that the answer they're
> looking for is probably 1k of text and 100k of example picture.  To me,
> that sounds like a terrible indictment of how badly organized the docs are.
> Let me phrase this question differently:
> - if you currently use the all-in-one HTML page, how could we organize
> the non-all-in-one docs such that you use them?

I haven't followed the discussion in detail, but isn't this something
that should be handled by makeinfo? It has a --split-size argument,
but that only works for info and plain text. If we could set size
limits to html files too, wouldn't that solve the problem?

Han-Wen Nienhuys - address@hidden -

reply via email to

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