On Monday 04 June 2007 06:39, Heikki Johannes Junes wrote: > I have also thought long for changing default LilyPond export format to > PDF, since PDF renderers are more stable.
Are they? I haven't noticed that myself, but if you two have, such a change would be fine with me. > > is) no longer provides a status dialog to inform me that it's doing > > something. There is simply a pregnant pause, and then the preview comes > > up in KGhostView. Maybe I'm missing some helper app Xdialog? You may remember the helper scripts are inconsistent -- the Lilypond one uses Xdialog, the project packager uses kdialog. I'd rather use kdialog for both, but ISTR the particular progress reporting mechanism in Xdialog was rather handy, and not quite trivial to replace with kdialog's DCOP-based mechanism. If Xdialog isn't available, it doesn't complain, it just doesn't show progress. That is intentional (if not necessarily wise). > > Rosegarden's direct preview-to-print system. [...] Everything would come > > out with a whole note, plus whatever stems and flags. Printing via .PDF > > solved that problem back then too. [...] > > The mapping of the font files may change between LilyPond versions Rosegarden includes its own versions of the font files, it doesn't rely on a particular Lilypond version for its own display and native printing. In fact, it doesn't actually use fonts for note heads in native-printed PostScript at all -- it rasterises them during export. That's one reason printing is so slow (and, perhaps, one reason the results are so lousy). It does that to work around a particular issue for on-screen display -- the fact that it happens for printing as well is a historical accident (the print code _is_ the on-screen display code, just bigger and with a different target device). I think we've mentioned this before, but I do think that now would be a good time to switch to using Lilypond for the "native" printing implementation. That is, make both "Print..." and "Print Preview..." go through Lilypond, and then perhaps add a draft-print function (or option on the print dialog) to allow you to use native printing if you really want to. Or, alternatively, remove the native printing code completely. That would presumably mean (i) working out how to offer the user a target printer selection dialog without actually using KDE's printing mechanism at the time -- prior to running the job through Lilypond and then using KDE's print mechanism on the results (or is there perhaps a KDE facility that could be exploited to use Lilypond as some sort of output filter?), and (ii) making the Lilypond export code capable of exporting a subset of segments on demand (for printing from notation view etc). Chris ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
