"Phil Holmes" <[email protected]> writes: > "David Kastrup" <[email protected]> wrote in message > news:[email protected]... >> "Phil Holmes" <[email protected]> writes: >> >>> Looks like a bug to me: it doesn't work on windows even if you ignore >>> the command line and set the options in the lilypond file: >>> >>> #(ly:set-option 'resolution 169) >>> #(ly:set-option 'pixmap-format "pngalpha") >>> >>> resolution is set, tranparent not. Comment out the resolution line >>> and all is OK. >> >> Is there a way to see what options Ghostscript is getting called with >> from LilyPond? >> >> Under Linux, it would be easy enough to point PATH at directory >> including a "gs" script that not just calls gs but also records the >> command line arguments. >> >> Windows? > > Just knocked up a c# app. Results all look like they should. Further > testing shows that the two options together work for resolutions up to > 160 dpi, but fail above that...
That's more or less the switchover point ( > 150 dpi) between nostrokeadjust and strokeadjust. However, 2.16 and 2.18 always switched strokeadjust on explicitly anyway. It's only 2.19 that lets the "natural" setting run its course. So I am pretty much at a loss here. At any rate, it would appear that it is Ghostscript itself that cannot deal with the settings for whatever reason. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
