Issue 5467/3: Change font path loaded by EPS file when -dfont-export-dir
With LilyPond's commandline option -dfont-export-dir,
outputted PS / EPS files used absolute font path when font loading
by Ghostscript was requested.
This commit makes they always use relative font path
from lilypond-datadir same as without the -dfont-export-dir option.
Issue 5467/2: Define lilypond-datadir in exported font PS files
Exported font PS files didn't define lilypond-datadir.
However, to use relative font path, we need the define.
This commit makes define lilypond-datadir in the PS files.
Issue 5467/1: Fix make check without extractpdfmark
Without extractpdfmark,
make check failed because output-distance.py specified
the relative path from wrong origin for Ghostscript.
This commit makes output-distance.py specify correct absolute path.
-dfont-export-dir--> Fix make check without extractpdfmarkDiff:
http://lists.gnu.org/archive/html/lilypond-devel/2019-01/msg00113.html
Passes make, make check and a full make doc as a normal patch.
I also was able to make check with this patch when I didn't have extractpdfmark in the PATH.
Use
abs_dir--- this requires Issue 5466http://codereview.appspot.com/349110043
I've uploaded Patch Set 2.
This patch requires Werner's Issue 5466.
Passes make, make check and a full make doc all without using extractpdfmark
Patch on countdown for Feb 1st
Patch counte d down - please push.
I've pushed to staging.
commit a64b4dbc92ac0bbece08043349a55dccd84f4fd7
Issue 5467/3: Change font path loaded by EPS file when
-dfont-export-dircommit b0300944e015b5957e50441224699e55c68c3dc3
Issue 5467/2: Define
lilypond-datadirin exported font PS filescommit f76997b5097f588060f823c4c87f01bac9f2fe50
Issue 5467/1: Fix
make checkwithout extractpdfmark