Lilypond-book: Auto-detect linewidth and exampleindent in texinfo mode

Lilypond-book: Auto-detect linewidth and exampleindent in texinfo mode

[dak, 2011-08-22 11:51:37]

http://codereview.appspot.com/4938044/diff/7001/python/book_texinfo.py
File python/book_texinfo.py (right):

http://codereview.appspot.com/4938044/diff/7001/python/book_texinfo.py#newcod...
python/book_texinfo.py:228: val = float (m.group (1))/72
This would be wrong.  TeX's principal unit, the pt or printer's point, is
1in/72.27.  You are confusing this with PostScript points, 1in/72, which TeX
calls bp (big points).

[Reinhold, 2011-08-22 12:30:15]

On 2011/08/22 11:51:37, dak wrote:
> python/book_texinfo.py:228: val = float (m.group (1))/72
> This would be wrong.  TeX's principal unit, the pt or printer's point, is
> 1in/72.27.  You are confusing this with PostScript points, 1in/72, which TeX
> calls bp (big points).

Ah, thanks, that explains a lot!
New patch uploaded.

Now, it's clear that lilypond produces .pdf files that are about 0.5-1 mm too
wide. So we now have the proper way to fix #1816

[Graham Percival (old account), 2011-08-22 23:55:52]

On 2011/08/22 12:30:15, Reinhold wrote:
> Now, it's clear that lilypond produces .pdf files that are about 0.5-1 mm too
> wide. So we now have the proper way to fix #1816

What does "0.5-1mm" mean?  Is it 0.5 for top/bottom, 1.0 for left/right?  Or
does it depend on some random factor?  (i.e. whether there's bar numbers or not)
?  Or does it depend on the paper size that latex is using ?  (i.e. does it
still work in a0 and a5 paper)

Thanks incredibly much for adding this functionality!

[Reinhold, 2011-08-23 11:38:10]

On 2011/08/22 23:55:52, Graham Percival wrote:
> On 2011/08/22 12:30:15, Reinhold wrote:
> > Now, it's clear that lilypond produces .pdf files that are about 0.5-1 mm
too
> > wide. So we now have the proper way to fix #1816
> 
> What does "0.5-1mm" mean?  Is it 0.5 for top/bottom, 1.0 for left/right?  Or
> does it depend on some random factor?  (i.e. whether there's bar numbers or
not)
> ?

I'm only talking about horizontal extents of the generated pdfs. The bar numbers
on the left are no problem, because we use "-deps-box-padding=3\\mm" to add an
additional 3 mm on the left for the bar number (and reduce the line-width by the
same amount).  
What I'm observing is that the pdf is always a bit larger (more than 0.5mm, but
usually less than 1mm) than the line-width plus the 3mm left padding. I have not
yet investigated in how far bar lines on the right end increase it. I suspect
that it has an influence.

> Or does it depend on the paper size that latex is using ?  (i.e. does it
> still work in a0 and a5 paper)

It should work independent of the paper size, since we only extract the
line-width from texinfo or latex and then simply handle that to lilypond as a
numeric value. LilyPond simply creates a score with this line-width and then
crops the image, leaving a small amount of extra space on the right, which I
think is the cause of this problem.

[Graham Percival, 2011-08-23 18:06:07]

On Tue, Aug 23, 2011 at 11:38:10AM +0000, reinhold.kainhofer@gmail.com wrote:
> On 2011/08/22 23:55:52, Graham Percival wrote:
> >On 2011/08/22 12:30:15, Reinhold wrote:
> >> Now, it's clear that lilypond produces .pdf files that are about
> 0.5-1 mm too
> >> wide. So we now have the proper way to fix #1816
> 
> >What does "0.5-1mm" mean?  Is it 0.5 for top/bottom, 1.0 for
> left/right?  Or
> >does it depend on some random factor?  (i.e. whether there's bar
> numbers or not)
> >?
> 
> I'm only talking about horizontal extents of the generated pdfs.

Oops, sorry.  Yes, that was obvious.  Brain fart on my part.

> What I'm observing is that the pdf is always a bit larger (more than
> 0.5mm, but usually less than 1mm) than the line-width plus the 3mm left
> padding. I have not yet investigated in how far bar lines on the right
> end increase it. I suspect that it has an influence.

ok.

> It should work independent of the paper size, since we only extract the
> line-width from texinfo or latex and then simply handle that to lilypond
> as a numeric value. LilyPond simply creates a score with this line-width
> and then crops the image, leaving a small amount of extra space on the
> right, which I think is the cause of this problem.

ok, sounds good.

Cheers,
- Graham

[Graham Percival (old account), 2011-08-26 03:12:46]

LGTM, please push.