Adobe Caslon Pro Bold Italic Font Free Download
Vida Hubbert
I'm having a mysterious problem with Word (version 16.40) and the Adobe Garamond Pro font: Four variants of the font are installed (regular, italic, bold, and bold italic), but if I select regular, Word instead uses bold. It's as if the program can't see the regular (and regular italic) styles, except that Word itself lists all four styles in the font menu and displays the name of the font using the regular variant. It's just in the text that it's misbehaving.
No other app seems to have this problem, and Font Book reports no problems with the font. This behavior appeared only recently, as it was noticed first today in a file that uses the font and was last edited without problem on Aug 3.
I've tried clearing the system font caches and Word's font cache. I've tried disabling and re-enabling the font. I've restored a previous version of Word from Time Machine. None of these has had any effect. Other similar fonts work fine, for example, Garamond Premier Pro.
I have several files very carefully formatted using Adobe Garamond Pro, so I'm not eager to change the font to something that's working properly, then have to redo the formatting. Has anyone seen a problem like this and found a solution?
Another curious thing: The font menu that appears under Format->Font (rather than the one that appears in the ribbon) shows "Adobe Garamond Pro" as a choice the first time Word is run, but after that shows "Adobe Garamond Pro Bold" instead. It also, from the second time on, has a number of font names appearing in all upper case.
If I had to guess, the first time it's run Word reads in all the font data from the system correctly. When quit (or sometime before that) it writes that data to disk, but when it reads that data in subsequently, something goes wrong. However, I haven't been able to find where that info is being written, if that's what's actually happening. It feels like I'm trying to debug MS's app for them...
It's fixed. The culprit appears to have been Adobe Acrobat Reader DC and was fixed with a recent update (version 2020.12.20043). You may have to quit Word and restart it, you possibly have to run Reader once before the fonts work again.
Presumably this is a new behaviour that didn't used to happen? I would test the behaviour with an existing document in a new user account. If the fonts behave there, then you know it's some issue in your user Library. Go back to the original account, and test removing things, such as Word's preference files, application caches, etc.
Thank you so much for taking the time to explain. I just switched from Word to Affinity and am not sure this is the problem though. In Word, all these common fonts are easily made to italics or bold with one click. I imported my Word doc to Affinity to complete it and now am wondering if somehow Affinity doesn't recognize my file, and so is stuck. I just don't know and feel helpless. Thank you for trying to help .
I am using Affinity Publisher. I just tried opening a new document and the italics and bold work in the new document for all my fonts, but not in the document I imported from Word. Gosh, I would hate to have to start my book over
The only font I create a style for is Andika (body).... the other problem is that when I imported my Word document Affinity won't give me the usual style options. It's rather upsetting. I feel like I am going to have to start from scratch, or go back to Word.
I could try that. But I just tried something you suggested earlier. You said maybe the style I created was causing the problem. So I deleted the body style I created (which now made a mess), but now the italics and bold are showing. But only for that text frame. On the other text frame for another style I created, it won't show either unless I delete the style. Does that give us any more clues what could be happening. I suppose I could write it without any styles... not the best, but might work. Thoughts?
Good news! If I copy all my text into my notepad to remove the formatting from Word, then copy and paste it back into affinity, the italics and bold work! Now I still have to figure out why styles don't work.
I tried that but it didn't work. But it does work if I first remove all the formatting by copying it onto my desktop notepad. I suppose I can do that. Thank you so much for sticking with me! Any idea why my styles aren't working though?
Also depends on the fonts being properly configured.
What fonts were you were testing with?
And what Operating system?
If you are on a Mac, some of the Apple supplied fonts are purposely broken so the Bold and Italic buttons may not work properly.
Like @LibreTraining asked, it might be interesting which fonts cause issues. As just because other apps and programs provide bold and italic variants for them, those might be fake. IIRC Word (at least when I used it ages ago) just added an outline or skewed a font in order to provide a "bold" and "italic" variant of a font even if the font doesn't naturally provide either.
Adobe Caslon Pro Bold Italic is a timeless and elegant font that exudes sophistication and flair. With its bold and italicized style, this font is perfect for adding a touch of drama and emphasis to any design project. The strong, yet graceful letterforms of Adobe Caslon Pro Bold Italic make it a versatile choice for headlines, titles, and other display purposes.What makes Adobe Caslon Pro Bold Italic even more appealing is that it is available for free download at FontsMarket.com. This means that you can easily access this high-quality font without any cost, making it a valuable addition to your font collection. Whether you are working on a professional project or a personal creative endeavor, Adobe Caslon Pro Bold Italic is sure to elevate your design with its bold and striking appearance.
Many newer platforms can use strings intended for different platforms if a font does not include strings for that platform. Some applications might display incorrect strings, however, if strings for the current platform are not included.
There are two versions of the Naming Table. Version 0 uses platform-specific, numeric language identifiers. Version 1 allows for use of language-tag strings to indicate the language of strings. Both versions include variable-size string-data storage, and an array of name records that are used to identify the type of string (name ID), platform, encoding and language variants of the string, and the location within the storage.
Version 0 differs from version 1 in regard to handling of language identification: it uses only numeric language IDs, which generally are values less than 0x8000 and have platform-specific interpretations. See Name Records below for more detail.
When version 1 is used, the language IDs in name records can be less than or greater than 0x8000. If a language ID is less than 0x8000, it has a platform-specific interpretation as with a version 0 naming table. If a language ID is equal to or greater than 0x8000, it is associated with a language-tag record (LangTagRecord) that references a language-tag string. In this way, the language ID is associated with a language-tag string that specifies the language for name records using that language ID, regardless of the platform. These can be used for any platform that supports this language-tag mechanism.
The language-tag records are associated sequentially with language IDs starting with 0x8000. Each language-tag record corresponds to a language ID one greater than that for the previous language-tag record. Thus, language IDs associated with language-tag records must be within the range 0x8000 to 0x8000 + langTagCount - 1. If a name record uses a language ID that is greater than this, the identity of the language is unknown; such name records should not be used.
Each string in the string storage is referenced by a name record. The name record has a multi-part key, to identify the logical type of string and its language or platform-specific implementation variants, plus the location of the string in the string storage.
The name ID identifies a logical string category, such as family name or copyright. Name IDs are the same for all platforms and languages; these are described in detail below. The other three elements of the key allow for platform-specific implementations: a platform ID, a platform-specific encoding ID, and a language ID.
As with encoding records in the 'cmap' table, name records must be sorted first by platform ID, then by platform-specific encoding ID, then by language ID, and then by name ID. Descriptions of the various IDs follow.
The platform, encoding and language IDs of a name record allow for platform-specific implementations. Different platforms can support different encodings, and different languages. All encoding IDs are platform-specific. Language IDs are similarly platform-specific, except in the case of IDs used in conjunction with the language-tag mechanism of naming table version 1, described above.
For a typographic family that includes member faces that differ from Regular in relation to attributes other than weight, width or slope, there may also be some member faces that differ only in relation to these three attributes. For example, the Minion Pro family includes Minion Pro Display, but also includes Minion Pro Bold and Minion Pro Italic. IDs 21 and 22 should be used only in those fonts that differ from the Regular face in terms of an attribute other than weight, width or slope. For example, IDs 21 and 22 should be used in Minion Pro Display, but not in Minion Pro Bold or Minion Pro Italic.
Note: While both Apple and Microsoft support the same set of name strings, the interpretations may be somewhat different. But since name strings are stored by platform, encoding and language (placing separate strings for both Apple and MS platforms), this should not present a problem.
The key information for this table for Microsoft platforms relates to the use of name IDs 1, 2, 4, 16 and 17. Note that some newer applications will use name IDs 16 and 17, while some legacy applications require name IDs 1 and 2 and also assume certain limitations on these values (see descriptions of name IDs 1 and 2 above). Fonts should include all of these strings for the broadest application compatibility. To better understand how to set values for these name IDs, some examples of name usage, weight class and style flags have been created.
d3342ee215