- **summary**: Change font path loaded by EPS file when `-dfont-export-dir` -->
Fix make check without extractpdfmark
- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,24 +1,24 @@
-Change font path loaded by EPS file when `-dfont-export-dir`
+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.
+ 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.
+ This commit makes they always use relative font path
+ from `lilypond-datadir` same as without the `-dfont-export-dir` option.
-Define `lilypond-datadir` in exported font PS files
+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.
+ 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.
+ This commit makes define `lilypond-datadir` in the PS files.
-Fix `make check` without extractpdfmark
+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.
+ 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.
http://codereview.appspot.com/349110043
~~~~
- **Needs**: -->
- **Comment**:
http://lists.gnu.org/archive/html/lilypond-devel/2019-01/msg00113.html
---
** [issues:#5467] Fix make check without extractpdfmark **
**Status:** Started
**Created:** Thu Jan 24, 2019 12:22 PM UTC by Masamichi Hosoda
**Last Updated:** Thu Jan 24, 2019 12:22 PM UTC
**Owner:** Masamichi Hosoda
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.
http://codereview.appspot.com/349110043
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
