![]() ![]() I guess you didn't read my explanation of the solution very closely. OTF is supposed to be a superset of TT, no? I don't consider Adobe's OTF fonts to be "printer fonts", but I guess Windows XP does. I don't consider Adobe's OTF fonts to be "non-TrueType". But the newer OTF fonts that CS3 installed in Windows\Fonts seem to have PS outlines, and they DIDN'T show up. Re some versions of Caslon available: Yes, because there was an older version of Caslon (from CS or CS2?) that had TT outlines which I had installed in Windows\Fonts myself, and it showed up. What I will check out on a rainy weekend is changing the name definitions inside of the PFB (seems easy) and PFC file (not so easy as the family name there seems to be inside of a binary section.) Of course this cannot be a general solution, but I just want to know if I can group those styles together I think being compatible and - even more important to me - ungroup some of the styles such that I do not have only one family with 17 styles as it is now. Peter: You are right as two of my fonts are from a manufacturer other than Bitstream, I saw it when inspecting the PFB and PFM file. (At the moment, when exchanging documents across platforms, ID always asks me to remap the same fonts as last time.) What I would like to see in the future is a feature of document-independent font grouping and mapping. If, as in my case, Adobe FrameMaker enables me to select fonts in a way I am used to and on the contrary ID behaves in a way seemingly to not offer some styles, I will think of a bug at first rather than assuming a feature I should be glad about.Īs even the helpful experts that supported me here did not immediately find the solution for my problem, I think that the CS3 team (developers as well as product managers) have underestimated the consequences of the new behavior for the users. Most probably the new way CS3 handles fonts is much better than the old one CS2 did (which I never had installed) - I'm just missing transparency. I totally agree to you that almost all kind of software behavior is not based on random but on the idea to aid the users at their work. Interestingly, in all of the time that Adobe spent on trying to resolve this issue, they never tumbled to this. In short, unchecking this box made all Adobe fonts that were installed in Windows\Fonts available to all programs. This was also true in InDesign, Photoshop, et al, UNLESS I had copied the Adobe OTF fonts into Adobe's "private" fonts folder. Since I had checked this box, in programs like Word I saw only older TTF fonts, and those OTF fonts from Microsoft which have TrueType outlines (and have a TTF file extension).Īdobe's newer OTF fonts with PS outlines weren't available. all of the newer Adobe fonts) are NOT TrueType fonts but PRINTER fonts. OpenType fonts with PostScript outlines (i.e. Windows XP considers OpenType fonts with TrueType outlines to be TrueType fonts, BUT. I assumed the distinction was between raster fonts and vector (TTF and OTF) fonts. There's a check box there which reads something like this: "Show only TrueType fonts in the Programs on my computer". In Windows XP, at Control Panel/Fonts/Tools/Folder Options, you find a TrueType tab. When you try to use the fonts in office do they actually work, or just show up in the list? Have you scanned through the entire list in InDesign to make sure they aren't listed out of order, perhaps by foundry name?įWIW, I have finally gotten to the root of MY problem. It isn't clear to me from your post if you've tried loading the newly purchased fonts, or only the ones that might have come in the package from the designer. ![]() In the Windows font's folder they would be available to all apps, in the private folder only to Adobe apps. If you've purchased Windows compatible TT, T1, or OpenType versions of the fonts you SHOULD be able to either install them normally using the "Install Font" command from the fonts folder, or copy them into the private fonts folder as you've described. For reasons known only to Apple and the font folks, all of the font information is in the resource fork, so you see 0 kb files in windows if you try to install them. ![]() Mac fonts in those formats have two parts, a data fork which windows sees, and a resource fork, which windows does not see. It sounds like the fonts you tried to load the first time were Macintosh format TrueType or Type 1 fonts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |