Abraham Lee writes:
> On Fri, Aug 1, 2014 at 3:51 PM, Alexander Kobel wrote:
>>
>> factor is relevant if you set the global staff size to something
>> different than 20, the default. The usual rule-of-tree used to be
>> something like
>> myStaffSize = #17.82
>> #(set-global-staff-size mySta
Janek Warchoł wrote:
> So, we can say that \magnifyStaff sets staff "size" to an
> absolute value - defined as the fraction of the default
> size - and not "relative" to the previous size.
Not exactly. A magnifyStaff value is only relative to the
previous staff size the first time it's used in a
Patchset 4 LGTM :)
I agree that it would be nice to separate melisma stuff from ties, but -
as i've already written on the tracker - that's a topic for another
patch.
https://codereview.appspot.com/117050043/
___
lilypond-devel mailing list
lilypond-d
2014-08-02 9:05 GMT+02:00 Mark Polesky :
> Janek Warchoł wrote:
>> So, we can say that \magnifyStaff sets staff "size" to an
>> absolute value - defined as the fraction of the default
>> size - and not "relative" to the previous size.
>
> Not exactly. A magnifyStaff value is only relative to the
>
Mark Polesky writes:
> Janek Warchoł wrote:
>> So, we can say that \magnifyStaff sets staff "size" to an
>> absolute value - defined as the fraction of the default
>> size - and not "relative" to the previous size.
>
> Not exactly. A magnifyStaff value is only relative to the
> previous staff si
On 2014/08/01 19:31:40, dak wrote:
On 2014/08/01 19:30:45, dak wrote:
> It's a public function, so a convert-rule seems prudent to do.
Purely
internal
> functions are not exported.
Actually, it's probably easier to do an alias rather than a convert
rule.
Like this? Or is there some specia
On 08/02/2014 09:00 AM, David Kastrup wrote:
Abraham Lee writes:
On Fri, Aug 1, 2014 at 3:51 PM, Alexander Kobel wrote:
BTW, I never really understood whether it is technically possible to
automatically figure out "factor" at the point where
make-pango-font-tree is called? If not, why? An
Hello,
Here is the current patch countdown list. The next countdown will be on
August 5th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch
_
On Sat, Aug 2, 2014 at 4:46 AM, Alexander Kobel wrote:
On 08/02/2014 09:00 AM, David Kastrup wrote:
Well, looking at the definition of set-global-staff-size would seem
to
indicate how the size is being set. I suspect that calculating the
"relevant module" in that manner and then looking up ou
Hi Alexander,
2014-08-01 12:15 GMT+02:00 Alexander Kobel :
> Hi all,
>
> can anyone explain me why both numbers 11 and 12 (as in 11pt and 12pt)
> appear in the implementation of add-pango-fonts (scm/font.scm, lines 208,
> 219 and 224)?
I have no idea; this looks really strange. The difference wa
Abraham Lee writes:
> On Sat, Aug 2, 2014 at 4:46 AM, Alexander Kobel wrote:
>> On 08/02/2014 09:00 AM, David Kastrup wrote:
>>> Well, looking at the definition of set-global-staff-size would seem
>>> to
>>> indicate how the size is being set. I suspect that calculating the
>>> "relevant module
2014-08-01 12:04 GMT+02:00 :
> The user interface is simply an optional argument (default 1) in the
> font-spec-list. [...]
Ah, so it's up to the user to provide scaling factors. I thought that
there is some code measuring height of the x letter and scaling the
font accordingly :)
Ok, now i see
https://codereview.appspot.com/122750044/diff/20001/scm/output-lib.scm
File scm/output-lib.scm (right):
https://codereview.appspot.com/122750044/diff/20001/scm/output-lib.scm#newcode1114
scm/output-lib.scm:1114: (export grob::calc-property-by-copy)
You can just use define-public here. It is onl
Am 02.08.2014 11:35, schrieb Janek Warchoł:
Now with requests for absolute and relative versions, as
>well as this:
>
> \temporary \magnifyStaff 1.3
> ...
> \undo \magnifyStaff 1.3
>
>...I'm starting to wonder how much of this is really
>necessary. Can anyone provide an actual use case to
Reviewers: ,
Message:
This is the current state of Abraham's approach to make music fonts
switchable. The patch is incomplete in a few senses, but Abraham wants
an official review for that current state:
- there's no documentation
-> We'll take care of that once the user interface
has bee
On Sat, Aug 2, 2014 at 10:40 AM, lilyli...@googlemail.com wrote:
Reviewers: ,
Message:
This is the current state of Abraham's approach to make music fonts
switchable. The patch is incomplete in a few senses, but Abraham wants
an official review for that current state:
- there's no documentation
Attempting to push a single patch, using the directions in CG 3.4.11, I
get the console output appended. I haven't attempted anything since, and
would be grateful for guidance from the gurus. Online research suggests
either permission errors on the savannah repo, space issues at savannah,
or co
Hi,
2014-08-02 20:32 GMT+02:00 Colin Campbell :
> Attempting to push a single patch, using the directions in CG 3.4.11, I get
> the console output appended. I haven't attempted anything since, and would
> be grateful for guidance from the gurus. Online research suggests either
> permission errors
On 2014/08/02 18:32:41, janek wrote:
use simpler syntax
Looks good. Looking at the name grob::copy-property-from-event, I think
that grob::property-from-event is shorter but probably equally
descriptive. Though perhaps we have a number of others starting with
copy- already.
Your call.
https
LGTM
https://codereview.appspot.com/46060045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2014/08/02 18:56:19, Keith wrote:
LGTM
Cannot find the corresponding Google Code issue.
https://codereview.appspot.com/46060045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2014/08/02 19:26:11, dak wrote:
On 2014/08/02 18:56:19, Keith wrote:
> LGTM
Cannot find the corresponding Google Code issue.
http://code.google.com/p/lilypond/issues/detail?id=3646
https://codereview.appspot.com/46060045/
___
lilypond-devel ma
- Original Message -
From: "Keith E OHara"
To:
Cc: "Phil Holmes"
Sent: Saturday, August 02, 2014 9:44 PM
Subject: updated doc snippets on LSR
Two snippets used a function make-simple-closure.
No-one understands the purpose of that function anymore, so we stopped
recommending it in
Two snippets used a function make-simple-closure.
No-one understands the purpose of that function anymore, so we stopped
recommending it in the docs with issue 3993.
I re-entered these two snippets in form that avoids make-simple closure
http://lsr.di.unimi.it/LSR/Item?id=948
http://lsr.di.uni
Am 03.08.2014 00:26, schrieb Abraham Lee:
On Sat, Aug 2, 2014 at 1:46 PM, Urs Liska wrote:
Hi Abraham, as fonts.openlilylib.org is "Under construction" you
should provide a download link for the fonts (or at least one plus
Gonville (for the braces), so others can actually test the patch.
Please
On 14-08-02 12:41 PM, Janek Warchoł wrote:
Hi,
2014-08-02 20:32 GMT+02:00 Colin Campbell :
Attempting to push a single patch, using the directions in CG 3.4.11, I get
the console output appended. I haven't attempted anything since, and would
be grateful for guidance from the gurus. Online resea
On 14-08-02 05:26 PM, Colin Campbell wrote:
Thanks for the try, Janek! It's still happening, after a git pull -r .
Gitk shows one commit difference. Git fsck ran with no errors reported.
Still baffled,
Colin
Less baffled now: the problem was in my local ~/lilypond-git/.git/config
file, wh
27 matches
Mail list logo
