larsenwork/monoid

"Wrapping" ligatures in spaces

Open

#124 opened on Aug 11, 2015

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (7,781 stars) (168 forks)batch import
enhancementhelp wanted

Description

I'm starting to "wrap" ligatures in spaces to avoid current problems like this: screen shot 2015-08-11 at 19 02 01

Some ligatures can only have space to one side though and maybe some ligatures can't have spaces at all?

e.g. < ! - - won't work but< ! - - will

If you can see other examples like this amongst current ligatures then please let me know :)

Contributor guide

Tech stack
None
Domain
design
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
font design basicsunderstanding of ligatures
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
The issue describes a visual bug where ligatures with spaces on one side only cause rendering issues. Investigate the font's ligature code (likely in the source font files) to identify which ligatures are affected. Look at the comment thread for user reports of specific problematic characters. The goal is to determine if the ligature substitution rules can be updated to handle spaces correctly, possibly by modifying the OpenType feature code. Since the repository is archived with no recent activity, this may require forking the project or setting up a local development environment to test changes.