On Tue, Aug 20, 2013 at 5:49 PM, Ted Walther <tederi...@gmail.com> wrote:
> Another problem with that snippet is the amount to drop. With a good > centering command, it is centered. But if I alter the font size, etc, the > amount of raising and dropping needed to center the lyrics will alter. How > can I predict that without a lot of kludgy code? Again, I'm generating > lilypond code from templates. I can compensate for some complexity, but > the simpler the better. > > Ted > > > On 20 August 2013 14:47, Ted Walther <tederi...@gmail.com> wrote: > >> Thank you Carl. Interesting example. For the hymns I do, that might >> work for the first couple bars, but then I'll have to predict where the >> linebreak will be and revert it at that point. I'm using a template system >> to auto-generate the lilypond code, so having to insert a counter-acting >> command at an unpredictable spot in the lyrics will be rather annoying. >> >> Are there any Lilypond developers still active on the list who might be >> interested in doing a sponsored modification that would allow two staves to >> be pasted together within a score. Alternatively, allowing two scores to >> be pasted together on the same line, since scores already follow one >> another sequentially inside a book? >> >> Ted >> > I am also using a template system. Right now, the system is composed of nested include files (one for the lyrics, one for the music, another to put the two together in combination, another to apply a layout, etc.), but eventually it will be database-driven, with an outside script generating the LP code to run. The idea is to allow end users to mix and match compatible texts and tunes. Since the template system is explicitly designed for output to multiple formats (print and screen) AND because I am endeavoring to keep phrases intact on a line (which is absolutely critical for usability on slides), I do not leave line breaks to chance. I have explicit line breaks in all my scores. This is why your issue isn't a factor for me, since a chorus/refrain theoretically should always begin a new phrase (and thus, can be shunted to a new line). Carl
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
