>> The 2 situations, tune and page, have to be kept separate somehow, >> it seems to me, they're on different levels. > Yes. A newpage directive is only useful for applications that can > deal with entire tunebooks, such as abcm2ps and potentially lilypond.
And BarFly, though you probably wouldn't want to. > Application that operate on the level of individual tunes, can > better ignore it. And what if a tune is more than a page long? BarFly's model is horrendous for this - it treats each score as a galley proof and slices it up with a virtual guillotine, so you often end up with odd notes on the wrong page. I believe there are workarounds for this, but they're far too complicated for me to want to deal with. A newpage command that told the program that all the music before it went on one page and all after it on the next would sort this. ----------------------------------------------------------------------------- Jack Campin: 11 Third Street, Newtongrange, Midlothian EH22 4PU; 0131 6604760 <http://www.purr.demon.co.uk/jack> * food intolerance data & recipes, Mac logic fonts, Scots traditional music files, and my CD-ROM "Embro, Embro". ------> off-list mail to "j-c" rather than "abc" at this site, please <------ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
