2018-09-16 21:28 GMT+02:00 Dan Eble :
>> Real
>> Page_breaking::page_height (int page_num, bool last) const
>> {
>> // The caches allow us to store the page heights for any
>> // non-negative page numbers. We use a negative value in the
>> // cache to s
Never mind. I only focused on half the comments.
Sorry for the noise.
Carl
Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Isnt this talking about negative page heights, not negative page numbers?
Carl
Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lily
Am 16. September 2018 21:28:26 MESZ schrieb Dan Eble :
>> Real
>> Page_breaking::page_height (int page_num, bool last) const
>> {
>> // The caches allow us to store the page heights for any
>> // non-negative page numbers. We use a negative value in the
>
> Real
> Page_breaking::page_height (int page_num, bool last) const
> {
> // The caches allow us to store the page heights for any
> // non-negative page numbers. We use a negative value in the
> // cache to signal that that position has not yet been initialized.
>
Thanks Trevor.
https://codereview.appspot.com/151230044/diff/40001/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
https://codereview.appspot.com/151230044/diff/40001/Documentation/notation/spacing.itely#newcode1000
Documentation/notation/spacing.itely:10
LGTM, Valentin, apart from a trivial nit-pick.
Trevor
https://codereview.appspot.com/151230044/diff/40001/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
https://codereview.appspot.com/151230044/diff/40001/Documentation/notation/spacing.itely#newcode100
Greetings,
having pushed the recent "string-number-styles" patch, I thought another
area where we might benefit from roman numerals would be page numbers.
This is an attempt at getting there.
https://codereview.appspot.com/151230044/
__
Keith: Comment #3 on issue 2794
> Well, I'll complain; I prefer having page numbers at the start of each book
> part. I propose in 'titling-init.ly' to
> change "print-page-number-check-first" back to
> #(define (print-page-number-check-first layout pr
In message <[EMAIL PROTECTED]>,
Joe Neeman <[EMAIL PROTECTED]> writes
There was a request a while back about making the places for page turns
more flexible. With the solution I have in mind for this, you would be
able to say that it should turn only after even pages and the first
page should be
nd which one is
preferable depends on conditions - will I be trying to turn a page
that's pegged onto the stand to prevent it blowing away in the wind ...
I hope you've probably already made it choosable, but it needs to be
user-specified whether the page-turn-page-breaker is invoked afte
Han-Wen Nienhuys wrote:
Han-Wen,
I second the suggestion that print-page-number should be #t by
default; this is causing a lot of confusion to some people. Could
this be done before 2.10?
Certainly. Please apply/revert this change. The last I can remember is
that Mats changed the name
Graham Percival escreveu:
Carlo Stemberger wrote:
“print-page-number = ##t” should be the default (so unnecessary), but
I must put this command into a \paper block so that version 2.8 (also
2.8.7) generates page numbers.
Han-Wen,
I second the suggestion that print-page-number should be #t
sary), but
I must put this command into a \paper block so that version 2.8
(also 2.8.7) generates page numbers.
Han-Wen,
I second the suggestion that print-page-number should be #t by
default; this is causing a lot of confusion to some people. Could
this be done before 2.10?
Cheers
Carlo Stemberger wrote:
“print-page-number = ##t” should be the default (so unnecessary), but I must
put this command into a \paper block so that version 2.8 (also 2.8.7)
generates page numbers.
Han-Wen,
I second the suggestion that print-page-number should be #t by default;
this is
Joe Neeman wrote:
Done. And here is some suggested documentation.
Thanks! I rewrote it a bit (see below); please commit.
Cheers,
- Graham
Index: ChangeLog
=
On Sat, 2006-09-30 at 11:47 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman schreef:
> > This is sort of a bug fix, but I thought I'd post it instead of
> > committing because it changes behaviour. In current lily CVS, it's
> > assumed that the first page of a book is always the left-hand page. This
>
Joe Neeman schreef:
This is sort of a bug fix, but I thought I'd post it instead of
committing because it changes behaviour. In current lily CVS, it's
assumed that the first page of a book is always the left-hand page. This
is usually false: odd-numbered pages should go on the right and the
first
This is sort of a bug fix, but I thought I'd post it instead of
committing because it changes behaviour. In current lily CVS, it's
assumed that the first page of a book is always the left-hand page. This
is usually false: odd-numbered pages should go on the right and the
first page is usually page
Werner LEMBERG writes:
> I would like to see, say,
>
> Layout output to `foo.ps' [1][2][3]
>
> similar to TeX. Is this possible?
Not without writing some code. IIRC, lilypond now prints the measures
where the page breaks fall. That tells you more than just the number
of pages alone.
Jan.
-
I would like to see, say,
Layout output to `foo.ps' [1][2][3]
similar to TeX. Is this possible?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Butting in well late on this thread I know, so ignore me if you want :-)
But having hit this problem repeatedly with word-processors and trying
to print certain pages (like restarting page numbers at 1 ten pages in
and trying to print the second page 1 ...) I think you need to have the
concept
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> in 2.3, you will have to make several \book, each of which starts
> afresh on page 1.
I didn't know it could have several \book blocks! And it gerenates
different files for each block (like foo.ps, foo-1.ps, ...). That's
pretty cool!
Pedro
__
[EMAIL PROTECTED] writes:
> Will this patch also make it possible to reset the page numbering
> between scores if you have have several \score in the same
> .ly file? This would be convenient, for example, if you want
> to typeset a number of instrumental part with a single call to
> lilypond.
in
Mats Bengtsson <[EMAIL PROTECTED]> writes:
> Will this patch also make it possible to reset the page numbering
> between scores if you have have several \score in the same
> .ly file?
I don't think so :-(
Pedro
___
lilypond-devel mailing list
[EMAIL
t page-number is always initialized to
zero. Looks like a bug...
patch appreciated.
I added the "initialpagenumber" parameter to make lilypond start on
other page numbers than 1. The code seems to be working so I commited
it to cvs. There is one catch, thought, the page number in the fir
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> how about firstPageNumber ? (or firstpagenumber)
sounds good to me. I've changed to firstpagenumber. I commited the
changes and updated the manual.
Pedro
___
lilypond-devel mailing list
[EMAIL PROTECTED]
lilypond start on,
> >> say, page 2? Looking into framework-ps.scm, function
> >> `output-framework', I see that page-number is always initialized to
> >> zero. Looks like a bug...
>
> > patch appreciated.
>
> I added the "initialpagenumber" param
-ps.scm, function
>> `output-framework', I see that page-number is always initialized to
>> zero. Looks like a bug...
> patch appreciated.
I added the "initialpagenumber" parameter to make lilypond start on
other page numbers than 1. The code seems to be working so I
[EMAIL PROTECTED] writes:
>
> Since the old `pagenumber' parameter of \paper is gone for the PS
> backend (why?), what shall be used instead to make lilypond start on,
> say, page 2? Looking into framework-ps.scm, function
> `output-framework', I see that page-number is always initialized to
> ze
Since the old `pagenumber' parameter of \paper is gone for the PS
backend (why?), what shall be used instead to make lilypond start on,
say, page 2? Looking into framework-ps.scm, function
`output-framework', I see that page-number is always initialized to
zero. Looks like a bug...
Werner
31 matches
Mail list logo
