> On 16 Aug 2023, at 16:23, Khaled Hosny <kha...@libreoffice.org> wrote: > > > >> On 16 Aug 2023, at 5:44 PM, Chris Tapp <opensou...@keylevel.com> wrote: >> >> Hi Guys, >> >> I’m supporting an organisation that is using LO to create pdfs that are used >> as inputs to a print-on-demand service, and we have identified a couple of >> issues that I would like to have a go at resolving: >> >> 1) The handling of font names differs between the Windows and MacOS builds, >> resulting in the rendering differing between the platforms; > > This is https://bugs.documentfoundation.org/show_bug.cgi?id=105298, I had a > stap at it recently on https://gerrit.libreoffice.org/c/core/+/155455, but it > is a complicated issue since macOS have no way of giving us the names we need > for windows compatibility, and if we start to read the font name ourselves > (like in the change above), more system API become useless (e.g. if we ask > for font fallback, we will get names that is different from what we now have > on our font list). > > I have some ideas to how to handle this, if you are still interested. > > Regards, > Khaled
Thanks. I had tried looking to see if there were open bugs for these, but I hadn’t managed to find them. Using the Open Sans Google Font, Font Book shows 12 styles: Regular Italic Light Light Italic Medium Medium Italic Semibold Semibold Italic Bold Bold Italic ExtraBold ExtraBold Italic Within a local build (MacOS) of LO that includes your patch, I see the following Family / Typefaces: Open Sans / Regular, Bold, Italic, Bold Italic Open Sans Extra Bold / Regular, Italic Open Sans Light / Regular, Italic, Bold, Italic Open Sans Medium / Regular, Italic Open Sans Semibold / Regular, Italic Within the latest release, all 12 styles are shown as Typefaces under the “Open Sans” family - which is consistent with the identifiers shown for each font in Font Book. I am definitely interested in any ideas you have to handle this. Chris
