The EPS files have some tricks to keep sizes small (load font files
directly from the FS), which requires -dNOSAFER, and makes them more
fiddly.
If you are trying to get up to speed with regression testing, you
could try running the whole thing (baseline and test) with
-dbackend=cairo which produc
Uh. I wonder if the resulting pdf, notwithstanding the directions to embed
the fonts, also requires something like nosafer to work...
On Sun, 29 Sept 2024, 09:31 Luca Fascione, wrote:
> I'm using the same options that gv uses, nosafer and all, and gv displays
> the file just fine. I've not fiddl
I'm using the same options that gv uses, nosafer and all, and gv displays
the file just fine. I've not fiddled with it enough to make gs
DRIVER=display work, because WSL2 and that driver don't seem to be on good
terms. But I'll spend some time on that today.
Because I'm still experimenting with thi
Ok so,
I looked in the PDF and I saw
I got a partial improvement using -dEPSCrop, now I get a pdf that gv will
open (but interestingly not okular, for some reason)
This is weird.
L
On Sun, Sep 29, 2024 at 9:33 AM Luca Fascione wrote:
> Uh. I wonder if the resulting pdf, notwithstanding the direc
Chrome displays it "ok" too (I'd swear there is a missing scanline at the
top, possibly two, and maybe one or two at the bottom)
L
On Sun, Sep 29, 2024 at 10:59 AM Luca Fascione wrote:
> Ok so,
> I looked in the PDF and I saw
> I got a partial improvement using -dEPSCrop, now I get a pdf that gv
On Sun, Sep 29, 2024 at 9:32 AM Luca Fascione wrote:
>
> I'm using the same options that gv uses, nosafer and all, and gv displays the
> file just fine. I've not fiddled with it enough to make gs DRIVER=display
> work, because WSL2 and that driver don't seem to be on good terms. But I'll
> spen
Brilliant.
Now that I got EPSCrop going, I am able to make my own rasters using mupdf,
and it's working well.
eps -> pdf takes ~ 70ms
pdf -> numpy array ~ 5ms (a 300dpi raster of 221x1884 pxl, I have run this
with 8x8 aa and aa disabled and I got the same speed)
SIFT feature detection -> 500ms
OR
We are happy to announce the release of LilyPond 2.25.20. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.4, the current stable
release.
Please refer to the Install
