adobe-fonts / adobe-fonts/source-serif

Is the contour direction of `theta` incorrect/reversed?

Offen
#124 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
addressed in source files
Vorherrschende Sprache
CSS
Sterne
2.4k
Forks
165
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Two similarily looking glyphs, `theta` and `fita`, are created with a different contour order:

This results different contour order when converting the master .ufo to .pfa with the `tx` command:

Take this command for instance:
```bash
tx -t1 ./source-serif-main/Roman/Masters/text/master_0/SourceSerif_0.ufo /tmp/test.pfa
```

Here's the result (Left: `theta`, Right: `fita`):
![image](https://github.com/adobe-fonts/source-serif/assets/959433/b17f003f-e19e-4934-9afb-264c1a52f604)

If a font is produced with this source, `fita` will render correctly, but `theta` could be incorrect at certain size, probably depending on the rendering engine:

![image](https://github.com/adobe-fonts/source-serif/assets/959433/d195d190-6c67-4e4f-a8f4-9aaceda09b8d)
*(Same font but in different size; Word 365 on Windows 11)*

Note that fonts released here seems fine. The problem arises when a custom build from the masters is needed.

I checked several glyphs that are similar in composition (`Oslash`, `oslash`, `theta`, `Fita`, `fita`, `Obarcyr`, `obarcyr`, `Fita.sc`, `Obarcyr.sc`), with `theta`'s contour direction being the only exception, thus I tend to think this is something to do with the source, not the `tx` script, so I am reporting it here. Thanks in advance!

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.