Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDF production issues when using Montserrat font in ArcGIS Pro 3.0.x in virtual environments #7393

Closed
sbleiler opened this issue Mar 15, 2024 · 2 comments

Comments

@sbleiler
Copy link

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.

  1. 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.
  2. Export the layout as a PDF with embedded fonts.
  3. Open the PDF with any of the following: Adobe Acrobat DC, Adobe Photoshop or FireFox
  4. Adjust the zoom level on the document to reveal the void spaces in the font. The font will display correctly at certain zoom levels.
  5. 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
Montserrat Issue

Additional context
None

@kenmcd
Copy link

kenmcd commented Mar 15, 2024

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).

The embedding as a TTF fonts as a Type-1 is an Adobe Acrobat issue - which means they are probably using Acrobat Distiller to embed the fonts (my guess).
See: Why do OpenType fonts appears as Type 1 fonts in the Acrobat font list?

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

@davelab6
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants