You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue with the appearance of the Montserrat font in the PDFs produced using ArcGIS Pro 3.0.x within a virtual environment.
Describe the bug
Font appears to have void space where vectors in the font overlap. ArcGIS Pro is embedding this True Type Font as a Type 1 Font in the PDF. PDF displays incorrectly in several applications (Adobe Acrobat DC, Adobe Photoshop and FireFox).PDF displays correctly in several applications despite being embedded as a Type 1 Font (MS Edge, Chrome).
To Reproduce
Steps to reproduce the behavior.
Using ArcGIS Pro 3.0.x in a virtual environmental (Citrix on Windows Server 2019), create a layout that utilizes Montserrat 8.0 true type fonts.
Export the layout as a PDF with embedded fonts.
Open the PDF with any of the following: Adobe Acrobat DC, Adobe Photoshop or FireFox
Adjust the zoom level on the document to reveal the void spaces in the font. The font will display correctly at certain zoom levels.
Review the PDF document properties within the FONT tab. All instances of the font will be listed as a Type 1 Font.
Expected behavior
The font should be embedded as a true type font. The font should display without visual defect regardless of PDF viewer or display zoom level. ESRI has determined this is a bug but cannot explain why it only occurs with this font and no others.
Screenshots
Additional context
None
The text was updated successfully, but these errors were encountered:
The "void spaces" are due to the overlaps being present in the static fonts.
Some text rendering engines are advanced enough to render static fonts with the overlaps (must be able to do this variable fonts).
Which is why it works fine in some applications (i.e. Chrome/Edge).
I assume you have control of what fonts to use... some options...
The TTF releases in the font designer's repo have the overlaps removed - see here: v7.222
and also includes OTF fonts - and OTF fonts do not have overlaps.
Run the GF v8 fonts thru a tool to remove the overlaps (like FoundryTools-CLI)
Convert the GF v8 fonts to OTF (which have no overlaps)
again could use FoundryTools-CLI or various other tools, online, or font editors
Montserrat 8.0 - True Type Fonts
Issue with the appearance of the Montserrat font in the PDFs produced using ArcGIS Pro 3.0.x within a virtual environment.
Describe the bug
Font appears to have void space where vectors in the font overlap. ArcGIS Pro is embedding this True Type Font as a Type 1 Font in the PDF. PDF displays incorrectly in several applications (Adobe Acrobat DC, Adobe Photoshop and FireFox).PDF displays correctly in several applications despite being embedded as a Type 1 Font (MS Edge, Chrome).
To Reproduce
Steps to reproduce the behavior.
Expected behavior
The font should be embedded as a true type font. The font should display without visual defect regardless of PDF viewer or display zoom level. ESRI has determined this is a bug but cannot explain why it only occurs with this font and no others.
Screenshots
![Montserrat Issue](https://private-user-images.githubusercontent.com/163560674/313256248-b295022d-a35b-49ac-95ab-4bc5681a7a1d.JPG?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA0NTQyOTksIm5iZiI6MTcyMDQ1Mzk5OSwicGF0aCI6Ii8xNjM1NjA2NzQvMzEzMjU2MjQ4LWIyOTUwMjJkLWEzNWItNDlhYy05NWFiLTRiYzU2ODFhN2ExZC5KUEc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwOFQxNTUzMTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00MWVlNzczYTFlMjZmZGExZDg1NzNhYjgzNjdlMzM3ZTdlOGUzZGJhN2M0NTFhYTMwNzkyOTQ4YmYxN2ZjN2JjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.KbTjoFG0fFcgO8RRf42PK1hTmquCP6y0IUT6UZKsrRI)
Additional context
None
The text was updated successfully, but these errors were encountered: