> Le 21 avr. 2023 à 15:18, Jean Abou Samra a écrit :
>
> The idea is that rather than putting all the .otf file in one directory, you
> make one subdirectory per font. Cf. the bit about recursive searching.
By the way, this is what we’re heading toward with SMuFL anyway. It doesn’t
> Now to the second approach, which I prefer. [...]
Me too. All your suggestions are sound, thanks.
Werner
> Le 21 avr. 2023 à 14:48, Wols Lists a écrit :
> Just to add to bikeshed colours, please DON'T call it "stylesheet". Call it
> the same name as the font, or something like that.
> If I've got a bunch of custom fonts I use, I just want to dump them in a
> directory and forget about them. If
On 21/04/2023 12:03, Kieren MacMillan wrote:
If, next to the .otf font file, a file called stylesheet.ily (or another
bikeshed color) is found, it is read and defines the style parameters. Because
we want to be able to apply it both globally and locally to one
score/bookpart/book, we take it
Le vendredi 21 avril 2023 à 07:03 -0400, Kieren MacMillan a écrit :
> How modular and adaptable will that be? In a robust stylesheet system, there
> would be “inheritance”, “cascading”, etc., rather than the “include and
> overwrite” that happens with [ad-hoc] stylesheets now.
"Inheritance" is
alternative music fonts.
As someone who (a) uses alternative music fonts for almost everything and (b)
upgrades often, this is a welcome MR. Thank you!
> Now, from the user point of view, the question is how we want to organize the
> UX of using an alternative music font:
> • Downlo
desirable to have
that in the medium term and I think it makes sense to keep it in mind for
designing this — at least, to avoid making changes that will complicate it.
Now, from the user point of view, the question is how we want to organize the
UX of using an alternative music font:
1. Download
> Le 3 avr. 2023 à 15:34, Werner LEMBERG a écrit :
>
> Yes. There is no equivalent to `glyphshow` in PDF. For some comments
> on that see, for example,
>
> https://bugs.ghostscript.com/show_bug.cgi?id=698305#c10
> https://bugs.ghostscript.com/show_bug.cgi?id=695259
OK, thanks.
> BTW,
>>> Essentially, this option switches between the `show` and `glyphshow`
>>> PostScript operators to access Emmentaler glyphs. The former is
>>> considered the 'standard' method for accessing glyphs in a PS file
>>> (according to the GS developers); however, it needs properly set up
>>> encoding
Jean Abou Samra writes:
> Le dimanche 02 avril 2023 à 18:20 +, Werner LEMBERG a écrit :
>> Essentially, this option switches between the `show` and `glyphshow`
>> PostScript operators to access Emmentaler glyphs. The former is
>> considered the 'standard' method for accessing glyphs in a PS
Le dimanche 02 avril 2023 à 18:20 +, Werner LEMBERG a écrit :
> Essentially, this option switches between the `show` and `glyphshow`
> PostScript operators to access Emmentaler glyphs. The former is
> considered the 'standard' method for accessing glyphs in a PS file
> (according to the GS
> Would anyone be able to explain me what the purpose of the
> music-font-encodings option is? I'm trying to understand how the
> generation of the Emmentaler font works. I see that there is quite
> a bit of infrastructure for this option, which is used in
> `--pspdfopt`, but
Hi,
Would anyone be able to explain me what the purpose of the music-font-encodings
option is? I'm trying to understand how the generation of the Emmentaler font
works. I see that there is quite a bit of infrastructure for this option, which
is used in `--pspdfopt`, but it's not clear to me
to
contact me and I'll do what is necessary. Or take the offer by other
friendly helpers.
Regarding the music font selection:
My uneasy feeling about breakinge existing code is surely invalid
because convert-ly will handle that easily.
That's good to hear. I'm not familiar enough with convert-ly
was
threefold:
a) (ACHIEVED.)
I needed the feature, right now. Well, turned out I didn't, but I
thought I do.
b) (ACHIEVED.)
I wanted to have a draft ready before some interface for the music font
changing is settled, because we might want to do both in one shot.
c) (TODO)
I hoped for a small
On 07/24/2014 01:08 AM, Alexander Kobel wrote:
https://code.google.com/p/lilypond/issues/detail?id=4014 ?
On the other hand, I actually don't know if it is correct when
I say: the Pango description string for the font, which is passed as-is
to the Pango interface. Is this Pango? Is it
for the announcement of the patch in its current shape
was threefold:
a) (ACHIEVED.)
I needed the feature, right now. Well, turned out I didn't, but I
thought I do.
b) (ACHIEVED.)
I wanted to have a draft ready before some interface for the music
font changing is settled, because we might want to do both
Hi,
2014-07-20 16:43 GMT+02:00 Abraham Lee tisi...@gmail.com:
On Sun, Jul 20, 2014 at 3:47 AM, Janek Warchoł janek.lilyp...@gmail.com
wrote:
A thought: i'm missing the possibility to set the weight of the music font
used by LilyPond for a particular score. In other words: let's
say i have
* ; music font
*gonville* ; piano brace font
FreeSerif
FreeSans
Inconsolata
(/ staff-height pt 20)))
}
I agree with David's comment here.
Btw, just to make sure: have you seen
https://code.google.com/p/lilypond/issues/detail?id=4014 ?
Hi all,
and Janek: thanks
(make-pango-font-tree
*lilyjazz* ; music font
*gonville* ; piano brace font
FreeSerif
FreeSans
Inconsolata
(/ staff-height pt 20)))
}
I agree with David's comment here.
Btw, just to make sure: have you seen
https://code.google.com/p/lilypond/issues
and piano-brace fonts are put at the first)
\paper {
#(define fonts
(make-pango-font-tree
*lilyjazz* ; music font
*gonville* ; piano brace font
FreeSerif
FreeSans
Inconsolata
(/ staff-height pt 20)))
}
I agree with David's comment here.
Btw, just to make
the change.
- Question 1: *Should the new syntax be something like this?* (where the
music and piano-brace fonts are put at the first)
\paper {
#(define fonts
(make-pango-font-tree
*lilyjazz* ; music font
*gonville* ; piano brace font
FreeSerif
FreeSans
Am 20.07.2014 11:47, schrieb Janek Warchoł:
Right now the font versions meant for smaller staff-sizes are
physically smaller. I think we could produced all versions in the
same size, just with different weights. I think that's how it's
done with text fonts - for example, a font has a display
Am 20.07.2014 11:47, schrieb Janek Warchoł:
A thought: i'm missing the possibility to set the weight of the music
font used by LilyPond for a particular score. In other words: let's
say i have an engraving with staff-size 16; Lilypond automatically
uses Feta16 for that. I'd like to be able
the possibility to set the weight of the music
font used by LilyPond for a particular score. In other words: let's
2
Yeah, that makes sense. That's exactly how Feta (Emmentaler) is
designed. Each optical size has a different weight, where heavier
ones are designed for smaller print sizes and lighter ones
the original functions. 99+% of the code is the same.
Putting the music/brace font arguments at the end also sound fine to me if
that works for everyone else.
Regards,
Abraham
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Next-step-for-easier-custom-music-font
like this?* (where the
music and piano-brace fonts are put at the first)
\paper {
#(define fonts
(make-pango-font-tree
*lilyjazz* ; music font
*gonville* ; piano brace font
FreeSerif
FreeSans
Inconsolata
(/ staff-height pt 20)))
}
- Question 2: *Should we require
experience the change.
- Question 1: *Should the new syntax be something like this?* (where
the
music and piano-brace fonts are put at the first)
\paper {
#(define fonts
(make-pango-font-tree
*lilyjazz* ; music font
*gonville* ; piano brace font
FreeSerif
FreeSans
Inconsolata
to be made regarding how users
would
experience the change.
- Question 1: *Should the new syntax be something like this?* (where
the
music and piano-brace fonts are put at the first)
\paper {
#(define fonts
(make-pango-font-tree
*lilyjazz* ; music font
*gonville* ; piano brace font
Some interesting activities on music fonts:
http://www.smufl.org/
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
about bugs that annoy many
people, and they waste a lot of your own time. Have you considered
organizing a collective bounty to fix that bug?
We now have a webpage for this:
http://lilypond.org/sponsoring.html
My main goal was to
attract attention to Emilio's nice project of music font
?)(was: Re: music font)
Let's take a look at the current statistics, shall we?
http://lilypond.org/~graham/maybe-missing-emails.html
[from 2011 Dec 01 to 2012 Jan 24]
Response category Number Percent of total
Less than 24 hours 50 68.49%
24 to 48 hours6 8.22%
More than 48 hours 8 10.96
On Tue, Jan 24, 2012 at 12:27:56PM -, Phil Holmes wrote:
Of course, a 96-hour reponse rate isn't precisely fantastic, but
it's a start.
Well - TBH time isn't of the essence as a general rule. Whether a
bug gets added to the tracker in one day or 3 rarely affects the
overall
2012/1/24 Graham Percival gra...@percival-music.ca:
Our published materials says 24 hours:
[...] we should update that accordingly.
http://codereview.appspot.com/5575047/ and stop worrying.
:)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
attention to Emilio's nice project of music font with LilyPond.
I attracted Graham's attention on me instead.
Well, you asked for Graham's attention when you cc'd him. I think
cc'ing him was a mistake, because:
- his function as administrator means that he won't do stuff like this
(help someone
Graham Percival gra...@percival-music.ca writes:
On Sun, Jan 22, 2012 at 12:05:46AM +0100, Xavier Scheuer wrote:
I am not a developer, just a simple user.
But I must say I am a bit disappointed no developer (except Janek)
replied to your e-mail.
And I'm a bit disappointed that you keep on
Thanks Janek for your suggestion. I'm looking at the gonville readme but it
will take me some time to understand, I'll let you know.
Of course I've tried some shortcuts before, I opened lilypond font (the 20pt
weight) in a font-editor, modified some glyphs and dropped an otf replacing the
old
Il 22/01/2012 09:40, Emilio Grazzi ha scritto:
[...]
Interpretazione della musica...
errore di programmazione: Errore FreeType: SFNT font table missing
continua, incrociare le dita
errore di programmazione: Errore FreeType: SFNT font table missing
continua, incrociare le dita
errore di
This is a split reply from the thread music font.
http://lists.gnu.org/archive/html/lilypond-devel/2012-01/msg00752.html
The title is a reference to the fist Users versus developers flame war
of which I appear to be also at the origin.
http://lists.gnu.org/archive/html/lilypond-user/2009-05
(except Janek)
replied to your e-mail.
Some of these developers are known to grump at the lack of investment
(mainly from users) to help improving LilyPond. And when a typographic
designer come with a music font and ask for help in order to run it
with LilyPond, these same developers simply ignore
On Sun, Jan 22, 2012 at 12:05:46AM +0100, Xavier Scheuer wrote:
I am not a developer, just a simple user.
But I must say I am a bit disappointed no developer (except Janek)
replied to your e-mail.
And I'm a bit disappointed that you keep on whining about
developers not doing what you want
2012/1/9 Emilio Grazzi i...@emiliograzzi.com:
Hi you all,
i'm a (typo)graphic designer from Italy and i'm about to finish my
dissertation about typography inside musical notation.
I would like to apply my result inside lilypond like it was for the gonville
font (
Hi you all,
i'm a (typo)graphic designer from Italy and i'm about to finish my dissertation
about typography inside musical notation.
I would like to apply my result inside lilypond like it was for the gonville
font ( http://www.chiark.greenend.org.uk/~sgtatham/gonville/ ).
The problem is that
2011/7/10 Bernardo Barros bernardobarr...@gmail.com:
I'm thinking of creating a font for contemporary music with the most
commonly used symbols.
I miss a lot of specific symbols and I'm sure a lot of LilyPond users do too.
I know that there are some sources for this purpose, and find them
Carl Sorensen schrieb:
[...]
Ok, so I'll go for this. It isn't as easy as I thought, because I cannot
just rotate the whole picture, because the path is too complex for metafont.
So I'll have to transform every point and draw thereafter. It seems to
work, but
I have to change some explicit
On 1/1/10 2:52 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
[...]
Ok, so I'll go for this. It isn't as easy as I thought, because I cannot
just rotate the whole picture, because the path is too complex for metafont.
So I'll have to transform every point and draw thereafter.
Carl Sorensen schrieb:
On 1/1/10 2:52 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
[...]
Ok, so I'll go for this. It isn't as easy as I thought, because I cannot
just rotate the whole picture, because the path is too complex for metafont.
So I'll have to
On 1/1/10 4:08 PM, Han-Wen Nienhuys hanw...@gmail.com wrote:
On Fri, Jan 1, 2010 at 2:21 PM, Marc Hohl m...@hohlart.de wrote:
IIUC, you should do the following:
1) Make a sample at 1200 dpi and post it somewhere so that we can be
satisfied that it looks right at 1200 dpi.
Ok, I
On Fri, Jan 1, 2010 at 9:18 PM, Carl Sorensen c_soren...@byu.edu wrote:
This doesn't make a lot of sense: you should print out the PDF on a
1200 dpi printer, and see how it looks on paper. Screen appearances
are misleading.
OK, so if we print it out on a 1200 dpi printer, how do we get
Carl Sorensen schrieb:
On 12/30/09 7:42 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
On 12/30/09 6:06 AM, Marc Hohl m...@hohlart.de wrote:
@Carl:
I am not at all familiar with SVG. Could you please produce a file
similar to the one you sent already with
Francisco Vila schrieb:
2009/12/29 Marc Hohl m...@hohlart.de:
I concatenated the pdfs to one file, which is too big for the list, so I
put it on my website:
http://www.hohlart.de/marc/gclef-slant.pdf
I know that there is a spurious error on value 2, but I think that's not the
main problem.
On 12/30/09 6:06 AM, Marc Hohl m...@hohlart.de wrote:
@Carl:
I am not at all familiar with SVG. Could you please produce a file
similar to the one you sent already with different rotating angles?
I can only produce a file like that with the clefs you have designed if you
generate svg
Carl Sorensen schrieb:
On 12/30/09 6:06 AM, Marc Hohl m...@hohlart.de wrote:
@Carl:
I am not at all familiar with SVG. Could you please produce a file
similar to the one you sent already with different rotating angles?
I can only produce a file like that with the clefs you have
Marc Hohl schrieb:
Francisco Vila schrieb:
Just to add a bit to the brainstorming:
The uppermost lace of our G-clef already was slightly oversized.
I cannot explain why, but latest proposals I've seen are getting it
even greater.
Anyone appreciates the same?
Well spotted. I was not sure
2009/12/29 Marc Hohl m...@hohlart.de:
I concatenated the pdfs to one file, which is too big for the list, so I
put it on my website:
http://www.hohlart.de/marc/gclef-slant.pdf
I know that there is a spurious error on value 2, but I think that's not the
main problem. Which value looks best?
On 12/29/09 1:54 PM, Marc Hohl m...@hohlart.de wrote:
Marc Hohl schrieb:
Francisco Vila schrieb:
Just to add a bit to the brainstorming:
The uppermost lace of our G-clef already was slightly oversized.
I cannot explain why, but latest proposals I've seen are getting it
even greater.
Francisco Vila schrieb:
Just to add a bit to the brainstorming:
The uppermost lace of our G-clef already was slightly oversized.
I cannot explain why, but latest proposals I've seen are getting it
even greater.
Anyone appreciates the same?
Well spotted. I was not sure whether this is kind
Marc Hohl m...@hohlart.de writes:
Carl Sorensen schrieb:
Looks good to me. I'd also like to see half-way between this attempt
and the first attempt, not because I think this is wrong, but because
I tend to find optimum settings by finding not enough and too
much and going between those
On 12/23/09 12:41 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
On 12/22/09 12:45 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
On 12/21/09 1:52 PM, Marc Hohl m...@hohlart.de wrote:
[...]
I like it much better. But I think
Just to add a bit to the brainstorming:
The uppermost lace of our G-clef already was slightly oversized.
I cannot explain why, but latest proposals I've seen are getting it
even greater.
Anyone appreciates the same?
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
No le
On 12/22/09 12:45 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
On 12/21/09 1:52 PM, Marc Hohl m...@hohlart.de wrote:
[...]
I like it much better. But I think that the bulb on the bottom of the clef
needs to shift slightly to the right with this change.
Carl Sorensen schrieb:
Jan Nieuwenhuizen janneke-list at xs4all.nl writes:
Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon
Tatham:
It's interesting that you should mention that: that actually reminds
me of one of my specific issues with Feta, namely that the curved
On Mon, Dec 21, 2009 at 8:08 AM, Marc Hohl m...@hohlart.de wrote:
It's interesting that you should mention that: that actually reminds
me of one of my specific issues with Feta, namely that the curved
centre line of its treble clef _does_ make it look to me as if it's
leaning over backwards.
On 12/21/09 3:08 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
Jan Nieuwenhuizen janneke-list at xs4all.nl writes:
Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon
Tatham:
It's interesting that you should mention that: that actually reminds
me
On 12/21/09 1:52 PM, Marc Hohl m...@hohlart.de wrote:
[...]
I like it much better. But I think that the bulb on the bottom of the clef
needs to shift slightly to the right with this change.
Like the attached one?
You may use the pdf file for a printout.
This may be a bit too much
On Sat, Nov 28, 2009 at 2:27 PM, Carl Sorensen c_soren...@byu.edu wrote:
It's interesting that you should mention that: that actually reminds
me of one of my specific issues with Feta, namely that the curved
centre line of its treble clef _does_ make it look to me as if it's
leaning over
On 2009-10-28, Patrick McCarty wrote:
On 2009-10-28, Patrick McCarty wrote:
On 2009-10-28, Neil Puttock wrote:
2009/10/20 Neil Puttock n.putt...@gmail.com:
2009/10/20 Patrick McCarty pnor...@gmail.com:
This should be fixed now in latest git.
Works for me.
I guess I
2009/10/29 Patrick McCarty pnor...@gmail.com:
This isn't entirely true, now that I look at it again. In this case,
gonville, gonville-brace, and aybabtu are all loaded, but aybabtu is
used for the braces.
Thanks for fixing this, Patrick; now I can compare and contrast the
ugliness of the
2009/11/1 Patrick McCarty pnor...@gmail.com:
On 2009-11-01, Neil Puttock wrote:
This is what I saw before reversing the settings (my latest commit),
and now everything loads fine for me.
Same here, but I can't see why you need to set font-defaults twice;
surely the first setting is ignored?
On 2009-11-01, Neil Puttock wrote:
2009/11/1 Patrick McCarty pnor...@gmail.com:
On 2009-11-01, Neil Puttock wrote:
This is what I saw before reversing the settings (my latest commit),
and now everything loads fine for me.
Same here, but I can't see why you need to set font-defaults
2009/10/20 Neil Puttock n.putt...@gmail.com:
2009/10/20 Patrick McCarty pnor...@gmail.com:
This should be fixed now in latest git.
Works for me.
I guess I spoke a bit prematurely here, since the fix you pushed
always loads aybabtu, even when font-defaults has been redefined.
I've tried
On 2009-10-28, Neil Puttock wrote:
2009/10/20 Neil Puttock n.putt...@gmail.com:
2009/10/20 Patrick McCarty pnor...@gmail.com:
This should be fixed now in latest git.
Works for me.
I guess I spoke a bit prematurely here, since the fix you pushed
always loads aybabtu, even when
On 2009-10-28, Patrick McCarty wrote:
On 2009-10-28, Neil Puttock wrote:
2009/10/20 Neil Puttock n.putt...@gmail.com:
2009/10/20 Patrick McCarty pnor...@gmail.com:
This should be fixed now in latest git.
Works for me.
I guess I spoke a bit prematurely here, since the fix you
On Mon, Oct 19, 2009 at 5:36 PM, Bertalan Fodor (LilyPondTool)
lilypondt...@organum.hu wrote:
Wow too.
Actually, there are things in Feta what I don't feel natural either.
For example: the caesura sign, the G-clef and the trill indication feels
better for me in Gonville.
Though the G-clef is
Op maandag 19-10-2009 om 20:49 uur [tijdzone +0200], schreef Jan
Nieuwenhuizen:
Hi Simon,
Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon
Tatham:
Jan Nieuwenhuizen janneke-l...@xs4all.nl wrote:
All I'd suggest is trivial changes to Lilypond to make it easy to
use an
Jan Nieuwenhuizen janneke-l...@xs4all.nl wrote:
is a bit problematic. We do not want to ship font binaries, but
I suppose we also do not want to add half an hour build time.
I guess you feel the same: it would really be nice if you found
a way to reduce the font build time :-)
Absolutely!
2009/10/20 Jan Nieuwenhuizen janneke-l...@xs4all.nl:
See
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=c56ba7b4abd3b27e96367ea04b37f2e1d3b77663
After this change, piano braces do not work. Would it require a
complete font build?
Drawing
On 2009-10-20, Francisco Vila wrote:
2009/10/20 Jan Nieuwenhuizen janneke-l...@xs4all.nl:
See
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=c56ba7b4abd3b27e96367ea04b37f2e1d3b77663
After this change, piano braces do not work. Would it require a
complete font
2009/10/20 Patrick McCarty pnor...@gmail.com:
This should be fixed now in latest git.
Works for me.
One little niggle remains: there are two grobs with font-family set to
'music (AmbitusAccidental and Clef), which means they ignore the
font-family change unless it's explicitly set (i.e.,
Op dinsdag 20-10-2009 om 09:47 uur [tijdzone -0700], schreef Patrick
McCarty:
On 2009-10-20, Francisco Vila wrote:
2009/10/20 Jan Nieuwenhuizen janneke-l...@xs4all.nl:
Drawing systems.../usr/local/share/lilypond/2.13.6/scm/font.scm:167:29:
In procedure string-replace in expression
Op dinsdag 20-10-2009 om 14:58 uur [tijdzone +0100], schreef Simon
Tatham:
Jan Nieuwenhuizen janneke-l...@xs4all.nl wrote:
I generate trivial Postscript describing
a lot of overlapping nib shapes moving round the curves, call
Ghostscript to render to a bitmap
Ah, I see.
Ghostscript is the
Hi,
I've recently drawn a new font of musical symbols for use with
Lilypond, which look more like the ones I'm used to and hence
distract me less. I put it up on the web this weekend at
http://www.chiark.greenend.org.uk/~sgtatham/gonville/
Currently the only way I've found to use that font
Op maandag 19-10-2009 om 08:15 uur [tijdzone +], schreef Simon Tatham:
Hi Simon,
I've recently drawn a new font of musical symbols for use with
Lilypond, which look more like the ones I'm used to and hence
distract me less. I put it up on the web this weekend at
Op maandag 19-10-2009 om 15:05 uur [tijdzone +0100], schreef Simon
Tatham:
(I hope this reply to the list works.
I think not, you'll have to subscribe.
I had to post my previous
message through the Gmane interface, but if I have to post this one
the same way, I won't be able to get the
Jan Nieuwenhuizen janneke-l...@xs4all.nl wrote:
Wow. You created a full font? That must have taken quite some time!
I think Feta took Han-Wen and me something between one and two
man-years of work.
This one has only taken me a couple of months (including some
initial thought about how to
Hi all,
Although I greatly prefer the Feta font to Gonville, I'm very much
enjoying this thread — kudos to Simon and Jan for all their hard and
considered work!
it doesn't seem surprising to me that one answer doesn't satisfy
everybody's tastes!
Agreed — this is one of the great(est)
Simon Tatham ana...@pobox.com writes:
I may yet make another attempt at redesigning the multiple flags.
The intention was to have them all essentially similar in shape
Why? What do you gain by smaller note values essentially making a
spread-out regular rectangular black pattern across the
Wow too.
Actually, there are things in Feta what I don't feel natural either.
For example: the caesura sign, the G-clef and the trill indication feels
better for me in Gonville.
Though the G-clef is I think a clear LilyPond watermark, so I would keep
that one :)
The best would be if I could
(I hope this reply to the list works. I had to post my previous
message through the Gmane interface, but if I have to post this one
the same way, I won't be able to get the In-Reply-To header to work
properly.)
Jan Nieuwenhuizen janneke-l...@xs4all.nl wrote:
Wow. You created a full font? That
On Mon, Oct 19, 2009 at 4:27 PM, Jan Nieuwenhuizen
janneke-l...@xs4all.nl wrote:
Op maandag 19-10-2009 om 15:05 uur [tijdzone +0100], schreef Simon
Tatham:
(I hope this reply to the list works.
I think not, you'll have to subscribe.
If this helps, I did receive Simon's earlier mail on the
Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon
Tatham:
Jan Nieuwenhuizen janneke-l...@xs4all.nl wrote:
This one has only taken me a couple of months (including some
initial thought about how to get nice-looking curves without an
excessive amount of manual specification).
it would be nicer if Lilypond itself could centre the digits
around the 2nd and 4th lines of the stave in the case
where they're smaller than 2*staff_spacing
Be sure to consider non-5-line staff situations.
Character glyph could be raised above the baseline using a seperate coding
point for
hi all,
please excuse my lousy english.
i would like to design a handwritten music font for lilypond based on the art
of music copying by clinton roemer.
would a modyfied feta-bolletjes.mf make sense to you to have a look at it?
regards,
johnny
--
Der GMX SmartSurfer hilft bis zu 70
customly-encoded feta music font. Here's a C snippet
canvas = GNOME_CANVAS (canvas_widget);
root = gnome_canvas_root (canvas);
int text_item = gnome_canvas_text_get_type ();
gnome_canvas_item_new (root, text_item, x, 45.0, y, 122.5,
font, lilypond-feta-nummer 16, text
94 matches
Mail list logo
