Torsten Hämmerle writes:
> Even JPEG is inferior for screenshots because it has been developed
> for photographs where you practically never have neighboring pixels of
> exactly the same colour.
"Desktop Wallpaper". "Translucent windows". "Antialiased fonts".
> Moreover, JPEG compression is
Hello,
On 11/10/18 12:49, Torsten Hämmerle wrote:
Urs Liska-3 wrote
What would be the remedy? A fix in the code to change the behaviour of
this specific combination? Or rather a "Known issue" addition to the NR?
Hmmm,
Given the fact that #ly:one-page-breaking is quite new (dating back to
Hi Raitis,
I'm afraid I don't understand your question.
Thomas
Original-Nachricht
Hi,
Here's the tiny showcase:
\version "2.19"
\book {
\paper { page-breaking = #ly:one-page-breaking }
\score { << \relative c { c } \chords { c } >> }
}
% lilypond --version
GNU
Urs Liska-3 wrote
> What would be the remedy? A fix in the code to change the behaviour of
> this specific combination? Or rather a "Known issue" addition to the NR?
Hmmm,
Given the fact that #ly:one-page-breaking is quite new (dating back to 2016)
and only part of the development versions of
Am 11.10.2018 um 12:23 schrieb Torsten Hämmerle:
Urs Liska-3 wrote
210 × 17428 mm
That's interesting… On my computer (Windows 10 64 bit), Adobe Reader XI
shows 210 x 5.080 mm.
But that seems to be a limitation of the Adobe Reader.
Considering the PDF (tested with 2.19.55, 2.19.82, 2.21.0),
Urs Liska-3 wrote
> 210 × 17428 mm
That's interesting… On my computer (Windows 10 64 bit), Adobe Reader XI
shows 210 x 5.080 mm.
But that seems to be a limitation of the Adobe Reader.
Considering the PDF (tested with 2.19.55, 2.19.82, 2.21.0), it says
This appears to be due to an odd interaction between one-page-breaking
and the default staff-affinity for ChordNames (which is #DOWN).
Adding this to the \score fixes it:
\layout { \context { \ChordNames
\override VerticalAxisGroup.staff-affinity = #UP } }
-- Aaron Hill
I'm not talking about the literal size of the PDF, but when seen in a
viewer, of course. It's hella long, like 40 times its width or something.
% pdfinfo main.pdf
Creator:LilyPond 2.19.80
Producer: GPL Ghostscript 9.25
CreationDate: Thu Oct 11 10:28:51 2018 EEST
Page size:
Hi,
Yes, with \chords (or \new ChordNames etc.) as last line the score, the PDF
page height will be 200 inches.
Aaron Hill wrote
> Interestingly, PNG 200dpi cropped is 164x137069 but only 291KB. Good
> compression. ;-)
/Off topic:/
That's the benefit of the PNG format for screenshots:
Am 11.10.2018 um 11:46 schrieb Thomas Scharkowski:
Could you specify "very long"?
LilyPond 2.19.82 on MacOS 10.14 produces a 37 KB pdf, which I would
call "quite short"
;-)
Thomas
210 × 17428 mm
on my computer. I would agree this is "long", especially given the
content ...
---
Could you specify "very long"?
LilyPond 2.19.82 on MacOS 10.14 produces a 37 KB pdf, which I would call
"quite short"
;-)
Thomas
--- Original-Nachricht
Hi, (I remembered to press "reply to all" this time)
I thought this was pretty obvious if you try compiling this, but the
Hi, (I remembered to press "reply to all" this time)
I thought this was pretty obvious if you try compiling this, but the
resulting PDF from the example is very long and it shouldn't be that way.
Fortunately it looks like Aaron managed to reproduce it.
On Thu, Oct 11, 2018 at 12:32 PM Thomas
On 2018-10-11 12:33 am, Raitis Veinbahs wrote:
Hi,
Here's the tiny showcase:
\version "2.19"
\book {
\paper { page-breaking = #ly:one-page-breaking }
\score { << \relative c { c } \chords { c } >> }
}
% lilypond --version
GNU LilyPond 2.19.80
Repros on 2.19.48 (lilybin.com)
Repros on
13 matches
Mail list logo
