Jump to content

Recommended Posts

Posted

Summary

On Windows, Affinity Designer does not properly load all cuts of this typeface.  I haven't seen this issue arise with other typefaces, though Cooper Hewitt does seem to perform as expected in the operating system and other applications.  I have tried reinstalling the font files but no dice.

Steps to Reproduce

Tested with Affinity Designer 2.3 on Windows 11

  1. Download the Cooper Hewitt OpenType version
  2. Unzip and install the OTF files
  3. Check that the files have been installed in Windows' font browser in Settings > Personalization > Fonts > Cooper Hewitt.  All the cuts from Thin to Heavy should be listed
  4. Open Affinity Designer, create a new text object with the typeface set to Cooper Hewitt, attempt to view all the available fonts for Cooper Hewitt.
  5. Observe problem

Additionally, I was unable to reproduce this on my Mac... Seems to be a Windows only issue.

Screenshots

Windows 11's font settings on the left showing all cuts of the typeface installed.  Affinity Designer on the right is unable to display them all.

Cooper Hewitt font selection not appearing in Affinity Designer for Windows.  Also open and working as expected in Windows' fonts menu.

The typeface does work as expected in Figma for Windows and macOS, indicating that it is not a platform issue.

Screenshot2024-01-08123848.png.661d62bbcda575db7efbb2ac26b8e416.png

The typeface and all of its cuts appear correctly in the menu on macOS. They are usable as expected.  When the same file is loaded on Windows the typeface gets set to the default.

Screenshot2024-01-08at12_45_31PM.png.b249854be8bcf1c1c01707ea7cf321ba.png

Posted

It would help to have a screenshot showing the problem. My guess: the Variable version of the font is installed on Windows.

Variable fonts aren't supported in Affinity. 

They will appear correctly in the menus on macOS, but still wenty work properly. They won't appear correctly or work on Windows.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5

Posted

The original fonts are broken.
The style groups are not correct so they will not work correctly in most Windows applications, and also in many other applications such as Affinity.

"Fixed" versions have been made available by others.
But, the version mentioned in that thread still does not have a correct RIBBI style group (so the bold and italic buttons will not work properly).

I made a fixed version for LibreOffice quite awhile ago - would you like that version?
(it will work correctly in Affinity)

 

Posted

@kenmcdThanks for the offer, I've already grabbed the fixed TTF files from that GitHub thread, but I'll happily take your version and at some point will probably compile my own hah.

If this is indeed out of scope, go ahead and disregard this issue, that said things work as expected in Figma so perhaps Affinity could interpret the cuts similairly?  Seems like an edge case...

Posted
11 minutes ago, Shrinks99 said:

I've already grabbed the fixed TTF files from that GitHub thread

As I said that is still not 100% fixed - the bold and italic buttons will not work as expected for the Regular weight.
Bold and Bold Italic are in a separate style group.
Just keep that in mind - you can work around it.

11 minutes ago, Shrinks99 said:

If this is indeed out of scope, go ahead and disregard this issue, that said things work as expected in Figma so perhaps Affinity could interpret the cuts similairly?  Seems like an edge case...

Common issue from font designers who only work on one platform, and only work in certain applications - and do not care if the fonts work correctly for all situations.
No commercial fonts would do this because they want their fonts to always work correctly.
Not an edge case, just a lazy and/or uncaring font developer.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.