Hans, as reported in a previous message, using beta from 2015.07.16 13:30, enabling the newotf module in the following sample makes the Mechanica fonts not being loaded in the final PDF document: \usemodule[newotf] \definefontfamily [txfont] [tt] [Mechanica] [tf=file:Mechanica.otf, it=features:slanted, sc=file:MechanicaSC.otf] \setupbodyfont[txfont] \starttext \tt Test {\it amfe} {\sc amfe} \stoptext The attached newotf-error.log contains the error message. Since both font files were generated with FontForge, I would like to know what they are missing to report upstream to the FontForge developers. Many thanks for your help, Pablo -- http://www.ousia.tk
On 7/19/2015 1:27 PM, Pablo Rodriguez wrote:
Hans,
as reported in a previous message, using beta from 2015.07.16 13:30, enabling the newotf module in the following sample makes the Mechanica fonts not being loaded in the final PDF document:
\usemodule[newotf]
\definefontfamily [txfont] [tt] [Mechanica] [tf=file:Mechanica.otf, it=features:slanted, sc=file:MechanicaSC.otf]
\setupbodyfont[txfont]
\starttext \tt Test {\it amfe} {\sc amfe} \stoptext
The attached newotf-error.log contains the error message.
Since both font files were generated with FontForge, I would like to know what they are missing to report upstream to the FontForge developers.
there seems to be a cid entry operator seen when populating a private dictionary in the cff section you can add this in line 552 of font-cff: cid = { -- actually an error }, and the font will probably load then, unless there is a fundamental flaw (i don't know where to get that font) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 07/20/2015 12:31 AM, Hans Hagen wrote:
On 7/19/2015 1:27 PM, Pablo Rodriguez wrote:
[...] The attached newotf-error.log contains the error message.
Since both font files were generated with FontForge, I would like to know what they are missing to report upstream to the FontForge developers.
there seems to be a cid entry operator seen when populating a private dictionary in the cff section
you can add this in line 552 of font-cff:
cid = { -- actually an error },
and the font will probably load then, unless there is a fundamental flaw (i don't know where to get that font)
Many thanks for your fix, Hans. It works perfectly fine. The font was an improved conversion from a Type1 font I got from CTAN. Many thanks for your help, Pablo -- http://www.ousia.tk
Pablo Rodriguez mailto:oinos@gmx.es 20. Juli 2015 17:08
Many thanks for your fix, Hans.
It works perfectly fine. The font was an improved conversion from a Type1 font I got from CTAN. Improved in which way?
Wolfgang
On 07/20/2015 10:47 PM, Wolfgang Schuster wrote:
Pablo Rodriguez 20. Juli 2015 17:08
Many thanks for your fix, Hans.
It works perfectly fine. The font was an improved conversion from a Type1 font I got from CTAN.
Improved in which way?
Wolfgang, at least, I added the space character (which is missing in the original font). I don’t remember if I included other improvements. Pablo -- http://www.ousia.tk
participants (3)
-
Hans Hagen -
Pablo Rodriguez -
Wolfgang Schuster