Microsoft announces deprecation of Type1 font support and removal in a future release
Recently, Microsoft announced the deprecation of Type1 font support in latest Windows release versions, and the intention to remove Type1 support in a future release.
Refer to the 'Adobe Type1 fonts' section - 6th section down - within the following announcement ;
Deprecated features in the Windows client | Microsoft Learn
What does this mean for EngageOne products on current Windows release versions
It means that Microsoft have 'deprecated' support for Type1 fonts in the latest Windows release versions , and support for Type1 fonts will be removed in a future Windows release.
Refer to Microsoft 'deprecation' definition here ;
Deprecation: What it means in the Windows lifecycle - Windows IT Pro Blog
In practice this means that any EngageOne product , such as EngageOne Designer and Content Author which uses Type1 fonts as the Design font, will continue to work in the current Windows 24H2 release versions, but Microsoft will not fix any issues reported using this font type , and Type1 fonts may be withdrawn without further notice by Microsoft in any new Windows release.
Q> What are the next steps ?
A > Review Type1 font usage and source a supported replacement font type
- Review usage of Type1 fonts within EngageOne Designer Publications , published Templates, and EngageOne Content Author Messages and repositories,
- For custom Type1 fonts - such as those provided by a third party Font vendor for use in Design Publications, Documents, Active Contents and Content Author messages - contact your Font vendor for replacement modern Font types supported by Engage Designer and Content Author.
Note that Engage Designer supports - both - Open Type (Postscript outlines - .OTF filetype) and True Type (.TTF filetype) font formats as Type1 font replacements, whereas Content Author supports True Type fonts only as a replacement for any Type1 fonts.
- For any EngageOne Designer Designer , Documents, Active Contents , check the presence of the following Designer Barcode 'Mode' = 'Standard' and 'Barcode Group' = 'Universal' types ;
- 2 of 5 (Interleaved)
- 3 of 9, 3 of 9 (With Checksum)
- Code 128, Code 128 (A), Code 128 (B), Code 128 (C),
- PlanetCode
- PostNet, PostNet (Checksum only)
Also check for the presence of Designer Barcode Group 'PDF417 barcode types' and 'Type' = 'PDF 417'
For any of the above Designer Barcodes - which use Type1 fonts - migrate the usage of these to the equivalent Designer Barcode
'Mode' = 'Line Drawing (AFP,eHTML, PCL, PDF, Postscript & VPS)' .
You may need to tweak the Line Drawing Bar width and height to render the Barcode according to your requirements.
Will existing EngageOne product resources, HIPs, HIMs, ZIPs, etc containing Type1 , continue to work in future releases ?
Yes, Adobe as the originator of the Type1 font format, who also announced the original Type1 deprecation as a Design font in Jan 2021 for Jan 2023 end of authoring support, have stated that the Type1 font format being an integral part of the PDF and Postscript language definitions will continue to function ;
Support for authoring with PostScript Type 1 fonts... - Adobe Community - 11800091
This Type1 font resource support - i.e For Non Design font usage - applies for processing Type1 in all relevant EngageOne products for AFP, PDF and Postscript in ;
- EngageOne Generate
- EngageOne Enrichment
- EngageOne Vault
------------------------------
Paul Barron
Principal QA
EngageOne Compose (Designer / Generate)
------------------------------