Re: bug 890040

Actually the only guaranteed way to resolve the font mismatch problem is to support SVG fonts and embed fonts with documents. We will have to do this ultimately, if we want to be taken seriously as a design app.

Other than that, we can be only "reasonably" sure. E.g. a user can take a Dingbats font and rename it to Times on his system.

What we can do now:

- Nathan, since you have access to different machines, could you please do a few tests to figure out what is the most common text font that would look OK for the tutorial? Just do a global search-and-replace of "Times New Roman" to any other font in tutorial.svg and see if it loads OK. I used Times New Roman simply because I have it, but I have little idea of what fonts arrive with modern distributions.

Of course if anyone else can do this on his/her system(s) that would be great. Especially valuable are "bare bones" systems with no additional fonts installed.

- Having default font configurable is probably not difficult to do, but it must be done in the libnrtype font matcher (so it does not take the first available font but looks up e.g. options.defaultfont) which I haven't looked at yet. Nathan, since you did some work in libnrtype recently, maybe you can hack it up? Or anyone?

_________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...