Dan Eble <d...@faithful.be> writes: > On Nov 21, 2014, at 04:53 , Urs Liska <u...@openlilylib.org> wrote: >> >> Am 21.11.2014 10:46, schrieb David Kastrup: >>> Urs Liska <u...@openlilylib.org> writes: >>> >>>> I just read about the " ly:one-line-breaking" function and thought it >>>> would be a good idea to have a "ly:one-page-breaking" complement for >>>> it too. >>>> This would produce a score with regular line length and paper width, >>>> but on one long page. > >>> So it would seem to me like we should likely be able to specify the page >>> breaking strategy (including none) and the line breaking strategy >>> (including none) independently. > >> Sorry, that's what I intended to say. >> I meant that any displaying entity (say an editor like Frescobaldi) >> could *decide* to use both options at the same time. But of course >> they should not be tied together. >> >> So, yes, this is two related but independent feature requests. > > What are the page-height limitations of the output formats that would > be used? Will the displaying program handle a page that is 3m long > (10 A4 pages). What about 30m? What about other viewing programs > that might be used for debugging?
We do not appear particularly concerned about that with ly:one-line-breaking and that one will result in quite larger dimensions. > Will the displaying program have to render the whole page in one shot > and cache the output for display? It might be more practical to > produce a score with one variable-height page per system and have the > displaying program stitch them together. Then it could ignore pages > that are not on screen so as not to waste time or memory. Setting systems-per-page to 1 is already feasible I think. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
