[NTG-context] Change of Optima to Optima Nova: how to get Optima Nova working?

Pablo Rodriguez oinos at gmx.es
Sun May 24 17:44:16 CEST 2020

On 5/24/20 1:50 PM, Gerben Wierda wrote:
>>>> [...]
>>>> I’ve decided to buy the Optima Nova font. But now that I use it, I
>>>> run into the problem that suddenly my fallback for Cyrillic has
>>>> stopped working.

Hi Gerben,

the only reason may be that fallback families only work if the main
family works too (I have just discovered that).

BTW, the issue with Optima Nova is that the font family seems to be
rather tricky. It seems to be "Optima nova Pro".

>>> \definefontfamily
>>>     [archimate]
>>>     [ss]
>>>   [Optima Nova]
>>> [  tf=file:/Library/Fonts/OptimaNovaLTPro-Medium.otf,
>>>    it=file:OptimaNovaLTPro-MediumIta.otf,
>>>    bf=file:OptimaNovaLTPro-Bold.otf,
>>>    bi=file:OptimaNovaLTPro-BoldIta.otf,
>>> ]
> [...]
> The first problem was solved, I had to rebuild the font database:
> mtxrun --script fonts --reload

After rebuilding the font database (required to use new fonts added to
the system), you don’t need to specify files, as long as you invoke the
right family name, such as in:

      [Optima nova Pro]% or whatever the family name is

> And latin text works. Fallback for cyrillic doesn’t yet.

Which is the output from "mtxrun --script fonts --list --all

Could you try the following sample and report back?

      [Optima nova Pro]


    The quick brown... Ядро метамодели.

If not you don’t get Cyrillic with Helvetica, please add the relevant
line from the log.

I hope it helps,


More information about the ntg-context mailing list