That's what I thought. I just wanted to make sure that that's what was really the issue that needed to be addressed.
Regards, Abraham Sent from my iPhone > On Sep 28, 2014, at 9:34 PM, Chris Crossen <elaparic...@gmail.com> wrote: > > > >> On Sep 28, 2014, at 8:08 PM, Abraham Lee <tisimst.lilyp...@gmail.com> wrote: >> >> Paul, >> >> This sounds intriguing! First of all, my best wishes to you and your startup >> company. May you have great success! >> >> Secondly, I'm not entirely sure I understand what you are trying to avoid >> with the text above measure bars. Can you give us an example or two showing >> us exactly what you mean? I think that will help us know who can help you. >> >> Regards, >> Abraham >> >> Sent from my iPhone >> >>> On Sep 28, 2014, at 9:00 PM, Paul Tannous <ptann...@hotmail.com> wrote: >>> >>> LilyPonders: >>> >>> We are part of a startup company that wants to put LilyPond-generated >>> musical scores on tablets. We believe this will allow users to have >>> beautiful, readable scores on tablets and spread the usage of LilyPond to a >>> wider audience. We have completed the first version of an Android >>> application that does this. It dynamically repaginates the music score to >>> fill the tablet screen, and it supports written annotation. >>> >>> We have a series of programs that run on a Mac or PC to generate the scores >>> to be rendered on tablets of different screen sizes. A tablet-format score >>> of our own design is built from LilyPond-generated score images so a tablet >>> page of any size or orientation can be built dynamically, using note sizes >>> that will be readable. If you’ve seen PDF scores reduced and displayed on >>> tablets, you’ll understand why we think we have a better approach. >>> >>> Creating our tablet-format scores to support dynamic repagination means we >>> have to take steps to avoid having text directly above and below each of >>> the measure bars. We add measure bars back when rendering each line and >>> vary the bar widths in addition to adding space to fill out the lines. So >>> any text (tempo, dynamics, pedal instructions, etc.) spanning measures >>> would be split, pixels lost, and unwanted spacing added. We avoid this now >>> by writing the LilyPond source to avoid text above or below the measure >>> bars. However, this can be painstaking and time-consuming work. >>> >>> We would therefore like to see an option added to LilyPond, that could be >>> set before processing, that would avoid placing text above or below measure >>> bars. >>> >>> We believe there must be code already in the engravers to avoid splitting >>> text over measures at line ends. So, we are hoping our proposed enhancement >>> would be an extension of that code. >>> >>> We would be willing to pay a bounty to have this feature added if no one >>> else is interested in this functionality, but we have no idea of how much >>> effort would be required. We would like to have some feedback on how long >>> this would take and what someone who could do it would charge for the >>> effort. >>> >>> >>> >>> _______________________________________________ >>> lilypond-user mailing list >>> lilypond-user@gnu.org >>> https://lists.gnu.org/mailman/listinfo/lilypond-user > <1000px-Chopin_Prelude_7.svg.png> > My understanding of the problem can be demonstrated in the attached graphic. > The tempo Andantino above the first two measures would be a problem. The > dynamic pp under the treble clef of the last measure is also possibly > problematic. > > > >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
