You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<- <-- <== <-< <=< <<- <<= <~ <~~ -< -<< =<< <-| <=| <-> <=> <==>
They are rendered as arrows. However, the italic ligatures have holes in them.
The bugs occured in v1.0.3(as mentioned in #184), and were fixed in v1.0.4, but occured again in v1.0.5.
The text was updated successfully, but these errors were encountered:
— Fixed problem with disappeared Powerline arrows #189
— Added U+0336 #190
— Added >-> Ligature #194
— Fixed rendering problems with arrow in ligatures #196
— Added exclusion in ligatures with -- --- to treat loading #151
— Added source files in .ufo format
yvvt0379
changed the title
Bugs on these ligatures <- <-- <== <-< <=< <<- <<=
(Continuously updating)Bugs on leftward arrows
Apr 9, 2020
yvvt0379
changed the title
(Continuously updating)Bugs on leftward arrows
(Continuously updating)Bugs on some of the arrows
Apr 9, 2020
Major changes
— Fixed problems with rendering of Powerline symbols #189
— Added support of Vietnamese language #14#209
— All diacritics redone. Corrected a bunch of problems of placing & more balanced mass.
— Added DesignSpace+UFO source files. Just converted & dumped as they are, for now. There are issues with Masters compatibility. Tested in Glyphs app.
Other fixes
— Fixed construction of † ‡ ∏ ∐ #205#206
— Added exclusion in /* ligature #88
— Refactored ß
— ~= ligature removed #204
— Added >-> ligature #194
— Added u0336 Long stroke overlay #190
— Added ligature //= #185
— Corrected contour of the arrows in ligatures #196
Known issues
— In Medium weights the height of [ ] { } decreased by one pixel in 12px, 13px sizes. This is a hinting bug.
<- <-- <== <-< <=< <<- <<= <~ <~~ -< -<< =<< <-| <=| <-> <=> <==>
They are rendered as arrows. However, the italic ligatures have holes in them.
The bugs occured in v1.0.3(as mentioned in #184), and were fixed in v1.0.4, but occured again in v1.0.5.
The text was updated successfully, but these errors were encountered: