Werner LEMBERG a écrit :
Sorry, I don't understand the problem. Why will this lilypond fix
break something in Canorus or vice versa?
Canorus installs Truetype versions of some of those fonts,
system-wide. The Lilypond configure command finds some of those
truetype fonts via fc-match in preference of the usual Type1
versions coming with GhostScript. This causes compilation of
Lilypond to fail.
This part I have understood. But I don't see a problem if we make
lilypond find the Type 1 versions of the URW fonts.
lf I understand correctly, the point of this subthread is figuring out
how to check presence of all Type 1
URW fonts to convert them to OTF in the build process and install these
OTFs, which is for example
needed for reading SVG output. This checking is done via configure
script, so IMHO it's a different
issue from font selection by lilypond itself.
May I apply the patch below?
Best,
John
##################
diff --git a/configure.in b/configure.in
index d8f1199..d45c4c0 100644
--- a/configure.in
+++ b/configure.in
@@ -73,7 +73,7 @@ if test "$NCSB_DIR" != "" ; then
else
if test "$FCMATCH" != ""; then
for style in Roman Italic "Bold Italic" Bold; do
- NCSB_FILE=`$FCMATCH --verbose "Century Schoolbook L:style=$style" | grep 'file:' |
grep -v "\.ttf"`
+ NCSB_FILE=`$FCMATCH --verbose "Century Schoolbook L:style=$style:foundry=urw" |
grep 'file:' | grep -v "\.ttf"`
NCSB_FILE=`echo $NCSB_FILE | sed 's/^.*"\(.*\)".*$/\1/g'`
NCSB_FILE=`$PYTHON "$srcdir/scripts/auxiliar/readlink.py" $NCSB_FILE`
##################
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
