Copyright © 2008 Adobe Systems Incorporated. All rights reserved.
Use of this website signifies your agreement to the Terms of Use and Online Privacy Policy (updated 03-30-2007).
Search powered by Powered by Google
Thank you for licensing OpenType fonts from Adobe. In your font package, you may find several files and folders. To learn more about your licensed fonts, you will need Adobe Acrobat® Reader®, a free utility for viewing and printing Portable Document Format (PDF) files, as many of the files in this package are supplied as PDFs. If you do not already have the current version, Acrobat Reader can be downloaded from: http://www.adobe.com/products/acrobat/readstep2.html.
This Readme is updated periodically. To get the latest version of this readme, download the OpenType User Guide, or get other information about OpenType, go to http://www.adobe.com/type/opentype.
Although it is dependent on how you purchased your fonts, generally an OpenType font package from Adobe contains:
To keep the size of online font downloads small, and to ensure that other material is as up-to-date as possible, we keep current versions of this readme and other OpenType information on the Adobe Web site. This includes:
A cross-platform font file format jointly developed by Adobe and Microsoft, OpenType is an extension of the TrueType sfnt format that can now support Type 1 (“PostScript®”) font data and new typographic features. OpenType fonts containing Type 1 outlines have an .otf file name suffix, while those with TrueType outlines may have a .otf, .ttf or .ttc file name suffix. OpenType fonts with Type 1 outlines use the “Compact Font Format” or CFF to store those outlines. In Windows 2000, XP, and Vista, one can double-click on an OpenType font to get a sample sheet that indicates what kind of outlines the font file has.
In general, both “flavors” of OpenType are equally supported in Adobe applications and in the PostScript language. Because both flavors share the same structures for multi-lingual support and advanced OpenType layout features, it is usually easy for applications and operating systems to support both flavors equally well. This document is primarily about technical issues around installing and using OpenType CFF fonts.
NOTE: Mac OS X provides native support for OpenType CFF fonts (as well as PostScript® Type 1 fonts), and does not require ATM Light for use with native and carbon applications. Applications running in Classic mode in Mac OS X still require ATM Light.
NOTE: Windows 2000, Windows XP, and Windows Vista provide native support for OpenType CFF fonts (as well as PostScript® Type 1 fonts in GDI applications) and do not require ATM Light or the Adobe PS printer driver.
Symptom: A family of fonts appears to be installed. Some of the installed fonts from the family, but not all, appear in the font menu. Specifically, some of the weights are missing, and all of the italic fonts. The problem typically occurs in some applications (e.g. Microsoft Word, Adobe PageMaker, QuarkXPress) but not others (Photoshop, Illustrator, InDesign).
Explanation:
The other “missing” fonts are accessible by using the bold and italic style buttons in each application. Use this method to tell which fonts are linked to which.
Additional Information:
Style-linking is used with fonts of all formats in standard Windows applications. Most Windows applications only show the “base font” of any style-linked group in their font menus. The additional style-linked fonts won't show up separately in the font menu of these applications.
Being able to directly pick the style-linked fonts (the bold and italic) is possible in only a few Windows applications, specifically ones that bypass the operating system for their font-handling (including Photoshop, Illustrator and InDesign). In typical Windows applications, there is no way other than the style link to access the style-linked fonts. They don't show up in the menu on their own. If you want to get to the fonts that can be accessed by the bold and italic buttons in these applications, the only way to access them is by use of these “stylings”; there is no alternative.
People who are used to the Mac OS (or applications which allow direct access to style-linked fonts) often incorrectly: (1) expect that you can always “directly pick” even a style-linked bold or italic font from a font menu in any application; and (2) believe there is something wrong or inferior with using fonts via style links.
Using style links does have the limitation that in most applications, if no actual style-linked font exists, the Windows OS will provide a simulated approximation, with no warning that your “base font” is simply being slanted or double-struck to approximate italics or bold. Without close inspection (by zooming in or printing out), it can be difficult to tell the difference on screen. As long as there is a style link, and the linked font is available, the real, style-linked font will be used in the document and in print.
Note:
This issue applies equally to OpenType, PostScript Type 1 and TrueType fonts on Windows.
Symptom:
When documents are created in some Mac OS applications are opened in the Windows version of the application, incorrect fonts are displayed. Even though the same fonts are installed on Windows, the Windows version of the application doesn't recognize that the same font is installed. The problem occurs in common Windows applications such as Microsoft Word, Adobe PageMaker and QuarkXPress (but not Illustrator, Photoshop or InDesign).
Explanation:
This is another aspect of the style linking issue described above. To avoid the problem, whenever possible the Mac OS user must select the base font and use the style links to access style-linked fonts, rather than selecting the style-linked fonts (bold or italic) directly from the font menu.
Background:
Most of the information in the style linking section applies for the user on the Mac OS as well, it's just Mac users also have the option of directly selecting the fonts. However, for certain applications, if someone is creating Mac documents that will also be used on Windows, they must use the style links when available, or the Windows version of the application will not be able to correctly identify the font used.
Note:
This issue applies equally to OpenType, PostScript Type 1 and TrueType fonts on Windows.
If your OpenType fonts do not work under Mac OS 8 or 9, we suggest you check to make sure the following things are true:
If the fonts still do not appear in any of your application font menus, try the following steps. This will force ATM to rebuild its cache of OpenType font information:
If you have followed all above steps, are using ATM Light 4.6 or later, and the fonts do not show up in any application font menus, you may try the following troubleshooting procedure (note that end users have reported this to work, but Adobe has not been able to reproduce this situation):
Under certain conditions, OpenType fonts may lose their distinctive icon. In most circumstances, this does not cause problems with the functioning of the fonts. However, one known issue is that fonts put in an Adobe application's own fonts folder or the fonts folder at Applications Support: Adobe may not be recognized by Adobe applications that normally support use of such folders.
Depending on the Mac OS version, there are different options for restoring this information.
Mac OS 8/9:
To correct existing OpenType fonts, use the OTF FileTyper. This is a simple drag-and-drop utility that will automatically correct the file type and creator codes for files with names ending in “.otf”. This application will work on nested subdirectories and even entire mounted volumes. The utility is available as a free download from Adobe at: http://www.adobe.com/type/browser/otf_typer.sit.hqx. (Note: this utility does not work in Mac OS X.)
If the FileTyper does not work, or existing OpenType fonts already on the Mac later lose their icon again, you should try rebuilding your desktop.
Additionally, to help future OpenType fonts get the correct icon, go to the File Exchange control panel, see that “.otf” files are already listed there, and turn on both of the file mapping checkboxes.
Mac OS X:
Rebuild the Launch Services preference files. Note that doing this may cause you to lose customized changes you have previously made (for example, in the Show Info window).
Additional Information:
Adobe packages its OpenType fonts so that they will get the correct icon when unpacked. In OS 8 and 9, the file Type and Creator codes are used in conjunction with the Mac OS Desktop DB file to assign correct icons to files. If the Type and Creator codes are incorrect or missing, or the Desktop DB is corrupt or damaged, icons may not display properly. Additionally, moving OpenType fonts from other operating systems, such as Windows or Unix, may damage or eliminate the Mac OS resource fork, which contains the Type and Creator codes, and custom icons. The standard OpenType icon is seen from the Type “sfnt” and the Creator “ATMC”.
Mac OS X can use either Type and Creator codes, or file extensions, to determine file types and icons to use. This information is stored in the LS (Launch Services) preference files.
TrueType flavored OpenType fonts (.ttf) are generally not supported prior to Mac OS X. Some select Adobe applications such as Adobe Photoshop, Adobe Illustrator, and Adobe InDesign can use these fonts if they are placed in a “Fonts” folder located inside the main application folder. All applications running on OS X (outside of the Classic environment) can use the fonts.
Style-linking in carbon/native applications:
As noted below, this problem was originally fixed in 10.2.3, but apparently re-appeared in 10.4. This issue is fixed in Mac OS X 10.4.9.
Kerning in cocoa applications:
In Mac OS X up to (at least) 10.2.4, the native support in Mac OS X does not include support for kerning information in OpenType CFF and Type 1 fonts. This means that OS X cocoa applications which rely on the OS to provide kerning information (rather than directly reading the OpenType font) see the font as having no kerning pairs.
Optical variants in OS X Font Palette:
Some Mac OS X applications use the new “Font Palette” to choose fonts, as an alternative to traditional font menus. In such applications, with families which offer variant fonts of different optical sizes, such as Display, Subhead and Caption, the “Regular” font may not appear in the Font Palette. This occurs in Mac OS X up to 10.2.8. It has been fixed in Mac OS X 10.3 and above.
Style-linking in carbon/native applications:
The native OpenType OTF support in Mac OS X did not initially include support for style links between OTF fonts. This means that OS X native or carbon applications which relied on the OS to provide style linking information will treat the fonts as having no style links. Therefore bold and italic style buttons will either not work or will create synthesized styles (smeared or slanted) instead of accessing the correct font. This can have side effects: opening or importing a document authored on an earlier OS with OpenType OTF fonts using style links may result in the correct font not being found. Workaround: For applications using Adobe's common font engine, such as InDesign, Photoshop, and Illustrator, one can work around this problem by putting the fonts in the application's fonts folder or in the application support:Adobe:Fonts folder. This issue was fixed in Mac OS X 10.2.3 to 10.3.9, reappeared in 10.4.0 and is again fixed in 10.4.9. Mac OS X 10.2.2 supports style links, but they may yield incorrect/unexpected results.
Kerning in carbon/native applications:
In Mac OS X 10.0 and 10.1, the native OpenType OTF support in Mac OS X did not include support for kerning information in the font. This meant that OS X native or carbon applications which rely on the OS to provide kerning information (rather than directly reading the OpenType font) would see the font as having no kerning pairs. This issue did not affect any Adobe applications using Adobe's common font engine, such as InDesign, Photoshop, and Illustrator. Also unaffected were any applications which are not yet carbonized, such as PageMaker and FrameMaker. This issue is fixed in Mac OS X 10.2.
Non-ASCII characters in carbon QuickDraw applications:
In Mac OS X 10.0 and 10.1, the native OpenType OTF support in Mac OS X had incorrect on-screen display of some non-ASCII characters in carbonized QuickDraw applications. Non-ASCII characters are those encoded at 128-255 in MacRoman encoding, accessed via option or option-shift key combinations. In applications which are carbonized, and still use QuickDraw for on-screen display (rather than ATSUI or Adobe's common font engine), some of these characters display as different characters or as undefined. Despite the display problem, the characters do print correctly, to both PostScript and non PostScript devices. This issue is fixed in Mac OS X 10.2.
Although OpenType fonts from Adobe are compatible with virtually all recent applications, operating systems, and output devices, Adobe’s symbol or “pi” fonts in OpenType format use code points in Unicode that are not part of the basic, standard Windows and Mac character sets. (Unicode is a platform-independent character encoding standard that maps each character in a font to a unique value that is used to access that character.) As a result, the pi and symbol characters in OpenType fonts are not accessible in most applications from normal keyboards. For more information on these issues consult the pi font info PDF.
OpenType fonts from Adobe typically have one of three levels of fraction support:
Fonts in the first category generally have only the 1/2, 1/4 and 3/4 fractions. For these fonts, using the OpenType fraction layout feature can help access these fractions but no others.
Fonts in the second category tend to have thirds and eighths fractions as well as the basic three. For these fonts, one can use the OpenType numerator and denominator features to access the numerators and denominators, and either feature will turn a slash character into a fraction bar.
Later in the development of OpenType, somebody figured out how to do “arbitrary” fractions, creating the third category. Using the same set of glyphs as fonts in category 2, simply turning on the OT “fractions” can make any fraction at all, even things like 1,023.2/14,077.
When Adobe has had occasion to revise existing “category 2” fonts, we have updated them to “category 3” to support arbitrary fractions. We expect to eventually update all such fonts. Note that newer OpenType fonts such as Garamond Premier Pro, Arno Pro, and Hypatia Sans Pro include additional punctuation glyphs (period, comma, space, left and right parens) in their fraction feature to accommodate languages that use different numerical delimiters.
Note that turning on fraction formatting in category 3 fonts can also affect numbers and punctuation that aren't fractions, so one needs to be careful to apply fraction formatting to only the fractions themselves. Even when using fonts where this is not a problem, one might later change fonts, or use a newer version of a font; therefore Adobe strongly recommends that users adhere to this practice even when using fonts for which globally applying fractions formatting does not cause immediate problems.
Some OpenType Pro fonts from Adobe such as Minion Pro, Garamond Premier Pro, Arno Pro, and Hypatia Sans Pro contain a full set of polytonic (ancient) Greek glyphs. The expected behavior in both OpenType and non-OpenType savvy applications is as follows:
The initial release of Garamond Premier Pro has non-marking UpperCase forms as the default behavior in non-OpenType savvy applications. Also, versions of Minion Pro up to 2.015 do not contain the more complex marking/non-marking behavior present in Garamond Premier Pro and Arno Pro (all forms are marking only). This behavior may be added in a future release.
(NOTE: For the latest application compatibility information, make sure you have the latest version of this readme, which can be found at http://www.adobe.com/type/opentype.)
If you are using the latest version of ATM Light, or an operating system, such as Windows Vista, Windows XP, Windows 2000, or Mac OS X (with native applications) which has native OpenType support, OpenType CFF fonts should work with virtually all your existing applications. However, some applications which perform some or all of the font-handling normally done by the operating system may need to be updated in order to recognize and render OpenType CFF fonts (see below).
Below are some older Adobe applications that do not recognize OpenType CFF fonts and may fail to include them in their font menus.
A bug in ATM 4.6 interacted with the AdobePS 8.8 driver, causing OpenType CFF fonts to print as Courier. This bug is fixed by an update to ATM, patching your ATM Light to 4.6.1a or ATM Deluxe to 4.6.2a.
OpenType is not officially supported in ATM 4.5 (Light or Deluxe) and requires version 4.6 or higher. Earlier versions of ATM will not recognize, rasterize, or manage OpenType CFF fonts.
NOTE: The default character cache setting of 512K in ATM 4.6 may not be enough for some OpenType fonts. To increase this cache to at least 1 MB in ATM, go to “Preferences” in the File menu. An insufficient character cache is the most common cause of the dialog “(3) ATM Deluxe is unable to activate <fontname> ATM Deluxe is out of memory (-108)”.
ATM Samples in Mac OS 8 and 9: Double-clicking on a OpenType CFF or OpenType TrueType font in the Finder yields an error message saying that “No sample is provided.” This problem occurs because these versions of the Mac OS do not natively understand OpenType fonts. Mac OS X offers native support, allowing users to double-click on OpenType fonts to get samples.
Kerning reported by ATM Deluxe 4.6: ATM Deluxe can report on a number of attributes about a font, including the number of kerning pairs. Although ATM correctly provides all kerning in the MacRoman area to the Mac OS, reports often understate the amount of kerning in the font.
Printing with ATM 4.6 and AdobePS 8.8: A bug in ATM interacted with the AdobePS 8.8 driver, causing OpenType CFF fonts to print as Courier. This bug is fixed by an update to ATM, patching your ATM Light to 4.6.2a or Deluxe to 4.6.2a.
Unable to activate fonts: In some situations, it is possible to get the error “ATM Deluxe cannot activate <fontname> because there is already an active font with the same name,” when there is no such font already active. In such a situation, the following procedure may fix the problem:
Note that this problem may be triggered by replacing one version of a OpenType CFF font with another without ATM “knowing” that the font has changed. See immediately below for the correct procedure to replace an existing font with a different version.
To replace an OpenType CFF font that is managed by ATM with a new version, without causing the above problem:
ATM 4.1 for Windows is the first version of ATM to support OpenType. Earlier versions of ATM will not recognize, rasterize, or manage OpenType CFF fonts.
NOTE: If running Windows 95, 98 or ME, go to the “Settings” tab in ATM and increase the ATM cache setting to at least 512K.
For the best results, we recommend using only the most recent version of Acrobat (currently Acrobat 8.0). Versions prior to 4.05 may have problems correctly handling PDFs with OpenType fonts.
PDFWriter (general): For most high-end applications, we recommend using Acrobat Distiller, the ”Create PDF” driver, or the application's “Export PDF” function to create PDF files, instead of PDFWriter.
PDFwriter (Mac): OpenType CFF fonts work correctly in PDFWriter 3.0.2 and Acrobat 3.0.2, but don't work correctly in PDFWriter 4.0.5. You can embed western OpenType fonts in PDFWriter 3.0.2 and view in Acrobat 3.0.2, but if you open the PDF document in 4.0.5 you will either get a blank or bitmapped document.
Editing PDFs in Acrobat 4: Acrobat 4's PDF-editing functions do not allow editing text in an OpenType font while maintaining that font. This limitation is resolved in Acrobat 5.05.
Cut/paste/search in Acrobat 4 & 5: When a PDF contains alternate forms of certain characters from an OpenType font, Acrobat may not understand what the underlying character is, causing problems with cutting and pasting text to other applications, or searching the text within Acrobat.
Silentium® Pro Roman II may not print properly to PostScript devices from CorelDraw 8 on the Mac. Other fonts may also be affected by this problem. Workaround: In Corel's print dialog, unchecking the “Download Type 1” fonts checkbox on the PostScript tab will allow the font to print correctly.
For some OpenType CFF font families, CorelDraw 9, 10, 11 & X3 for Windows fail to show certain weights in the font menu. Typically, a base font and its style-linked bold are handled correctly, while additional weights which should appear separately in the CorelDraw font menu do not appear at all. For example, if the regular and the bold are style-linked, the semibold fonts might not appear in CorelDraw's font menu.
For some OpenType CFF font families, Corel Ventura 8 for Windows fails to print certain weights. These appear to be the same cases listed for CorelDraw above.
For some OpenType CFF font families, Corel WordPerfect 9 for Windows displays the fonts with extremely irregular spacing. Depending on the printer and driver, this may or may not affect printed output. These may be the same cases listed for CorelDraw above.
Font Reserve 3 can only activate OpenType fonts when running under Mac OS X, and only for carbon or native applications (not Classic applications). If running under Mac OS 8 or 9 (not Classic), use ATM Deluxe instead of Font Reserve.
FrameMaker 5.x will crash if text is set in any font with very extensive kerning, which includes some full-featured OpenType fonts such as Silentium Pro and Warnock Pro. This occurs because FrameMaker 5.x has a limitation on the number of kerning pairs it can handle. This problem was fixed in FrameMaker 6.0.
If the menu name of an OpenType font contains accented characters, (for example Orgánica GMM Semiserif) FrameMaker 6.0 for Windows does not correctly recognize these characters and may display the font name incorrectly in the menu. Note that the font still works correctly. FrameMaker for Windows will also show an error message when opening a Macintosh FrameMaker document using such a font, but the font will display and print correctly.
The built-in “Make Adobe PDF” function in Freehand 8 and 9 for Macintosh does not work correctly with OpenType CFF fonts, and may crash the computer. Workaround: use Acrobat Distiller or the Acrobat “Create Adobe PDF” printer instead.
Freehand 10 fails to print on OS X when a OpenType CFF font contains a large number of glyphs (approximately 1100+). Workaround: use Freehand 8 or 9, or run Freehand 10 under OS 9.
For many style-linked fonts, if they are accessed directly on the font menu in Freehand 10, they may look correct on screen, but they will not print correctly. This applies only to fonts that are also accessible via a bold or italic style link. Workaround: pick any base-style face from the font menu, but pick any italic or bold styled face using the style popup on the text menu in order to get the correct font in print.
Freehand 8 prints OpenType CFF fonts as Courier to PostScript printers, but prints correctly to non PostScript printers. This occurs only with the Windows version.
If only a single OpenType CFF font from a given family is installed, Illustrator will display the font's PostScript name in the Illustrator font menu instead of the menu name. This does not affect the functionality of the font.
PDF files, containing OpenType CFF fonts, exported from Illustrator 10.0.3 for Macintosh will not print from Adobe Acrobat 5 and Acrobat Reader 5 on Mac OS. Also, using Acrobat 5 to create an EPS file from such a PDF, will result in an EPS file that will also not print.
Workarounds: create PDFs from Illustrator 10.0.3 using Acrobat Distiller instead of Illustrator's PDF export, or by using Illustrator 10.0.2 or earlier; or print the PDF from a Windows version of Acrobat 5.
If an OpenType font makes use of the same glyph for two different characters, only one will show up. For example, if a font has both a micro symbol and a Greek letter mu, which both use a single outline, InDesign will show one of them as an undefined character. This problem is fixed in InDesign 2.0.
All fonts (any format) which are formatted as “all caps” (using formatting, NOT the “change case” function added in InDesign 1.5) and are also set to “metrics” kerning, retain the kerning of the lowercase letters. Workaround: if using InDesign 1.5, use the “change case” function, which does not cause this problem. This problem is fixed in InDesign 2.0.
OpenType CFF fonts activated with ATM 4.1 on Windows 98 and ME do not appear in the InDesign 1.0/1.5 font menus. Workaround: copy the fonts to the Adobe Fonts folder located at Program Files/Common Files/Adobe/Fonts.
If Adobe Type Reunion is active, InDesign may incorrectly cause some fonts (of any formats) to sort at the bottom of the font menu, as if they were foreign language fonts. This can be avoided by opening the ATR control panel and adding InDesign to the list of applications not supported by ATR. As InDesign handles its own font menus similarly, ATR is not needed when using InDesign.
When using the Windows Character Map accessory to copy/paste many common math or Greek characters, Excel 2000 will substitute generic versions of these characters. Excel 97, Word 97, Word 2000, Office 2003 and Office 2007 do not have this problem.
The Windows Character Map shows blank spaces or bullets for all undefined characters in an OpenType CFF font, instead of just omitting them and additionally displays glyphs for a number of Eastern and Indic languages that are not present in the fonts. This can make it more difficult to identify what characters a font supports, because considerable scrolling through the character map may be required.
Additionally, although almost all characters may be selected from the character map and pasted correctly into Unicode applications (such as Microsoft Office), the f ligatures at FB00-FB04 may only display in TrueType fonts. Even though an OpenType CFF font is selected, the ligature may display in the closest available TrueType or OpenType .ttf font instead. This appears to be no longer the case in Windows XP SP2, Windows Vista and Office 2003/2007 (i.e. the correct glyphs paste).
Microsoft Word 6, on both operating systems, may crash if kerning is on, and text is set in any font with very extensive kerning (including some full-featured OpenType fonts). Alternately, Word 6 may crash when turning kerning on for such fonts.
This problem is fixed in later versions of Word, including Word 97, Word 2000, and Word 2003 (for Windows) and Word 98, Word 2001, and Word 2004 (for Mac OS). Besides upgrading to a newer version of Word, one may work around the problem by turning kerning off for the selected text. (Note that kerning is off by default in Word.)
Microsoft Word's “Insert Symbol” function does not recognize OpenType CFF fonts as having extended character sets, but only shows the current codepage.
Microsoft Word X may not save OpenType OTF fonts in style definitions. If you define a style using an OpenType font, the font defined in the style may revert to Times when you save the style. This is fixed in the 10.1.2 and later updates to Word X.
PageMaker 7.x prints some recent OpenType CFF fonts (Arno Pro and Hypatia Sans Pro) as Courier to PostScript printers, but prints correctly to non PostScript printers.
PostScript Level 1: OpenType CFF fonts are not officially supported on PostScript Level 1 output devices. This means that although they work in some situations, they do not work in all situations.
PostScript Printer Drivers: In general, we recommend that you always use the latest Adobe PostScript driver. OpenType fonts have been observed to work correctly with earlier driver versions, and even with third-party PostScript-compatible drivers, but these configurations have not been formally tested by Adobe, and are not supported. Current compatible drivers are:
-Windows 95/98/Me: AdobePS 4.3 and later (version 4.4 is recommended)
-Windows NT: AdobePS 5.1.2 and later (version 5.2 is recommended)
-Mac OS: AdobePS 8.6 and later (version 8.7 or 8.8 is recommended)
Mac OS 8/9 printing:
With foreground printing on, and an external hard drive connected to a PostScript device, some very large OpenType fonts have generated a “TypeCheck” error when printing. Workaround: either use background printing, or disconnect the hard drive from the printer.
OpenType CFF fonts can be rotated, while Type 1 fonts cannot.
Although OpenType CFF fonts generally work with QuarkXPress, trying to use Quark 4's “text to box” function fails, with the error message “cannot turn selected text into a box because the text has no outlines.” This problem is fixed in QuarkXPress 5.
Users of QuarkXPress® 6.x may receive an error message with some OpenType fonts when printing, that the font “may be corrupt and may be substituted with Courier”; simply click OK and proceed. Generally, the font still outputs correctly.One possible workaround to avoid the warning is provided by Quark at http://www.quark.com/service/desktop/downloads/details.jsp?idx=545
Users of Quark Xpress 6.5 in Mac OS X 10.4.x may notice that at certain zoom levels, onscreen spacing of OpenType fonts appears erratic. Zoom levels that are increments of 10 (100%, 110%, 120%, etc.) appear correctly, but other values that are not increments of 10 (162%, 123%, etc.) may display uneven or erratic letterspacing. This does not affect printed output.
Extensis Suitcase 10 can only activate OpenType fonts when running under Mac OS X, and only for carbon or native applications (not Classic applications). If running under Mac OS 8 or 9 (not Classic), use ATM Deluxe instead of Suitcase.
In some cases, EPS files exported from InDesign 1.0/1.5, that contain OpenType CFF fonts, fail to trap in TrapWise 3.5.
Solution: Depending on how many OpenType fonts are used, you may need to switch the “Embed fonts” setting in InDesign from “complete” to “subset,” or the other way around. If an InDesign document uses only one OpenType CFF font (not one family, but a single font), then Embed Fonts must be set to “Complete” in the Export as EPS dialogue box. If the document uses more than one OpenType font, Embed Fonts must be set to “Subset.” Also, sometimes one must try the “Trap” button twice; the second time works, even though the first time yields a PostScript error.
Adobe provides one free technical support call for all type products. To contact technical support in the United States or Canada, for Macintosh support please call 206-675-6206 and for Windows please call 206-675-6306. For international support, the closest phone number may be found at: http://www.adobe.com/support/intlsupport.html
For more information about Adobe's Type products, please visit http://www.adobe.com/type or call Customer Service in North America at 1-800-682-3623.
© Copyright 2000-2007 Adobe Systems Incorporated. All Rights Reserved.
Adobe, Acrobat, Adobe Type Manager, ATM, Adobe Illustrator, ImageReady, InDesign, FrameMaker, Dimensions, Photoshop, PhotoDeluxe, PostScript, Silentium, Warnock, Minion, Garamond Premier, Arno, and Hypatia Sans are either trademarks or registered trademarks of Adobe Systems Incorporated. Apple, Macintosh, Mac OS, and TrueType are trademarks of Apple Computer, Inc. Microsoft, OpenType, Windows, Windows NT, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the U.S. and/or registered in the U.S. and other countries. Pentium is a registered trademark of Intel Corporation. PowerPC is a registered trademark of IBM Corporation in the United States. All other trademarks are the property of their respective owners.
OTFRM v30
April 13, 2007-twp/egm
Copyright © 2008 Adobe Systems Incorporated. All rights reserved.
Use of this website signifies your agreement to the Terms of Use and Online Privacy Policy (updated 03-30-2007).
Search powered by Powered by Google
