Updates:
Status: Verified
Comment #34 on issue 1752 by brownian.box: redesigning G clef in our Feta
font
http://code.google.com/p/lilypond/issues/detail?id=1752
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Status: Fixed
Owner: janek.li...@gmail.com
Labels: -Patch-review
Comment #32 on issue 1752 by janek.li...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
pushed as e795110331497fbf46a7d61ed6ed73a9da4ae9c5
Updates:
Labels: -Patch-review Patch-needs_work
Comment #30 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
2011/7/26 Trevor Daniels t.dani...@treda.co.uk
The G clef font was changed 18 months or so
Updates:
Labels: -Patch-needs_work Patch-review
Comment #31 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I've looked on bug- archives and i see that i've missed a lot of
discussion! About 10
On Mon, Jul 25, 2011 at 04:36:47PM -0600, Carl Sorensen wrote:
On 7/24/11 5:43 PM, lilyp...@googlecode.com lilyp...@googlecode.com
wrote:
(obviously) I don't like this solution because it makes my work lie on a
shelf for a few months and do nothing but collect dust.
This proposal was
On 26 July 2011 21:33, Graham Percival gra...@percival-music.ca wrote:
I think this is the best solution as well. It might be nice to
add a bit more documentation about how somebody who really
disliked the new font could go about replacing it, but we've never
viewed documentation as holding
On Tue, Jul 26, 2011 at 09:47:10PM +0100, Neil Puttock wrote:
Since my suggestion appears to have passed most people by (probably my
own fault for its obscurity :), I'll reiterate: why not add support
for switching to the old-style clef via the \clef command?
IMO this mixes musical meaning
Comment #27 on issue 1752 by k-ohara5...@oco.net: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
How do you like it?
I would never notice the difference between the old and new glyphs.
Adding \override Staff.Clef #'style = xx complicates
Comment #28 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
2011/7/25 k-ohara5...@oco.net:
I would never notice the difference between the old and new glyphs.
:-)
Adding \override Staff.Clef #'style =
On Sun, Jul 24, 2011 at 11:43:02PM +, lilyp...@googlecode.com wrote:
However, I am aghast that the font switching architecture is going
nowhere. As far as I understand it,
1. we can switch to a different OTF font. (aka gonville)
Everything that i see on this topic is here
On 7/24/11 2:19 PM, lilyp...@googlecode.com lilyp...@googlecode.com
wrote:
Comment #25 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
The critical regression thing was a complete brain fart from me and
On 7/24/11 5:43 PM, lilyp...@googlecode.com lilyp...@googlecode.com
wrote:
Comment #26 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
In order to address the difference of opinion, we have two
Comment #29 on issue 1752 by k-ohara5...@oco.net: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Today, if I wanted to, I could \set Staff.clefGlyph =
#clefs.petrucci.g
However, i was unable to apply this override to a change clef - how it's
Comment #25 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
The critical regression thing was a complete brain fart from me and
should be scornfully ignored. I also now agree that the idea of an
\override
Comment #26 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
2011/7/24 n.puttock:
if we must have the option of switching between old new, I
think a parser-clef.scm entry would make more sense.
I'm not
Updates:
Labels: -Patch-needs_work Patch-review
Comment #22 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
clef selection for non-G clefs if 'old style is set is fixed now.
Comment #23 on issue 1752 by carl.d.s...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
It seems to me that we do not have agreement for having an override for the
clef. As far as I can see, there are those who prefer the old clef,
1752 in lilypond: redesigning G clef in our Feta font
Comment #23 on issue 1752 by carl.d.s...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I am *not* in favor of including the clef style override in lilypond --
it's a hack
Comment #24 on issue 1752 by n.putt...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I am *not* in favor of including the clef style override in lilypond --
it's a hack
that is not extensible and not maintainable in the long term.
Carl wrote
I am *not* in favor of including the clef style override in
lilypond -- it's a hack that is not extensible and not
maintainable in the long term.
Neither is Han-Wen. See comment 17:
I vote against overrides; we have too many of them, and the
difference between the old and new
Comment #20 on issue 1752 by x.sche...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
For what it counts, I still do not see the need to change the current
treble clef. But IMHO your last proposal is far more acceptable than
your first
Updates:
Labels: -Patch-review Patch-needs_work
Comment #21 on issue 1752 by n.putt...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Patch set 3 needs more work: clef selection is broken for all clefs apart
from treble if
Comment #19 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Han-Wen: I think that we should make old glyph available nevertheless
(besides, i cannot do this to James for all the feedback i had from him).
Comment #17 on issue 1752 by hanw...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Hi guys,
as the original designer of the G-clef, I applaud Janek's work, and don't
see any reason why we can or should not improve the shape of the
Comment #18 on issue 1752 by pkx1...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
'improve'? I don't think it is an improvement at all. It's worse.
Does mine (and the other's who also preferred the original) opinion not
count?
If
Comment #17 on issue 1752 by hanw...@gmail.com: redesigning G clef
in our Feta font
I vote against overrides; we have too many of them, and the
difference between the old and new glyph doesnt warrrant another
option.
I agree. LilyPond has many glyphs. If we start using
overrides to
On Wed, Jul 13, 2011 at 05:17:11PM +0100, Trevor Daniels wrote:
I vote against overrides; we have too many of them, and the
difference between the old and new glyph doesnt warrrant another
option.
I agree. LilyPond has many glyphs. If we start using
overrides to select glyphs with
Graham Percival wrote Wednesday, July 13, 2011 6:06 PM
Or, if there's serious oppositition to keeping this font in
lilypond itself, then at least provide the mechanism to change
fonts, and then James+company can add his own metafont font (the
bits from 2.14.0) from some separate archive site.
Updates:
Labels: font
Comment #15 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
2011/7/11 lilyp...@googlecode.com:
Comment #13 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta
Comment #16 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Yes, an \override would be fine for selecting the old font from a user
perspective. I can't comment on whether that's the best technical
solution,
Comment #6 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I agree with James -- why the change?
I'd like to see an alternate method of working here. Janek, could you work
on a framework to easily switch
Comment #7 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
New version of the clef (slightly higher).
Attachments:
clef-demo current Lily.pdf 26.1 KB
clef-demo new proposal.pdf 25.2 KB
Comment #9 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
2011/7/10 lilyp...@googlecode.com:
Comment #5 on issue 1752 by pkx166h: redesigning G clef in our Feta font
Comment #8 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I'm changing it because it doesn't look good. There is enough
not-goodness that it warrants the change in my opinon.
The notehead seems to be a bit
Comment #10 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I'm not sure if my replies to previous comments were properly sent... If
you didn't get them, check issue webpage.
2011/7/11
Comment #11 on issue 1752 by bordage@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
The last version is much better! It is perfectly balanced.
I think we should use this by default, since tis closer to traditional
clefs than the
Comment #13 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Unless absolutely every single person prefers the new clef, I have serious
concerns about changing it. This sounds like a Critical regression to me.
Comment #14 on issue 1752 by percival.music.ca: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
wait, let me rephrase that: it wouldn't be a Critical regression because it
would be a deliberate change.
However, I think it could still be a bad
Comment #3 on issue 1752 by mts...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I'll give you my first impression, which is entirely raw and
un-over-intellectualized.
I like the height of the new clef, but it seems too stout given
Comment #4 on issue 1752 by bordage@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I like the new height, but the top loop is too bent to the right.
In the file attached, you can see A, B and C aren't aligned, contrary to
the
Comment #5 on issue 1752 by pkx1...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Hello,
I'd just like to raise a hand here and ask
Why are we doing this again?
To me this is a pretty fundamental change in the look of the Feta Font,
Comment #1 on issue 1752 by carl.d.s...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I like the new clef better.
Can we see the Cue Clef as well?
Thanks,
Carl
___
bug-lilypond mailing
Comment #2 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
Thanks, Carl!
I attach a snippet with cue clefs and some scores from Mutopia.
cheers,
Janek
Attachments:
cue_and_change_clefs current
Status: Started
Owner: lemniska...@gmail.com
Labels: Type-Enhancement Priority-Medium Patch-review
New issue 1752 by lemniska...@gmail.com: redesigning G clef in our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
changing shape of the G clef
makes upper loop smaller,
bottom
44 matches
Mail list logo
