adobe-fonts / adobe-fonts/source-serif

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

Ouverte
#124 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub
addressed in source files
Langage dominant
CSS
Étoiles
2.4k
Forks
165
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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!

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.