On Wed Dec 10 18:36:30 2025 +0000, Nikolay Sivov wrote:
Ok, I see I confused otmpFullName with otmpFamilyName. Yes, unique name is not something for end user to see in a font selection list. It's true that some fonts do not install with font installation utility on Windows, it's not about otf vs ttf, but about missing things that wellformed font should have on Windows. Sometimes it's possible to add such fonts manually to windows/fonts, then to the registry, reboot, and use them. I don't actually know what Windows is using for otmpFullName on Windows, for the fonts that could be installed. API docs for [wingdi](https://learn.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-outline...) give: `The offset from the beginning of the structure to a string specifying the full name for the font. This name is unique for the font and often contains a version number or other identifying information.`
Based on that, and what I see commonly used for other fonts, the options are: using 4 (Full Name), if it exists, with 5 (Version), optionally if it exists; using 6 (PostScript), if that (likely) exists as an easy option; or constructing Full Name from 1 (Family) and 2 (Style), where "Regular" is not used for the Full Name. Any input on how to proceed? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9744#note_125404