Closed scriptbae closed 8 years ago
@verandaguy took the simple approach, will upload later today after fixing other issues too
@larsenwork Perhaps you can try
sub greater equal greater by kleislirightarrow;
sub greater equal by gteq;
Note the order, longer first.
@be5invis I use contextual substitution for ligatures so that syntax wouldn't work. (I do it to make the "ligatures" work in misc terminal applications
@larsenwork So this? This is the “original” syntax for chaining substitution, and it can replace all characters matched in one rule.
sub greater' lookup geaterToKleislirightarrow equal' lookup toSpace greater' lookup toSpace;
sub greater' lookup geaterToGteq equal' lookup toSpace;
I defer to your aesthetic sense but I'd personally prefer a connected arrow (long =
).
@larsenwork the simple approach is good enough -- it's already a huge improvement when it comes to readability. Thanks a lot!
@be5invis huh, looks like I could simplify my substitutions quite a bit.
Currently, when working with Haskell (not that that's particularly relevant), inputting the Kleisli arrow operators:
<=<
and>=>
results in the ligatures producing≤<
and≥>
, respectively.This leads to readability issues when working with Haskell code in an environment where the font is Monoid.
I propose that either ligatures be implemented for the
>=>
and<=<
trigraphs, or that these arrows explicitly remove the ligatures for>=
/≥
and<=
/≤
(if this is possible; I have extremely limited experience working with font construction).This issue is related to #135.