On Fri, Jan 1, 2010 at 9:18 PM, Carl Sorensen 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 approval for
>
On 1/1/10 4:08 PM, "Han-Wen Nienhuys" wrote:
> On Fri, Jan 1, 2010 at 2:21 PM, Marc Hohl 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 used th
On Fri, Jan 1, 2010 at 2:21 PM, Marc Hohl 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 used the same example and created a sample page.
> It is available as a 1
Carl Sorensen schrieb:
On 1/1/10 2:52 AM, "Marc Hohl" 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 poin
On 1/1/10 2:52 AM, "Marc Hohl" 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. I
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 draw
On 12/31/09 7:45 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 12/31/09 6:37 AM, "Marc Hohl" wrote:
>>
>>
>>> Carl Sorensen schrieb:
>>>
On 12/30/09 7:42 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>
>
OK, I've at
Carl Sorensen schrieb:
On 12/31/09 6:37 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
On 12/30/09 7:42 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
OK, I've attached a 300 dpi png and with the clef rotated from 0 to 4
degrees.
Thanks for your work
On 12/31/09 6:37 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 12/30/09 7:42 AM, "Marc Hohl" wrote:
>>
>>
>>> Carl Sorensen schrieb:
>>>
>>
>> OK, I've attached a 300 dpi png and with the clef rotated from 0 to 4
>> degrees.
>>
> Thanks for your work, Carl.
>> An Inkscap
Carl Sorensen schrieb:
On 12/30/09 7:42 AM, "Marc Hohl" wrote:
Carl Sorensen schrieb:
On 12/30/09 6:06 AM, "Marc Hohl" 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?
Carl Sorensen schrieb:
On 12/30/09 6:06 AM, "Marc Hohl" 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
ge
On 12/30/09 6:06 AM, "Marc Hohl" 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 output instea
Francisco Vila schrieb:
2009/12/29 Marc Hohl :
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 loo
On 12/29/09 1:54 PM, "Marc Hohl" 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
2009/12/29 Marc Hohl :
> 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?
At a ris
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 wh
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 o
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 de
Le mercredi 23 décembre 2009 à 09:41 -0700, Carl Sorensen a écrit :
> Having reviewed all four of the clefs, I think I like 3 the best, but I have
> a hard time deciding between 3 and 4. Either of them seems fine to me.
Looking at two-by-two comparisons of cropped graphics sent on the list,
I agr
On 12/23/09 12:41 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 12/22/09 12:45 AM, "Marc Hohl" wrote:
>>
>>
>>> Carl Sorensen schrieb:
>>>
On 12/21/09 1:52 PM, "Marc Hohl" wrote:
> [...]
>
>
>> I like it much better.
Le mercredi 23 décembre 2009 à 08:41 +0100, Marc Hohl a écrit :
> 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" an
David Kastrup schrieb:
Marc Hohl 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
Marc Hohl 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 two.
On 12/22/09 12:45 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 12/21/09 1:52 PM, "Marc Hohl" 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.
On 12/21/09 1:52 PM, "Marc Hohl" 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 differen
On 12/21/09 3:08 AM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>> Jan Nieuwenhuizen 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 o
On Mon, Dec 21, 2009 at 8:08 AM, Marc Hohl 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. G
Marc Hohl wrote Monday, December 21, 2009 10:08 AM
Carl Sorensen schrieb:
Jan Nieuwenhuizen 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 issue
Carl Sorensen schrieb:
Jan Nieuwenhuizen 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
centre line of
On Sat, Nov 28, 2009 at 2:27 PM, Carl Sorensen 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 backward
On 2009-11-01, Neil Puttock wrote:
> 2009/11/1 Patrick McCarty :
> > 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;
> su
2009/11/1 Patrick McCarty :
> 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?
Regards,
Neil
On 2009-11-01, Neil Puttock wrote:
> 2009/10/29 Patrick McCarty :
>
> > 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.
>
> Are you sure about the extra font-defaults setting?
2009/10/29 Patrick McCarty :
> 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 braces at large po
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 :
> > > > 2009/10/20 Patrick McCarty :
> > > >
> > > >> This should be fixed now in latest git.
> > > >
> > > > Works for me.
> > >
> > > I guess I spo
On 2009-10-28, Patrick McCarty wrote:
> On 2009-10-28, Neil Puttock wrote:
> > 2009/10/20 Neil Puttock :
> > > 2009/10/20 Patrick McCarty :
> > >
> > >> This should be fixed now in latest git.
> > >
> > > Works for me.
> >
> > I guess I spoke a bit prematurely here, since the fix you pushed
> > al
On 2009-10-28, Neil Puttock wrote:
> 2009/10/20 Neil Puttock :
> > 2009/10/20 Patrick McCarty :
> >
> >> 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 redef
2009/10/20 Neil Puttock :
> 2009/10/20 Patrick McCarty :
>
>> 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 amending the code to allow switching
On Mon, Oct 19, 2009 at 5:36 PM, Bertalan Fodor (LilyPondTool)
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 I think a clear Lil
Op dinsdag 20-10-2009 om 14:58 uur [tijdzone +0100], schreef Simon
Tatham:
> Jan Nieuwenhuizen 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 major consumer of
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 :
> > Drawing systems.../usr/local/share/lilypond/2.13.6/scm/font.scm:167:29:
> > In procedure string-replace in expression (string-replace
> > "emm
2009/10/20 Patrick McCarty :
> 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., \override
Staff.Clef #
On 2009-10-20, Francisco Vila wrote:
> 2009/10/20 Jan Nieuwenhuizen :
> > 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?
>
>
2009/10/20 Jan Nieuwenhuizen :
> 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 systems.../usr/local/share/lilypond/2.13.6/scm/fo
Jan Nieuwenhuizen 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! The half hour 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 wrote:
> >
> > All I'd suggest is trivial changes to Lilypond to make it easy to
> > use an alternative fon
> 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
poi
Op maandag 19-10-2009 om 15:33 uur [tijdzone +0100], schreef Simon
Tatham:
Jan Nieuwenhuizen 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).
Great. Are you willi
On Mon, Oct 19, 2009 at 4:27 PM, Jan Nieuwenhuizen
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 list.
(Perhaps he's
(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 wrote:
> Wow. You created a full font? That must have taken quite
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 set
Simon Tatham 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 page rather than
b
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) be
Jan Nieuwenhuizen 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 get nice-looking curve
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 I
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
>
> http://www.chiark.g
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 wit
57 matches
Mail list logo
