On 7/25/2019 2:57 PM, Ulrike Fischer wrote:
Am Wed, 24 Jul 2019 12:03:07 +0200 schrieb Hans Hagen:
Big Caslon Medium [BigCaslon.ttf] ABCDEFGHIJKLM
I don't have that file.
After number of test rounds we managed to get all fonts (with one
odd exception) working with these values:
Am Wed, 24 Jul 2019 12:03:07 +0200 schrieb Hans Hagen:
>> Big Caslon Medium [BigCaslon.ttf] ABCDEFGHIJKLM
> I don't have that file.
After number of test rounds we managed to get all fonts (with one
odd exception) working with these values:
BigCaslon.ttf needs {0, 1, 12}, the W*dings*
On 7/24/2019 11:47 AM, Ulrike Fischer wrote:
Big Caslon Medium [BigCaslon.ttf] ABCDEFGHIJKLM
I don't have that file.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 2
Am Wed, 24 Jul 2019 11:04:17 +0200 schrieb Hans Hagen:
>> we got a bug report that some (proprietary) mac fonts don't work
>> correctly. The reason seem to be that the OpenType cmap format used
>> by these fonts isn't supported by the fontloader.
>>
>> The necessary cmap formats are "platform 0 (
On 7/23/2019 8:49 PM, Ulrike Fischer wrote:
Hello Hans,
we got a bug report that some (proprietary) mac fonts don't work
correctly. The reason seem to be that the OpenType cmap format used
by these fonts isn't supported by the fontloader.
The necessary cmap formats are "platform 0 (Unicode), en
Hello Hans,
we got a bug report that some (proprietary) mac fonts don't work
correctly. The reason seem to be that the OpenType cmap format used
by these fonts isn't supported by the fontloader.
The necessary cmap formats are "platform 0 (Unicode), encoding 1
(Unicode 1.1(?)), format 12" and may