I encountered this issue as well.
I first tried the workaround suggested in duplicate bug #1083774. This worked, but then I realized I could work around the issue much easier by just replacing the font-name in the header-template of the company.
I encountered this issue as well.
I first tried the workaround suggested in duplicate bug #1083774. This worked, but then I realized I could work around the issue much easier by just replacing the font-name in the header-template of the company.