tonsky / tonsky/FiraCode

Add stylistic set for Typst compatibility

Open
#1,671 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

stylistic sets
Dominant language
Clojure
Stars
82k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

Hi! I'm developing a Typst editor and would love to use Fira Code, but a couple of ligatures conflicts with Typst's syntax. (Typst is a modern markup-based typesetting system in the vein of LaTeX.)

Issues:

  1. Heading syntax with ===

Typst uses = signs for headings:

= Heading - Level 1
== Heading - Level 2
=== Heading - Level 3
==== Heading - Level 4

In stylistic set ss08, the === ligature adds a third horizontal bar, making it visually distinct from = and ==. This breaks the visual consistency of heading syntax—all heading markers should look like repeated equals signs, not transform into a different glyph.

  1. En-dashes

Typst renders -- as an en-dash (–), which is standard typographic convention. However, Fira Code's -- ligature renders as a programming-style glyph with a small break in the middle.

Would it be possible to add a stylistic set optimized for Typst that adjusts the === ligature and renders -- as a continuous en-dash instead of a code ligature? This would make Fira Code perfect for markup/typesetting languages like Typst that mix code and typography.

Thanks for maintaining such an excellent font!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review Fira Code's existing stylistic-set behavior, especially ss08, and the handling of the === and -- ligatures. The work is done when a Typst-oriented stylistic set keeps repeated equals signs visually consistent and renders -- as a continuous en-dash without changing the default behavior.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.