Re: [PATCH] Re: Why is it _still_ so freaking hard to get info with images?

[David Kastrup]

John Mandereau <address@hidden> writes:

> 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"`
>

This should, I think, be an improvement over the previous situation.  At
least it would have stopped the problem I had.  From the discussion
afterwards, I _think_ that the resulting behavior should be more or less
acceptable.

However, Werner made it sound like Lilypond should come with its own
version of the fonts and use that, in which case it would seem sort of
pointless looking for the system-wide installation of those fonts.

So while the above patch fixes the symptom for the particular
configuration with which I encountered the problem, it may be possible
that we are barking up the wrong tree altogether trying to find the
right system font.

-- 
David Kastrup