Carl Peterson writes:
> I think we're getting hung up on the fact that SMuFL is being promulgated
> by a corporate entity and the only implementation of SMuFL is produced by
> that corporate entity (and that most of the musical font work is being done
> by other corporate entities releasing them
Johan Vromans schrieb:
>Carl Peterson writes:
>
>> I think we're getting hung up on the fact that SMuFL is being
>promulgated
>> by a corporate entity and the only implementation of SMuFL is
>produced by
>> that corporate entity (and that most of the musical font work is
>being done
>> by ot
Urs Liska writes:
> Johan Vromans schrieb:
>
>>Carl Peterson writes:
>>
>>> I think we're getting hung up on the fact that SMuFL is being
>>> promulgated by a corporate entity and the only implementation of
>>> SMuFL is produced by that corporate entity (and that most of the
>>> musical font wo
Is there a way to change the FretBoard size globally in a file? I'm
trying the following in my stylesheet, but I don't get it to work:
\context
{
\FretBoards
\override FretBoards.FretBoard #'size = #'-2
}
Jethro.
___
lilypond-user mailing li
Jethro Van Thuyne writes:
> Is there a way to change the FretBoard size globally in a file? I'm
> trying the following in my stylesheet, but I don't get it to work:
>
> \context
> { \FretBoards
> \override FretBoards.FretBoard #'size = #'-2
> }
That's not a compilable example. Try somethi
On 11/08/13 8:09 PM, David Kastrup wrote:
So far, I don't see that SMuFL is more than calling a particular
choice a standard. You could equally well say "why isn't Steinberg
picking up the Emmentaler standard?". SMuFL is a font layout. Saying
"it will be good to start thinking how LilyPond fon
Am 10.08.2013 10:30, schrieb David Kastrup:
Andrew Bernard writes:
This is of great interest to me because several of the people I do
scores for (contemporary composers) do not favour the very heavy black
Germanic look of the standard lilypond font, attractive though it may
be. It would be nic
Urs Liska writes:
> Am 10.08.2013 10:30, schrieb David Kastrup:
>> Andrew Bernard writes:
>>
>>> This is of great interest to me because several of the people I do
>>> scores for (contemporary composers) do not favour the very heavy black
>>> Germanic look of the standard lilypond font, attracti
Am 11.08.2013 14:43, schrieb David Kastrup:
Urs Liska writes:
Am 10.08.2013 10:30, schrieb David Kastrup:
Andrew Bernard writes:
This is of great interest to me because several of the people I do
scores for (contemporary composers) do not favour the very heavy black
Germanic look of the st
Urs Liska writes:
> Am 11.08.2013 14:43, schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> Adobe won't release their fonts under an open license, nevertheless
>>> we're happy to have standards that allow us to freely select from free
>>> and non-free fonts.
>> Correction: that allow those peopl
Am 11.08.2013 15:54, schrieb David Kastrup:
Urs Liska writes:
I don't think a GNU project should actively _prevent_ the use of
non-free software/fonts.
AS long as the Bravura font is available under the SIL open font
license, this is not really relevant to this discussion. But at any
rate, th
Hi all,
> 3)
> It's currently not really an option to tackle such a change from the
> technical POV.
> LilyPond is quite far away from being able to play together with other fonts.
>From my (perhaps naïve) perspective, this seems to be the chicken whence the
>egg comes. ;)
Put another way: If
Urs Liska writes:
> As I see it we have three core issues in this discussion. And we seem
> to be going in circles because of the interdependencies of these three
> issues:
More like because people don't listen and instead of addressing an
argument bring up something else again since there is mo
Kieren MacMillan writes:
> Hi all,
>
>> 3)
>> It's currently not really an option to tackle such a change from the
>> technical POV.
>> LilyPond is quite far away from being able to play together with other fonts.
>
> From my (perhaps naïve) perspective, this seems to be the chicken
> whence the
Hi,
just found a small bug in frameEngraver-bars-and-boxes.ly.
When the main *.ly file includes more than one *.ly file, like:
\include "1.ly"\include "2.ly"
... and each of those files (1.ly, 2.ly) includes frameEngraver-bars-and-boxes.ly, then I cannot compile the main.ly, because of:
fa
"Karol Majewski" writes:
> Hi,
>
> just found a small bug in frameEngraver-bars-and-boxes.ly.
>
> When the main *.ly file includes more than one *.ly file, like:
>
> \include "1.ly"
> \include "2.ly"
>
> ... and each of those files (1.ly, 2.ly) includes
> frameEngraver-bars-and-boxes.ly, then I c
Let's say I work on two pieces of music: piece-one.ly and piece-two.ly. Each of
them has some files included, like "deutsch.ly" or
"frameEngraver-bars-and-boxes.ly". Now I want to combine both files into one
PDF document. To achieve this, I create a new *.ly file (main.ly) which has
piece-one.l
Am 11.08.2013 19:13, schrieb Karol Majewski:
Let's say I work on two pieces of music: piece-one.ly and piece-two.ly. Each of them has some files
included, like "deutsch.ly" or "frameEngraver-bars-and-boxes.ly". Now I want to
combine both files into one PDF document. To achieve this, I create a
How would the code for that function look? I can't quite picture what you
mean.
Thanks!
Am 11.08.2013 19:13, schrieb Karol Majewski:
> Let's say I work on two pieces of music: piece-one.ly and piece-two.ly.
> Each of them has some files included, like "deutsch.ly" or
> "frameEngraver-bars-and-bo
Snowdusk wrote
> I would gladly include the example, if the coding isn't that long. I would
> need to include the example from the entire page to show that the page
> number is popping up too high. Otherwise, if I only include a few lines
> from the music score, it would look fine.
you can always
Can be downloaded from
https://www.dropbox.com/s/7zcup0cwc0i6870/lilydoc-2.17.24.pdf
56MB
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
21 matches
Mail list logo
