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 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
> 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
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:
>
>
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
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
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
>> 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
Hi,
as a follow-up to my previous thread about text formatting
(http://lists.gnu.org/archive/html/lilypond-user/2018-07/msg00395.html)
(of which I'll soon post the results, I hope) I ran into some problems
handling \textLengthOn.
The following snippet shows two things: \textLengthOn is a glo
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
> 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: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
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 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
Urs Liska-3 wrote
> (markup in voice one will push the music in voice two)
Yes, but that's only natural:
(0) \textLengthOn affects any neighbouring objects and will even push away
the surrounding notes etc.
(1) TextScript.self-alignment-X ist set to #CENTER and in combination with
\textLengthOn
For those of you who engrave orchestral music in which the strings often have
your typical divisi a2 or a3
Suppose a performance is coming up and you need to print parts from the full
score.
So when you go to engrave the individual parts for any of the strings for
example, (say Violin I), would y
On 7/20/18 11:32 PM, Pierre Perol-Schneider wrote:
Hi Patrick,
Try:
\version "2.19.81"
{
\time 1/4
\override Hairpin.to-barline = ##f
a8\> b
c'4\!
}
{
\time 1/4
a8-\tweak to-barline ##f \> b
c'4\!
}
Cheers,
Pierre
I appreciate the advice. Can you explain why a break, whether a
No, I can't but I can give you a workaround:
\version "2.19.81"
\paper {
ragged-bottom = ##t
ragged-right = ##t
}
\relative c'' {
c1
\override Hairpin.to-barline = ##f d1\<
e1\!
}
\relative c'' {
\override Hairpin.to-barline = ##f
c1 c c c c c c c c c
d1-\tweak t
If that could help for understanding this behaviour, in the regression
tests, hairpin-barline-break.ly says:
"If a hairpin ends on the first note of a new staff, we do not print that
ending. But on the previous line, this hairpin should not be left open, and
should end at the bar line."
This probab
19 matches
Mail list logo
