Copy link to clipboard
Copied
Two years ago I migrated my template from using the Lucida family created by Charles Bigelow (which I met personally in the 1990ies) to the more Uniccode savvy Noto family for the main text elements (body, lists, tables etc). In particular I wanted to use the condensed variation in tables.
My personal circumvention of the Noto Sans Condensed problem: Use Noto Sans and apply stretch 85% which (at least for me) gives the same visual impression.
References to this problem:
https://forums.adobeprerelease.com/framemaker/discussion/176/pdfl-does-not-find-installed-fonts-noto...
https://community.adobe.com/t5/framemaker-discussions/font-noto-sans-cond-does-not-behave-in-pdf-cre...
https://community.adobe.com/t5/framemaker-discussions/pdf-converted-from-framemaker-8-become-unsearc...
Copy link to clipboard
Copied
Might this be due to it being a Variable font?
Copy link to clipboard
Copied
I haven't seen any notion that Noto is a variable font. At least I get no answer on my question "is Noto a variable font" by google. And Google Fonts don't give any hint on the Noto page. A typical discription is this from typogram.co:
Noto is one of my favorite open-sourced font family of all time due to its extensive language support. Noto is a joint project by Google, Adobe, and Monotype to eliminate “Tofu,” which is the box that shows up when there is a missing character. Noto has italic styles, multiple weights, and widths, 3,741 glyphs, and supports 800 languages.
From all the avialable ttf files in Noto-hinted.zip I have installed these:
The last one is used for examples of RTL text.
The Condensed variants are only installable, while all others are editable. According to Microsoft that means:
My understanding of the Installable therefore is that it can not be embedded in PDF... Why this is the case only for the condensed variant is beyond my understanding.
Unfortunately Dov Isaaks is no more in our boat - he probably could enlighten me.
Copy link to clipboard
Copied
Perhaps another dead-end speculation, but how do the working and rubbished Noto fonts compare in codepoint coverage?
Specifically do the failed fonts include codepoints above BMP (above U+FFFF)?
FM doesn't yet support the Supplementary Planes (U+10000 and up), and I don't know what happens if you use a font that populates that region of the codepoint space. This is feature request FRMAKER-10976, just to forestall further filings.
Copy link to clipboard
Copied
Yes, Noto contains many code points in the Private Use area ... But that do all of the Noto's I have installed, not only the condensed variant.
In the meantime I have the font turned through the mill of FontLab 8 to get another version of ttf files (they are about 15% larger than the original).
PDFL can handle these:
But distiller still is not happy with it:
IMHO there is something rotten in the state of Google (to quote Shakespeare)...
For me it's clear that fonts still cause problems in FM when creating PDF...
But, wait a minute! I have checked in Word 2003 and get this output from the Adobe printer (which is installed with Acrobat 2017 pro):
This leads me to the assumption that the problem is somewhere in Acrobat - the distiller and the printer do not behave, while (at least with the 'milled' fonts) PDFL does
To dig for the background of this problem is IMHO an esoteric effort - which I don't need to do, as I have a reliable solution for my initial demand (condensed appearance in tables)..
Copy link to clipboard
Copied
re: Noto contains many code points in the Private Use area ..
Well, I was wondering about SMP codepoints, not PUA, but that's interesting; which PUA? (one is in BMP, and more are in the SMPs)
But in any case, your worthy experiments demonstrate that this isn't an FM problem per se.
re: IMHO there is something rotten in the state of Google (to quote Shakespeare)...
Their Code of Conduct used to emphasize "Don't Be Evil".
Find more inspiration, events, and resources on the new Adobe Community
Explore Now