Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong glyphs for phonetic ligatures U+02A3 through U+02AB #488

Closed
dscorbett opened this issue Apr 10, 2020 · 8 comments
Closed

Wrong glyphs for phonetic ligatures U+02A3 through U+02AB #488

dscorbett opened this issue Apr 10, 2020 · 8 comments

Comments

@dscorbett
Copy link

  • Your font version: 3.0.0-rc.6
  • Your font variant: all
  • Your operating system (name and version): macOS 10.14.6
  • Your application using Iosevka: hb-view

U+02A3 through U+02AB are rendered as digraphs, but they are supposed to be ligatures. For example, U+02A3 LATIN SMALL LETTER DZ DIGRAPH should not look like dz U+01F3 LATIN SMALL LETTER DZ. (The Unicode names are misleading.) Here they are in Iosevka Extended:
ʣʤʥʦʧʨʩʪʫ

@be5invis
Copy link
Owner

image
How about this?

@be5invis
Copy link
Owner

image
t-esh is also modified to look connected.

@dscorbett
Copy link
Author

In the new glyph of U+02A8 LATIN SMALL LETTER TC DIGRAPH WITH CURL, the bottom right end of the ⟨t⟩ protrudes slightly beyond the curl of the ⟨ɕ⟩. Was that intentional?

@be5invis
Copy link
Owner

@dscorbett These phonetic ligatures are built from the two parts so they may collide. Fixing that is too costy.

@be5invis
Copy link
Owner

image
By repeatedly knocking the second part this is now avoidable.

@throwaway571
Copy link

throwaway571 commented Apr 12, 2020

Glyph Design note: In the phonetic fonts I’ve come across, it’s the crossbar of the /t that reaches out and attaches to the /esh, not the exit stroke. The exit stroke may actually collide with the /esh, but only in proportional fonts when the spacing is too narrow. As for /ts and /tccurl, it might be possible for them to have two points of contact, one at the crossbar and one at the terminal.

Character Request note: There were two more IPA phonetic ligatures added in Unicode 12.0, U+AB66 and U+AB67. These are retroflex affricates attested in Chinese dialectology.

@be5invis
Copy link
Owner

image

be5invis added a commit that referenced this issue Apr 13, 2020
@throwaway571
Copy link

throwaway571 commented Apr 13, 2020

@be5invis Because the exit stroke of the /t in /tesh isn’t touching the /esh anymore, you might want to consider adding an upward terminal to it to mirror /t itself.

black-black-cat added a commit to black-black-cat/Iosevka that referenced this issue Apr 18, 2020
* More arrow fixup

* Add more detailed docs for building. Fixes be5invis#474

* Add docs for width customization

* Update Node.JS version requirement. Fixes be5invis#486

* Fix phonetic ligatures' shape. Now they are connected more closely (be5invis#488).

* Remove unused logs

* Fix LATIN SMALL LETTER TC DIGRAPH WITH CURL overflow

* Fix shape of U+AB30, U+AB64 and U+1DE7 (be5invis#489).

* Docs: fix required otfcc version (be5invis#490)

* Make dot removal work if a below or other mark is between the base and above mark

* Fix export of U+478 and U+479

* Make "ligtions using dlig and calt at same time" less strange

* Fixup format

* Fix shape of U+029A, U+1D08, U+1D4C (be5invis#491).

* remove "ai" knots

* Add U+AB66 and U+AB67 (be5invis#488).

* Force f-eng to be connected

* Add [reverse-rule] to simplify reverse subst code

* Make GSUB more efficient

* Need to keep correspondence

* Fix shape of U+1DF0 (be5invis#497).

* Adjust length of diagonal arrows

* Make double arrow only work with arrow2 selector

* Add ligation for shift-equal operators (>>=, <<=, >>>=, <<<=)

* Update visualization data

* Add ligation group "CLIK"

* Add warning about auto-generated README sections

* Add overrideSupportedLanguages list

* Bump version

* Fix incorrect sample images of ligations

Co-authored-by: Belleve Invis <belleve@typeof.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants