nooblab.blogg.se

Adobe fangsong std r normal
Adobe fangsong std r normal








adobe fangsong std r normal
  1. #Adobe fangsong std r normal pro
  2. #Adobe fangsong std r normal windows

> Weights=Thin 100, ExtraLight 200, SemiLight 250, Light, Light 300, I can just give a few hints that really aren't based on any

adobe fangsong std r normal

> Can anyone find errors in my syntax or confirm the bugs?

#Adobe fangsong std r normal windows

Not Windows will be left as is and hopefully those damn customers These questions are easy: Adobe doesn't care any longer about anyĬustomer's need for cross-platform compatibility. > file have font aliases in place to cater for the inconsistencies? > Why (given the inconsistent fonts) doesn't the default maker.ini > Why does Adobe supply inconsistently structured fonts for the (I don't have enough room to list the aliases that DO work.) in the console about missing fonts if you read in a document file Palatino alias works but still gives a nasty error pop-up and messages

#Adobe fangsong std r normal pro

Minion Pro SmBd,*,Bold=Minion Pro,*,SemiBold,Regular Try to make the separate Minion Pro SmBd font appear as an additional The font still appears in FM as Bookman Old Style.īookman Old Style,*,Light=Bookman,Regular,Light,Regularīookman Old Style,*,DemiBold=Bookman,Regular,DemiBold,Regular at least not for Regular, Light, Bold, or DemiBold weights. Try to get Bookman Old Style to appear as Bookman but it doesnt work, I cant find a combination that gives me all three weights within theĪdobe Garamond Pro,*,Regular=Adobe Garamond Pro,*,Regular,*Īdobe Garamond Pro,*,Bold=Adobe Garamond Pro,*,SemiBold,*Īdobe Garamond Pro Bold,*,Bold=Adobe Garamond Pro,*,Bold,* Weights=Thin 100, ExtraLight 200, SemiLight 250, Light, Light 300, Book, Book 300, Regular 400, SemiBold, SemiBold 600, DemiBold, DemiBold 600, Bold 700, Bold45, Bold57, ExtraBold 800, Heavy 900, Bolded 700 Variations=UltraCompressed, ExtraCompressed, Compressed, Condensed, UltraCondensed, Narrow, Regular, Wide, Poster, Expanded, Black, 45, 46, 55, 56, 65, 75 (I remember that in Windows 95 the wildcards didnt work so you had to use an explicit entry for each combination of bold and italic.)Īngles=Regular, Kursiv, Slanted, Oblique, Italic, Obliqued, Inclined I might be using the wrong word for Bold in some cases, for example.Īnd as far as I can tell, the wildcards seem to work in FM8 on Windows XP. I am using the settings and aliases shown below in the maker.ini file in an attempt to compromise the differences between fonts that have come with UNIX FrameMaker in the past 10 years or so, and Windows fonts that have come from various sources including Windows FrameMaker.Ĭan anyone find errors in my syntax or confirm the bugs? (If you try editing the aliases make sure you keep a working backup copy of the maker.ini file.) Some of the aliases dont work, and some of my attempts at setting them up disturb FrameMaker enough that it cannot read a file without crashing. I am having problems getting the font aliases to work in Windows FrameMaker 8. These inconsistencies really throw a spanner in the works when it comes to achieving seamless cross-platform compatibility for documents. Why (given the inconsistent fonts) doesnt the default maker.ini file have font aliases in place to cater for the inconsistencies? Why does Adobe supply inconsistently structured fonts for the two platforms in the first place? The first two questions that spring to mind are: In the past (FM 4 to 5.5.6) I got around this problem successfully by standardising on the UNIX font names and structures, and in Windows setting up font aliases in the WindowsToFrameFontAliases section of the maker.ini file. Unfortunately, the fonts supplied with FrameMaker on the two platforms are structured differently, although they have the same name. I work on the same FM documents on both UNIX and Windows.










Adobe fangsong std r normal