feat(fonts): update Departure Mono to v1.500 #1874
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rektdeckard
force-pushed
the
tf/departure-update
branch
from
6a6e6f5 to
17f0995
Compare
|
Thanks for the PR! |
|
Any blocker to merging? |
|
No, but update to 'latest' will always be done directly before the release. It does not make sense to update now and again to 1.600 ;) before release. At the moment I'm quite busy with my day-time-work; everything needs to be ready here on August 3rd 😬 After that for sure software problems will boil up, and then hopefully more relaxed times are on the horizon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Update Departure Mono to
v1.500.Side note: we now support the full set of box-drawing characters (
0x2500-0x259f,0x2574-0x257f) and brackets (0x276C-0x2771), so it should be possible to use them in the patched font.Requirements / Checklist
Issue number where discussion took place: #xxx
What does this Pull Request (PR) do?
Update Departure Mono to
v1.500.How should this be manually tested?
Using the patcher scripts to test locally.
Any background context you can provide?
N/A
What are the relevant tickets (if any)?
N/A
Screenshots (if appropriate or helpful)