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
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
Pablo Rodriguez mailto:oi...@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
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]
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
