Re: Missing image in web & docs
2010/10/8 Graham Percival : > On Fri, Oct 08, 2010 at 10:07:00AM +0200, Francisco Vila wrote: >> 2010/10/7 Graham Percival : >> >> > 2) texinfo finds the .eps, converts it into the appropriate output >> > format, but puts it in the wrong directory. >> >> It's not being converted to any other than PDF. > > Ok. So what's wrong with > Documentation/pictures/GNUmakefile > ? I see an: > OUT_BITMAP_IMAGES += $(EPS_ILLUSTRATIONS:%.pdf=$(outdir)/%.png) > > Is that rule not getting triggered? Is it getting triggered, but > failing for some reason, and that failure isn't stopping the > build? etc. It should be OUT_BITMAP_IMAGES += $(EPS_ILLUSTRATIONS:%.eps=$(outdir)/%.png) instead. I'll push a patch as soon as I'd verified that the resulting output is right. Thank you for the hints -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Missing image in web & docs
On Fri, Oct 08, 2010 at 10:07:00AM +0200, Francisco Vila wrote: > 2010/10/7 Graham Percival : > > > 2) texinfo finds the .eps, converts it into the appropriate output > > format, but puts it in the wrong directory. > > It's not being converted to any other than PDF. Ok. So what's wrong with Documentation/pictures/GNUmakefile ? I see an: OUT_BITMAP_IMAGES += $(EPS_ILLUSTRATIONS:%.pdf=$(outdir)/%.png) Is that rule not getting triggered? Is it getting triggered, but failing for some reason, and that failure isn't stopping the build? etc. That's the next place to look. :) (hint: I would start with a clean build dir, then cd Documentation/pictures && make out=www web &> build.log then examing build.log) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
NR 2.1 Vocal music
Graham
I've just pushed a patch to NR 2.1 Vocal music which provides a
first draft for the last of the blank sections marked TBC ("To Be
Completed"). I believe it's now in a much better shape than it was,
even though much of the chapter is in "first draft" state.
Next up are the 19 TODOs, and I'd like to work through them before
inviting a review of the whole chapter, although if you or anyone
else wishes to comment on the work so far I'd be happy with that
too.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: names of vertical spacing dimensions
Mark Polesky writes: > (Carl et al.: please read at least the last paragraph!) > > Xavier Scheuer wrote: >> The previous names were quite easy to understand (although >> it was a bit difficult due to the large number of such >> variables) but I don't catch at first sight the meaning of >> the new proposed ones... > > Well, in the new docs I would certainly mention the general > format: > > item1-item2-spacing > > I would also mention that the use of the word "markup" in > these variable names only refers to top-level markups and > titles. > > Would knowing this in advance make you feel differently or > do you still not like the proposed names? They sound systematic enough to obliterate them. Namely use an interface like spacing markup markup = 3cm spacing score markup = ... In other words: I like the systematics better than the resulting identifiers. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: names of vertical spacing dimensions
(Carl et al.: please read at least the last paragraph!) Xavier Scheuer wrote: > The previous names were quite easy to understand (although > it was a bit difficult due to the large number of such > variables) but I don't catch at first sight the meaning of > the new proposed ones... Well, in the new docs I would certainly mention the general format: item1-item2-spacing I would also mention that the use of the word "markup" in these variable names only refers to top-level markups and titles. Would knowing this in advance make you feel differently or do you still not like the proposed names? In the first post of this thread, I explained my own confusion with things like "after-title-spacing", which I would expect to control the spacing after titles. But this is doubly misleading. It does not control the spacing after titles that are followed by markups or other titles, yet it *does* control the spacing after some markups that are *not* titles. In contrast to this confusion, the variable always controls the spacing between a markup and a score*, whether the markup is a title or a top-level markup. Thus the name "markup-score-spacing" is both more informative and less misleading. *um, see the last paragraph... And even if you don't use top-level markups yourself, the spacing variable is designed to work with them, and the variable name should reflect this as clearly as possible. And that's just one example. There are plenty of other confusing things in the current list. Other examples: "top-system-spacing" controls the spacing *above* the top system, yet "bottom-system-spacing" controls the spacing *below* the bottom system. "before-title-spacing" does not control the spacing before titles at the top, nor does it control the spacing before titles preceded by a top-level markup. I (and several others) feel that a consistent format is preferable for future users, and worth the hassle for us current users. Okay, now I see something possibly sub-optimal. By changing "after-title-spacing" to "markup-score-spacing", it could confuse users due to the fact that the title is presumably *part* of the score, no? So if the title is technically considered part of the score, than this is not the distance between markup and score, but rather between markup and system (which reverts to my original proposal of "markup-system-spacing"). So now I prefer "after-title-spacing"-->"markup-system-spacing" and "before-title-spacing"-->"score-markup-spacing". Carl, what do you think? - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: names of vertical spacing dimensions
On 8 October 2010 09:14, Mark Polesky wrote: > > [...] > > This leaves: > > CURRENT NAME PROPOSED NAME > - > top-system top-system (no change) > top-title top-markup > between-title markup-markup > after-title markup-score > between-system system-system > before-title score-markup > bottom-system system-bottom > between-scores-system score-score I'm sorry to come come a day after the fair, but I truly dislike the new proposed names. What was wrong with the previous ones? I find all these "markup-something" or "something-markup" names very confusing. We have markups everywhere : we use the \markup command for TextScripts, which are _inside_ the score, we can use \mark \markup ... or even \tempo \markup ... We can even have \score blocks inside a \markup . These vertical system variables are usually somewhat related to "titles" (due to a \header block), even if sometimes it is not really a "header title", but simply a markup. But even in this case this markup usually play in a certain way as a title. The previous names were quite easy to understand (although it was a bit difficult due to the large number of such variables) but I don't catch at first sight the meaning of the new proposed ones... Cheers, Xavier -- Xavier Scheuer ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Missing image in web & docs
2010/10/7 Graham Percival : > IMO, there's three steps that could be failing: > 1) texinfo can't find the .eps image. IIRC the build stops if > this happens, but my memory could be faulty. Original image is ./Documentation/pictures/context-example.eps Several PDFs are being generated from this EPS. ./out-website/website/pictures/context-example.pdf ./out-www/offline-root/Documentation/pictures/context-example.pdf ./Documentation/pictures/out-www/context-example.pdf > 2) texinfo finds the .eps, converts it into the appropriate output > format, but puts it in the wrong directory. It's not being converted to any other than PDF. > 3) our mirroring tool (the python thing that copies from > Documentation/out-www/ to out-www/ ) doesn't copy that filetype, > or copies it but puts it in the wrong directory. the PNG is not being generated; the PDF is being used into the PDF docs and it's viewable there. Learning 3.3.1 I will give it more time. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: names of vertical spacing dimensions
Carl Sorensen wrote: > Does before-title-spacing apply at the top of the first > page, or only between scores? "before-title-spacing" does *not* apply at the top of the first page, even when print-first-page-number is #t (to force a header). > Does between-scores-system-spacing apply only to the case > where there are two scores without a markup between? AFAICT, yes. > Do we consider a header as part of a score or not? AFAICT, no. > If we don't consider the markup to be part of a score, I > like the term score-score-spacing. To me it says it > controls the spacing between the last system of the first > score and the first system of the next score. If that > meaning is right, let's keep the name. If that meaning is > wrong, let's change the name. I believe that the meaning is correct, so your vote is to keep "score-score-spacing"; that's fine by me. > Also, if system-markup-spacing only applies to the > distance between the last system of the first score and a > markup that comes after the score, then it should be > score-markup-spacing, IMO. If it applies to the spacing > between a system *in a score* and a markup *in the same > score*, then it should be system-markup-spacing. "system-markup-spacing" (a.k.a "before-title-spacing") does not apply to a system and markup in the same score, so your vote is for "score-markup-spacing"; that's fine by me. However, by extension of this logic, and to be consistent, we should then change "after-title-spacing" to "markup-score-spacing", as opposed to "markup-system-spacing". This leaves: CURRENT NAME PROPOSED NAME - top-system top-system (no change) top-title top-markup between-title markup-markup after-titlemarkup-score between-system system-system before-title score-markup bottom-system system-bottom between-scores-system score-score I'm fine with these changes, but now I'm confused by something else. After playing around with a bunch of settings, it seems that headers and footers are neither markups nor scores, yet they influence spacing, and there are no variables like "after-header-spacing" or "before-footer-spacing". What variable can I use to set the 'padding between the last system and the footer? Or do I just use bottom-system-spacing, and then the program automatically moves the last system up to prevent colliding with the footer? By the way, the annotate-spacing output is not very helpful here. No, that's too kind; annotate-spacing is so unhelpful it's essentially broken. When I have more time, maybe I'll submit a bug report. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
