Suitcase Fusion et Suitcase TeamSync deviennent Connect Fonts.
Vous avez des questions ?Cliquez ici pour obtenir des réponses.
Cet article n’est disponible ni en français. En consultant cet article, vous contribuez à notre réflexion sur sa traduction future.
Si vous avez besoin de plus d’aide ou si vous avez des questions relatives à l’assistance, veuillez contacter notre équipe dédiée d’assistance en français à l’aide de ce formulaire : https://help.extensis.com/hc/fr/requests/new
Affected versions
This article applies to all versions of Suitcase Fusion.
Finding and removing Type 1 fonts in Suitcase Fusion
Type 1 fonts will show as "PostScript" in the info panel. Multiple Master fonts (a variant of Type 1 fonts) will show as "PostScript - MM" in the info panel.
You can search for Type 1 fonts in your font library and system font folders by choosing Edit > Find Fonts. Select "Type" from the first dropdown menu, "matches" from the second menu, and "PostScript" from the third menu. Click the plus (+) button to add a second search condition; select "Type" from the first dropdown menu, "matches" from the second menu, and "PostScript - MM" from the third menu.
Select the fonts in the search results and choose Edit > Delete. In the dialog box that opens, click Remove from Suitcase.
Using PostScript Type 1 fonts in Suitcase Fusion
Suitcase Fusion recognizes and supports Type 1 fonts: you can add the fonts to your font vault, preview them, and activate or deactivate them.
Recent versions of macOS, Microsoft Windows, and other operating systems and applications have deprecated or eliminated their support for Type 1 fonts. As support for Type 1 fonts disappears from creative applications and operating systems, we can't provide support for using Type 1 fonts activated by Suitcase Fusion in specific applications.
- Adobe announced the end of support for Type 1 fonts in Adobe Creative Cloud applications by January, 2023
- Adobe Creative Cloud 2022 flags Type 1 fonts used in creative projects, and Adobe Photoshop CC 2021 and 2022 do not recognize Type 1 fonts at all
- Microsoft Office ended support for Type 1 fonts beginning with Microsoft Office 2013 for Windows and Microsoft Office 2016 for macOS
- Microsoft Windows applications that use the Windows Presentation Foundation frameworks can't use Type 1 fonts
- Apple describes Type 1 fonts as "might work but aren't recommended" on macOS; a prerelease version of macOS 10.15 couldn't use Type 1 fonts
- Android applications can't use Type 1 fonts
- iOS applications can't use Type 1 fonts
As the OpenType specification increases in popularity and adds new features, Type 1 fonts appear limited by comparison. Type 1 fonts created for Microsoft Windows aren't compatible with macOS, and vice versa. Type 1 fonts do not have support for Unicode character sets, color glyphs, custom ligatures, or variable outlines.
The Type 1 font suitcase file stores critical font data in the resource fork. Other operating systems don't have support for forked files, making it easy to destroy the resource fork of a font suitcase if you move them from computer to computer.