lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fix clef transposition alignment (issue 3186) (issue 8363044)


From: Janek Warchoł
Subject: Re: Fix clef transposition alignment (issue 3186) (issue 8363044)
Date: Mon, 18 Aug 2014 08:58:11 +0200

2014-08-17 15:14 GMT+02:00  <address@hidden>:
> Why would you want to access anything from C++?

You mean i should have written this whole code in Scheme rather than
C++?  Maybe.  I'm still more familiar with C++, that's why i chose it,
but i can rewrite it if you think i should.

> Lots of callbacks are
> written in Scheme, and it's not like you cannot also access Scheme
> variables, like with ly_lily_module_constant.  At any rate, we are
> talking about character dimensions here that are font-dependent.  So
> this effort should really be coordinated with the efforts of the people
> switching various music fonts around, and then a decision has to be made
> how the respective information regarding attachment points/slant can be
> connected with various fonts.

Hmm.  Indeed, i was so preoccupied with getting a 2-year-old patch
finally done that i forgot about work on new music fonts...
Anyway, as far as i can see the new music fonts are supposed to come
with a set of "style overrides", which adapt thickness of lines and
other stuff to match a particular font.  So, people adding support for
new fonts can simply add an override to clef-alignments there - this
may be not perfect, but at least is straightforward.

> Apart from the font specificity of the displacement (which likely
> warrants coordination with the people working on multiple font support),
> scm/parser-clef.scm uses global variables to store various clef
> characteristics.

Hmm.  Maybe that would be a better place, but then it would be less
simple to change by the user.

cheers,
Janek



reply via email to

[Prev in Thread] Current Thread [Next in Thread]