Am 25.07.2018 um 17:10 schrieb Torsten Hämmerle:
Urs Liska-3 wrote
OK, I now see, there is also a reference to "ignore spaces" somewhere in
the verbose log output.
I rather suspect (that's a Pango issue) that the font name specified in
LilyPond is tweaked (ignore case and spaces) in order to
Am 25.07.2018 um 19:03 schrieb Werner LEMBERG:
It seems that LilyPond's fc-list does not search anything below
/usr/share/texmf, which is (I suppose) where TeX Live has installed
fonts. OTOH Debian's fc-list *does* search in
/usr/share/fonts/X11/Type1 where LilyPond finds the fonts I'm
current
Am 25.07.2018 um 18:50 schrieb Urs Liska:
Am 25.07.2018 um 18:35 schrieb Werner LEMBERG:
Have you played with the `FC_CONFIG' environment variable? Say
FC_CONFIG=31 fc-list | less
to get a *very* detailed output how fontconfig finds something. You
might then compare the outputs of th
> It seems that LilyPond's fc-list does not search anything below
> /usr/share/texmf, which is (I suppose) where TeX Live has installed
> fonts. OTOH Debian's fc-list *does* search in
> /usr/share/fonts/X11/Type1 where LilyPond finds the fonts I'm
> currently looking at.
Well, lilypond installs
Am 25.07.2018 um 18:35 schrieb Werner LEMBERG:
Have you played with the `FC_CONFIG' environment variable? Say
FC_CONFIG=31 fc-list | less
to get a *very* detailed output how fontconfig finds something. You
might then compare the outputs of the two programs.
Sorry, this must be `FC_DEB
>> Have you played with the `FC_CONFIG' environment variable? Say
>>
>>FC_CONFIG=31 fc-list | less
>>
>> to get a *very* detailed output how fontconfig finds something. You
>> might then compare the outputs of the two programs.
Sorry, this must be `FC_DEBUG=31'.
> So I realize that my pro
Urs Liska-3 wrote
> OK, I now see, there is also a reference to "ignore spaces" somewhere in
> the verbose log output.
I rather suspect (that's a Pango issue) that the font name specified in
LilyPond is tweaked (ignore case and spaces) in order to find the
corresponding font file and then, font s
Am 25.07.2018 um 15:04 schrieb Torsten Hämmerle:
Urs Liska-3 wrote
What makes me wonder even more is that in a LilyPond file the following
two are possible (i.e. call the right font):
\override TextScript.font-name = "TeX Gyre Adventor Bold Italic"
\override TextScript.font-name = "TeXGyreAdv
Am 25.07.2018 um 14:21 schrieb Werner LEMBERG:
OK, we're getting closer. There is a *substantial* difference in the
results of fc-list | grep TeX when run from the system fontconfig
and the one packaged with LilyPond:
Have you played with the `FC_CONFIG' environment variable? Say
FC_CONF
Urs Liska-3 wrote
> What makes me wonder even more is that in a LilyPond file the following
> two are possible (i.e. call the right font):
>
> \override TextScript.font-name = "TeX Gyre Adventor Bold Italic"
> \override TextScript.font-name = "TeXGyreAdventor Bold Italic"
>
> but not this:
>
>
> OK, we're getting closer. There is a *substantial* difference in the
> results of fc-list | grep TeX when run from the system fontconfig
> and the one packaged with LilyPond:
Have you played with the `FC_CONFIG' environment variable? Say
FC_CONFIG=31 fc-list | less
to get a *very* detaile
Am 25.07.2018 um 12:41 schrieb Federico Bruni:
What *would* be interesting is to see the output from that "LilyPond
fc-list", but that fails with "Fontconfig error: Cannot load default
config file". Any idea how I can get that to run?
Can you find the fonts.conf file in that installation
Il giorno mer 25 lug 2018 alle 8:19, Urs Liska
ha scritto:
[~]$ /opt/lilypond/usr/bin/fc-list --version
fontconfig version 2.8.0
[~]$ fc-list --version
fontconfig version 2.13.0
I'm not sure this is really relevant. The fact is that the libraries
are *different*, so there's a differ
Am 25.07.2018 um 07:19 schrieb Federico Bruni:
Il giorno mar 24 lug 2018 alle 21:37, Urs Liska
ha scritto:
Am 24.07.2018 um 20:48 schrieb David Wright:
On Tue 24 Jul 2018 at 18:50:27 (+0200), Urs Liska wrote:
Is it possible that the problem is due to an old fontconfig version
used by
Il giorno mar 24 lug 2018 alle 21:37, Urs Liska
ha scritto:
Am 24.07.2018 um 20:48 schrieb David Wright:
On Tue 24 Jul 2018 at 18:50:27 (+0200), Urs Liska wrote:
Is it possible that the problem is due to an old fontconfig version
used by LilyPond? my Debian package is 2.13.0, the LilyPo
Am 24.07.2018 um 20:48 schrieb David Wright:
On Tue 24 Jul 2018 at 18:50:27 (+0200), Urs Liska wrote:
Is it possible that the problem is due to an old fontconfig version
used by LilyPond? my Debian package is 2.13.0, the LilyPond
directory suggests a version 1.9.2 (is that possible?).
Can y
On Tue 24 Jul 2018 at 18:50:27 (+0200), Urs Liska wrote:
> Is it possible that the problem is due to an old fontconfig version
> used by LilyPond? my Debian package is 2.13.0, the LilyPond
> directory suggests a version 1.9.2 (is that possible?).
Can you be a bit more specific about what versioni
Hi all (especially the font wizards),
I have a follow-up question and unfortunately some more problems.
There are some fonts that seem to be reported wrongly by LilyPond.
Strangely it appears that on others' systems it's *other* fonts that are
reported wrongly.
One example: TeX Gyre Adventor
Hi all,
thanks to all the feedback I got my head around the matter and could
complete a pull request for Frescobaldi.
I encourage anybody who runs Frescobaldi from the Git repository to
check out the 'show-available-fonts' branch and test the function
"LilyPond=>Show Available Fonts...".
D
> I *think* I've finally understood how to read the output:
>
> * The "names" part of the details has always one or two entries,
>never more.
> * The first of these names is always identical to the family name
> * If a second name is present this is the font weight this entry is
> * abou
Am 17.07.2018 um 22:47 schrieb Aaron Hill:
On 2018-07-17 13:37, Urs Liska wrote:
Oh my, then again I get:
Aachen Std
['Aachen Std,Aachen Std Bold']
['Bold,Regular']
where I can't imagine the two being synonyms. But
$ fc-list : family style | grep "Aachen Std"
Aachen Std,Aachen Std Bold:styl
Am 17.07.2018 um 22:56 schrieb Werner LEMBERG:
[...] I'm curious what output you'd get if you had both 08 and 12
installed.
fc-list gives
.../EBGaramond08-Italic.ttf: EB Garamond,EB Garamond 08:style=08
Italic,Cursiva,kurzíva,kursiv,Πλάγια,Italic,Kursivoitu,Italique,Dőlt,Corsivo,Cursief,
Werner LEMBERG wrote
> EB Garamond 08
> ['EB Garamond 08']
> ['Italic', 'Cursiva', 'kurzíva', 'kursiv', 'Πλάγια', 'Italic',
> 'Kursivoitu', 'Italique', 'Dőlt', 'Corsivo', 'Cursief', 'Kursywa',
> 'Itálico', 'Курсив', 'İtalik', 'Poševno', 'Etzana']
>
> […]
>
> BTW, for emmentaler-26.otf I
> [...] I'm curious what output you'd get if you had both 08 and 12
> installed.
fc-list gives
.../EBGaramond08-Italic.ttf: EB Garamond,EB Garamond 08:style=08
Italic,Cursiva,kurzíva,kursiv,Πλάγια,Italic,Kursivoitu,Italique,Dőlt,Corsivo,Cursief,Kursywa,Itálico,Курсив,İtalik,Poševno,Etzana
.
On 2018-07-17 13:37, Urs Liska wrote:
Oh my, then again I get:
Aachen Std
['Aachen Std,Aachen Std Bold']
['Bold,Regular']
where I can't imagine the two being synonyms. But
$ fc-list : family style | grep "Aachen Std"
Aachen Std,Aachen Std Bold:style=Bold,Regular
seems to confirm LilyPond's re
Am 17.07.2018 um 22:24 schrieb Aaron Hill:
On 2018-07-17 12:52, Urs Liska wrote:
Of course I can use the fontconfig commands to investigate the matter,
but in the end I'll have to take what LilyPond reports. I'm a little
bit disappointed that it doesn't tell me the filenames.
That is somethi
> Take this example (the formatting is already the result of parsing
> into Python objects:
>
> EB Garamond
> ['EB Garamond', 'EB Garamond 08']
> ['08 Italic', 'Cursiva', 'kurzíva', 'kursiv', 'Πλάγια', 'Italic',
> 'Kursivoitu', 'Italique', 'Dőlt', 'Corsivo', 'Cursief', 'Kursywa',
> 'Itálico', 'Ку
On 2018-07-17 12:52, Urs Liska wrote:
Of course I can use the fontconfig commands to investigate the matter,
but in the end I'll have to take what LilyPond reports. I'm a little
bit disappointed that it doesn't tell me the filenames.
That is something we could file a bug against. The code, as
Am 17.07.2018 um 19:43 schrieb Aaron Hill:
On 2018-07-17 08:06, Urs Liska wrote:
If I have a family of "Libre Baskerville Condensed" and the detail
string "Libre Baskerville Condensed:style=Italic"
this probably means the italic variant of that font. And in fact there
are three instances of th
On 2018-07-17 08:06, Urs Liska wrote:
If I have a family of "Libre Baskerville Condensed" and the detail
string "Libre Baskerville Condensed:style=Italic"
this probably means the italic variant of that font. And in fact there
are three instances of that font with three different styles.
And "Mon
Hi Aaron, thanks for the hints.
Am 17.07.2018 um 16:14 schrieb Aaron Hill:
On 2018-07-17 02:27, Urs Liska wrote:
Hi, when running with the -dshow-available-fonts option I get (among
others) a list of font familes with entries like the following:
family Verdana
Verdana:style=Standard,Normal,o
On 2018-07-17 02:27, Urs Liska wrote:
Hi, when running with the -dshow-available-fonts option I get (among
others) a list of font familes with entries like the following:
family Verdana
Verdana:style=Standard,Normal,obyčejné,Κανονικά,Regular,Normaali,Normál,Normale,Standaard,Normalny,Обычный,No
32 matches
Mail list logo
