Re: strange result for escaping "\" with other font-name

[Masamichi HOSODA]

>> >>> >> > trying to escape "\" in a string leads to strange results, for some
>> >>> >> > font-names.
>> >>> >> > Example below was ok with 2.18.2
>> >>> >> >
>> >>> >> > \version "2.19.26"
>> >>> >> >
>> >>> >> > \markup \override #'(font-name . "Times New Roman") "\\<==what?"
>> >>> >>
>> >>> >> The displayed font is definitely not `Times New Roman'.  It seems
>> >>> >that
>> >>> >> the font substituted by FontConfig is a CJK font using half-width
>> >>> >> glyphs, and there it sometimes happens that the `\' slot gets
>> >>> >replaced
>> >>> >> with the Yen sign `¥', for compatibility with ancient Japanese
>> >>> >> practice.
>> >>> >>
>> >>> >
>> >>> >Agreed, so far.
>> >>> >
>> >>> >>
>> >>> >> I think there is nothing to be done here, since it displays a font
>> >>> >> problem (or bug).
>> >>> >>
>> >>> >
>> >>> >Though, if 2.18.2 displays nicely (and it does), I'd tend to think
>> >>> >something on our part causes this misbehahiour.
>> >>> >(Ofcourse "Times New Roman" _is_ installed)
>> >>> >
>> >>> >Cheers,
>> >>> >  Harm
>> >>> >_______________________________________________
>> >>> >bug-lilypond mailing list
>> >>> >address@hidden
>> >>> >https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> >>>
>> >>> Would you show us both 2.18.2 and 2.19.26 results of following command?
>> >>>
>> >>> $ FC_DEBUG=1 lilypond --verbose fonts-test-01.ly > result.txt 2>&1
>> >>>
>> >>
>> >> Will do in the evening. Have to run for my rl job :(
>> >>
>> >
>> > Got a spare minute.
>> >
>> > Remark: I always rename latest devel-version to lilydevel
> 
> 
> Many thanks for your time looking into this.
> 
>>
>>
>> Perhaps, it has two problems.
>>
>> First, both 2.18.2 and 2.19.26, fontconfig is requested "Times New" font,
>> instead of "Times New Roman".
>> Ofcourse, "Times New" font does not exist.
>> So fontconfig finds substitute font.
> 
> 
> Indeed very interesting that it can be done inserting the comma
> 
> \version "2.19.26"
> 
> \markup \override #'(font-name . "Times New Roman,") "\\<==what?"
> 
> http://sourceforge.net/p/testlilyissues/issues/4591/
> 
> Meanwhile I've found
> http://code.google.com/p/lilypond/issues/detail?id=699
> 
> Obviously it worked some time in the past, than not, than again ....

If I understand correctly,

Pango 1.23.0 (2009-02-03) was added "Roman" style.
https://git.gnome.org/browse/pango/commit/pango/fonts.c?id=b072c3353cc2d10d6b26fb86cb13694a967a59cd
https://git.gnome.org/browse/pango/commit/pango/fonts.c?id=07992d0e2c7cca25032aeac650c847a905079b23

So Pango 1.22.4 (2008-12-15) and below versions did not have "Roman" style.

Issue 699
http://sourceforge.net/p/testlilyissues/issues/699/
was reported 2008-10-24.

In other words, Pango at the time did not have "Roman" style.
So "Times New Roman" was interpreted "Times New Roman" font family
and no styles.

>> Second, your 2.19.26's fontconfig configure files
>> do not seem to have substitute settings.
> 
> It's not clear to me why this happens. Is it a LilyPond-problem or
> something at my part?
> With 2.18.2 and 2.19.26 I'm on a 64-bit LINUX
> Trying with a build from master, lilyDev (32bit Debian), I do get
> substitute settings
> 
> If I try
> \version "2.19.26"
> \markup \override #'(font-name . "not existing font") "\\<==what?"
> 
> I do get substitute settings as well.

According to the log file, your 2.19.26's fontconfig
default top configure file is
/home/hermann/lilydevel/usr/etc/fonts/fonts.conf

And, maybe,
/home/hermann/lilydevel/usr/etc/fonts/local.conf
/home/hermann/lilydevel/usr/etc/fonts/conf.d/*.conf
are fontconfig auxiliary configure files.

Your 2.18.2's one are
/home/hermann/lilypond/usr/etc/fonts/fonts.conf
/home/hermann/lilypond/usr/etc/fonts/local.conf
/home/hermann/lilypond/usr/etc/fonts/conf.d/*.conf

Would you compare them?