I am using OS 10.4.11, Inkscape .45. I started working on a file and used a specific font. Then I discovered that my effects are not working, so I had to download a newer build of Inkscape from http://inkscape.modevia.com/macosx-snap/ along with the python packages. I reinstalled Inkscape and got the effects working, but when I opened my old file, the fonts have changed to something generic, and I cant get them to go back to what they were! I rolled back to the older version on Inkscape, but that did not fix the problem. All my previous work with that font got messed up (I still have the original files in hopes of getting this to work.) Does anyone know how to get my fonts to work again? 2nd part of the question: And if I get new fonts, how do I add them to Inkscape running on OSX? Thanks for your help
On 2008-February-05 , at 08:02 , churro wrote:
I am using OS 10.4.11, Inkscape .45. I started working on a file and used a specific font. Then I discovered that my effects are not working, so I had to download a newer build of Inkscape from http://inkscape.modevia.com/macosx-snap/ along with the python packages. I reinstalled Inkscape and got the effects working, but when I opened my old file, the fonts have changed to something generic, and I cant get them to go back to what they were! I rolled back to the older version on Inkscape, but that did not fix the problem.
Could you perform these little tests, with the document that has the generic font and on both version of Inkscape: - select the faulty text, open the xml editor and check what the font attributes are (name, weight etc.) - check wether you see the font in the text and font palette (even if it's not used in the document)? - if you see it, what happens when you select the text and apply this font?
All my previous work with that font got messed up (I still have the original files in hopes of getting this to work.) Does anyone know how to get my fonts to work again?
Font got reworked between those two versions and the library that deals with fonts was also updated, but all that should have improved compatibility, not the contrary. Gail, could you look at that please?
2nd part of the question: And if I get new fonts, how do I add them to Inkscape running on OSX?
All depends on the format of the font. If you get a ttf font in a regular format (ttf extension) Inkscape should be able to see it. Inkscape has issues with fonts in the dfont format and with Microsoft Font Suitcases (no visible extension). If you install the font on your Mac the regular way (double click and click install), Inkscape should have acces to it. To force the refresh of the font library on startup, delete a file via a command in Terminal: rm ~/.inkscape/.fccache-new Inkscape will rebuild the font cache on next startup.
Hope that helps.
JiHO --- http://jo.irisson.free.fr/
- select the faulty text, open the xml editor and check what the font
attributes are (name, weight etc.)
these are the attributes: I'm using Culrz MT font-size:98.06591034px;font-style:normal;font-weight:normal;fill:#ff8080;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Curlz MT
- check wether you see the font in the text and font palette (even if it's
not used in the document)?
The font does not show up in the font palette
If you get a ttf font in a regular format (ttf extension) Inkscape should be able to see it. Inkscape has issues with fonts in the dfont format and with Microsoft Font Suitcases (no visible extension). If you install the font on your Mac the regular way (double click and click install), Inkscape should have acces to it. To force the refresh of the font library on startup, delete a file via a command in Terminal: rm ~/.inkscape/.fccache-new Inkscape will rebuild the font cache on next startup.
I tried forcing the font library refresh on both versions of Inkscape, original dmg and the new one, to no avail. I searched for the font Curlz under finder and it shows up in the Fonts directory... I noticed there are several other fonts that are in the fonts directory but dont show up in Inkscape. -Thanks-
On 2008-February-05 , at 19:12 , churro wrote:
- select the faulty text, open the xml editor and check what the font
attributes are (name, weight etc.)
these are the attributes: I'm using Culrz MT font-size:98.06591034px;font-style:normal;font- weight:normal;fill:#ff8080;fill-opacity:1;stroke:none;stroke-width: 1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font- family:Curlz MT
This is a (Microsoft I think) Font Suitcase format, which indeed causes issues. The strange thing is that it worked in an earlier version of Inkscape. I am guessing that the difference actually comes from the font itself. When did you start this piece of work? Did you upgrade your system or MS Office in between?
- check wether you see the font in the text and font palette (even
if it's
not used in the document)?
The font does not show up in the font palette
If you get a ttf font in a regular format (ttf extension) Inkscape should be able to see it. Inkscape has issues with fonts in the dfont format and with Microsoft Font Suitcases (no visible extension). If you install the font on your Mac the regular way (double click and click install), Inkscape should have acces to it. To force the refresh of the font library on startup, delete a file via a command in Terminal: rm ~/.inkscape/.fccache-new Inkscape will rebuild the font cache on next startup.
I tried forcing the font library refresh on both versions of Inkscape, original dmg and the new one, to no avail. I searched for the font Curlz under finder and it shows up in the Fonts directory... I noticed there are several other fonts that are in the fonts directory but dont show up in Inkscape.
OK, that's to be expected with font suitcases unfortunately. They can easily be converted to their ttf elemental form though. See the FAQ about that.
Please send this the needed info to Gail too, she's the font expert.
JiHO --- http://jo.irisson.free.fr/
This is interesting, I have not upgraded office since I started working on this in October. The last time it worked fine was last week, before I upgraded Inkscape. I don't think I changed anything else. I also found this font in MSOffice folders on my Mac, so it is an MS font... I'll convert it to ttf and see if that works. I can't think of anything else I changed. I guess I must have a whole bunch of these fonts from MS, is there a way to batch convert them or something like that so I can use them in Inkscape? Thanks
jiho wrote:
On 2008-February-05 , at 19:12 , churro wrote:
- select the faulty text, open the xml editor and check what the font
attributes are (name, weight etc.)
these are the attributes: I'm using Culrz MT font-size:98.06591034px;font-style:normal;font- weight:normal;fill:#ff8080;fill-opacity:1;stroke:none;stroke-width: 1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font- family:Curlz MT
This is a (Microsoft I think) Font Suitcase format, which indeed causes issues. The strange thing is that it worked in an earlier version of Inkscape. I am guessing that the difference actually comes from the font itself. When did you start this piece of work? Did you upgrade your system or MS Office in between?
- check wether you see the font in the text and font palette (even
if it's
not used in the document)?
The font does not show up in the font palette
If you get a ttf font in a regular format (ttf extension) Inkscape should be able to see it. Inkscape has issues with fonts in the dfont format and with Microsoft Font Suitcases (no visible extension). If you install the font on your Mac the regular way (double click and click install), Inkscape should have acces to it. To force the refresh of the font library on startup, delete a file via a command in Terminal: rm ~/.inkscape/.fccache-new Inkscape will rebuild the font cache on next startup.
I tried forcing the font library refresh on both versions of Inkscape, original dmg and the new one, to no avail. I searched for the font Curlz under finder and it shows up in the Fonts directory... I noticed there are several other fonts that are in the fonts directory but dont show up in Inkscape.
OK, that's to be expected with font suitcases unfortunately. They can easily be converted to their ttf elemental form though. See the FAQ about that.
Please send this the needed info to Gail too, she's the font expert.
JiHO
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
On 2008-February-05 , at 19:37 , churro wrote:
This is interesting, I have not upgraded office since I started working on this in October. The last time it worked fine was last week, before I upgraded Inkscape. I don't think I changed anything else. I also found this font in MSOffice folders on my Mac, so it is an MS font... I'll convert it to ttf and see if that works. I can't think of anything else I changed. I guess I must have a whole bunch of these fonts from MS, is there a way to batch convert them or something like that so I can use them in Inkscape? Thanks
It has been a frequent request associated with all these font issues. While it does not solve the underlying problem, it may ease the font conversion: I've finally put up a small app based on a script of mine which did this. Drop one or several font files on it and it will convert all of them to TTF, in the same directory.
http://jo.irisson.free.fr/dropbox/Font2TTF.zip
It uses Fondu[1] to convert Font Suitcases (wether they are dfont or the old Font suitcase format) and FontForge[2] for other types (otf, pfb currently). Fondu is included for 10.5 users (on Intel but I guess there are few 10.5 users on PPC). Fontforge needs to be installed (either via the link below or through MacPorts/Fink. I used MacPorts, it works fine).
WARNINGS: - this may just-not-workTM - it overwrites ttf fonts of the same name already present (this is to allow to reconvert fonts if you already did it, without having to manually deleting all of them). - this duplicates the fonts already present on the system. FontBook will put a dot next to their name. You'll probably need to deactivate a version so that OS X behaves sensibly. - if you convert system fonts, you'll not be able to deactivate them, hence you'll need to live with the duplicates - duplicated font can cause rendering problems on Firefox (last time I tried anyway)
ADVICE: - copy (not move, copy. this is achieved by holding down the Alt key when dropping the files) the fonts from your libraries (/Library/ Font, /Users/yourname/Library/Font) to somewhere (a folder on your desktop is fine), then select the fonts in this new location and convert them there, eventually select all the newly created TTFs and put them back in a font library folder (or double click each of them to install them) - if you want these TTF versions to be available to X11 apps only and to continue to use the rest idependently, move them to an X11 only location. ~/.fonts for example (the .fonts folder in your home directory). Do to this, in Terminal: mkdir ~/.fonts cd the-folder-where-your-ttf-fonts-are mv *.ttf ~/.fonts - manually rebuild the font cache, just to be sure. In Terminal: sudo fc-cache
Let me know if it works/helps/screws everything up. Cheers,
[1] http://fondu.sourceforge.net/ [2] http://sourceforge.net/project/showfiles.php?group_id=103338&package_id=...
JiHO --- http://jo.irisson.free.fr/
participants (2)
-
churro -
jiho