On 2007-November-22 , at 18:05 , bulia byak wrote:
On Nov 22, 2007 3:15 AM, jiho <jo.irisson@...155...> wrote:
I'm affraid that won't help. The problem comes from Pango, the library Inkscape uses to get the font and font names, which does not like OS X dfont format. Compiling without X11 will render the font using either cairo or even the native OS X ATSUI system but the font names and faces will still be get through Pango and the same problems are likely to remain.
Maybe this is worth adding to the FAQ?
There is already a FAQ about the font problem. Do you suggest that I add something about the rendering of fonts? I am afraid this is not part of the problem. Well I would need to test to be sure of course ;) but the problem seems fairly forward: we can't get correct font names/representations (this is the part where I guess it's Pango's fault) so no matter how we display them (this is the part where X11/no-X11 would make a difference) the problem will still be here.
FYI, the FAQ currently reads:
[edit] Inkscape does not see some of the fonts (Mac OSX) It is a problem in the way Pango (the lib Inkscape uses to manage fonts) handles .dfont (and some .suit) fonts. One solution is to convert everything to individual ttf files (Times.dfont becomes TimesRegular.ttf, TimesItalic.ttf, and so on) with fondu or/and fontforge (both are available via Fink, DarwinPorts or with standalone installers). Beware though: * you'll end up with duplicated fonts, you need to suppress or disable one version (the dfont one) * do not disable system fonts (if you need system fonts in TTF for X11 apps, put them in an X11 specific directory, such as ~/.fonts) * this can cause problems with Firefox which mozilla guys do not seem ready to solve soon because the problem seems unconsistent in its appearance
JiHO --- http://jo.irisson.free.fr/