Re: binding-offset bug

[James]

On 20/07/14 12:13, Karol Majewski wrote:
>> It seems to me (from my limited playing about with 2.19.8) that if you
>> comment out either/or 'two-sided' or 'binding-offset' then the problem
>> 'goes away'. So is this a 'binding-offset' issue or a 'two-sided' issue?
> James, note that binding-offset doesn't work at all when two-sided is 
> disabled. This is from documentation:
>
> binding-offset - The amount inner-margin is increased to make sure nothing 
> will be hidden by the binding. If the paper size is modified, this 
> dimension’s default value is scaled accordingly. Works only with 
> two-sided set to true.
>
> Karol
>
>
Thanks - off course that makes sense - although one can still bind
single page documents, so technically a 'binding offset' could be valid
nomenclature if not really the purpose of the function in LilyPond.

However I don't think it is clear if it is the binding offset function
that is causing the problem or the two-sided function (bear in mind I am
not a LP programmer) but merely pointing out that we have _two_
variables here and without one of them (even if that is invalid) the
problem goes away, so the two are interdependent (no?) which was what I
was getting at really.

Anyway, the tracker is created with your example; so I am sure for those
devs, that know how this all works, this will be enough to see
what/where the issue could be.

James