On Sat, Feb 20, 2010 at 9:01 AM, Orcan Ogetbil <[email protected]> wrote: > Yes. That is exactly what I need. To solidify let me make up an example: > So if CXXFLAGS is predefined, its contents should not be overridden by > you. But I should be able to override your defaults.
OK, I will do as described. [fonts] > This is mainly to avoid duplication of system fonts. If these feta and > parmesan fonts were available in Fedora, then I was going to remove > your copy of font files altogether and make the patch such that > rosegarden points to the system feta and parmesan fonts. Right, and that's what we need to avoid. These fonts have (as you noted elsewhere) varied between Lilypond versions, so if the wrong version is picked up, there's a risk that the notation editor will work incorrectly (or at least not look quite right) but the packager might not notice. Similarly, it would be a real mistake for any other program to pick up Rosegarden's builds of these fonts when it wanted the current Lilypond versions. > By the way, these feta and parmesan fonts that come with rosegarden > are not present in the recent lilypond releases. Are these some > modified versions? Old versions? They are unmodified old versions. I haven't checked the current state of Lilypond's fonts for a while now. It's not that we particularly want to stick with older versions or avoid newer ones, simply that different builds tend to have idiosyncracies that are more visible at small pixel sizes and we have to some extent tuned to the fonts we have (and if we updated, we'd simply be tuning for an equally specific but newer version). I'm less paranoid about this than I used to be, partly because the way we address fonts in Thorn has changed from 1.7.x and is now less subject to weird variations, and partly because we haven't done much work on tuning the details of layout for Thorn yet anyway. But it would still take some significant work and QA to change this. Chris ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
