cplusplus / cplusplus/draft

Use Fira Mono font for code

Open
#8,445 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

decision-required P3-Other
Dominant language
TeX
Stars
221
Forks
813
Avg merge
16h 4m
Merged PRs (30d)
36

Description

There has been some discussion on the topic of font changes on the linked parent issue. Thomas pointed out that we make some fairly advanced use of TeX features, and font changes may not be so easy. It seems like this wouldn't apply to our code font at least because monospace rendering is simple.

The rendering of ^^ in reflection code is why I think it's worth revisiting this issue.

There was an example standard PDF rendered with different fonts.

Issue with current code font

In general, our fonts are a bit antiquated and could use improvement. The regular serif font is very thin, and our carets look extremely squashed, which is particularly noticeable in reflection code:

Image

Actually, there are many glyphs our current code font that don't look good. Our & looks like there's way too much detail crammed into a box, and it's somehow less tall than %, which seems to fill the whole box.

Image Image

I know that it's subjective, but our %:%: and ^^ look extremely ugly to me.

Fira Mono

The proposed Fira Mono is an improvement in my opinion:

Image Image Image

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

Start by reviewing the linked parent issue and the example standard PDF comparing the current font with Fira Mono. Check how the draft renders code glyphs such as ^^, %:%:, and &, and consider the work complete when the code font change is applied without disrupting the draft's TeX rendering.

Written by the indexing model from the issue text.

Assessment

Tech stack
tex
Domain
documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.