Hello David
No that does not work, you need to compile from git. You might notice that
your generated pdf file does not in fact have transparency. This is because
the gs version bundled with the LP webpage download is 9.21, which is very old
(2016ish). For this transparency thing to work we nee
Hello David,
I'm simply using a colored markup with alpha channel. Such as
\markup\with-color #(rgb-color 1 0 0 0.5) "a"
Cheers,
Valentin
13.09.2021 06:59:02 David Wright :
> On Sat 11 Sep 2021 at 21:35:00 (+0200), Valentin Petzel wrote:
>> From what I see pdftops appears to be intelligent eno
On Sat 11 Sep 2021 at 19:11:36 (-0700), H. S. Teoh wrote:
> I discovered that converting the pdf to ps and back again significantly
> reduces the file size. So it's kinda my poor-man's way of compressing
> pdfs. Of course, this only works if your pdf doesn't contain any
> features incompatible w
On Sat 11 Sep 2021 at 21:35:00 (+0200), Valentin Petzel wrote:
> From what I see pdftops appears to be intelligent enough to rasterize the
> file
> only if it does actually contain transparency. If it does it uses a much less
> smooth rasterization that is probably not fit for printing, so be ca
"H. S. Teoh" writes:
> On Sat, Sep 11, 2021 at 09:35:00PM +0200, Valentin Petzel wrote:
>> From what I see pdftops appears to be intelligent enough to rasterize
>> the file only if it does actually contain transparency. If it does it
>> uses a much less smooth rasterization that is probably not f
On Sat, Sep 11, 2021 at 09:35:00PM +0200, Valentin Petzel wrote:
> From what I see pdftops appears to be intelligent enough to rasterize
> the file only if it does actually contain transparency. If it does it
> uses a much less smooth rasterization that is probably not fit for
> printing, so be car
From what I see pdftops appears to be intelligent enough to rasterize the file
only if it does actually contain transparency. If it does it uses a much less
smooth rasterization that is probably not fit for printing, so be careful with
this! See the attached picture for a comparisation, the left
On Sat, Sep 11, 2021 at 12:04:11PM +0200, Valentin Petzel wrote:
> Okay. Basically the problem is that conversion from PDF to PS get’s
> really complicated at some point, and results in really large PS
> files.
>
> I’ve tracked down the responsible commit to be
> cf2ae39e9d93c2dcdc50afd7d0389c3148
On Fri 10 Sep 2021 at 13:52:04 (-0700), H. S. Teoh wrote:
> On Fri, Sep 10, 2021 at 09:52:09PM +0200, Jean Abou Samra wrote:
> > Le 10/09/2021 à 19:09, H. S. Teoh a écrit :
> > > OK, I attached a contrived .ly file that produces 2 pages of music
> > > (the effect is most noticeable when there's mor
> Okay. Basically the problem is that conversion from PDF to PS get’s
> really complicated at some point, and results in really large PS
> files.
>
> I’ve tracked down the responsible commit to be
> cf2ae39e9d93c2dcdc50afd7d0389c314898273c, which implements
> transparency for PDF. Now this seems
Okay. Basically the problem is that conversion from PDF to PS get’s really
complicated at some point, and results in really large PS files.
I’ve tracked down the responsible commit to be
cf2ae39e9d93c2dcdc50afd7d0389c314898273c, which implements transparency for
PDF. Now this seems plausible, a
On Fri, Sep 10, 2021 at 09:52:09PM +0200, Jean Abou Samra wrote:
> Le 10/09/2021 à 19:09, H. S. Teoh a écrit :
> > OK, I attached a contrived .ly file that produces 2 pages of music
> > (the effect is most noticeable when there's more than 1 page), and
> > two .pdf's, one compiled by the official D
Le 10/09/2021 à 19:09, H. S. Teoh a écrit :
OK, I attached a contrived .ly file that produces 2 pages of music (the
effect is most noticeable when there's more than 1 page), and two
.pdf's, one compiled by the official Debian lilypond package (2.22.1),
and one by my local lilypond build (latest g
Is it a problem with all documents, or only with specific ones? Can you give
us some example file where you get the problem (also maybe two pdf files
compiled with both versions)?
signature.asc
Description: This is a digitally signed message part.
On Fri, Sep 10, 2021 at 02:22:50PM +0200, Jonas Hahnfeld wrote:
> Am Freitag, dem 10.09.2021 um 10:46 +0200 schrieb Valentin Petzel:
[...]
> > This is nothing new and an arbitrary decision by Lilypond, simply
> > because XeTeX defaults to 1.5 and thus produces error when embedding
> > a 1.7 PDF.
>
Am Freitag, dem 10.09.2021 um 10:46 +0200 schrieb Valentin Petzel:
> Hello,
>
> This is nothing new and an arbitrary decision by Lilypond, simply because
> XeTeX defaults to 1.5 and thus produces error when embedding a 1.7 PDF.
>
> But this means that whatever problem you have should not come fr
Hello,
This is nothing new and an arbitrary decision by Lilypond, simply because
XeTeX defaults to 1.5 and thus produces error when embedding a 1.7 PDF.
But this means that whatever problem you have should not come frome the PDF
CompatibilityLevel, as this did never change (and anyway a lower v
Oh, is this why Adobe Reader has started putting up a box saying “preparing
output” when I open a LilyPond pdf?
Paul
Sent from my iPad
> On 10 Sep 2021, at 01:42, H. S. Teoh wrote:
>
> Hi all,
>
> For a long time I have been using a local build of lilypond cloned from
> git, IIRC around 2.2
Hi all,
For a long time I have been using a local build of lilypond cloned from
git, IIRC around 2.21.0 or thereabouts. Today, on a whim, I decided to
update lilypond to the latest git master. After recompiling everything,
lilypond started producing version 1.4 PDF files instead of version 1.7
l
19 matches
Mail list logo
