Follow-up to #31 (custom fonts per map file), which imports a single style per font entry with bold/italic synthesized by the renderer.
This would let a custom font entry bundle multiple files — Regular/Bold/Italic/Bold Italic — so those weights/styles render with real glyphs instead of synthesized fake bold/italic.
Bigger data model than the single-style version (list of {weight, style, bytes} per font entry instead of one blob) and more import UI (attach multiple files to one font entry, tag each with weight/style). Deliberately deferred out of the initial implementation.
Follow-up to #31 (custom fonts per map file), which imports a single style per font entry with bold/italic synthesized by the renderer.
This would let a custom font entry bundle multiple files — Regular/Bold/Italic/Bold Italic — so those weights/styles render with real glyphs instead of synthesized fake bold/italic.
Bigger data model than the single-style version (list of {weight, style, bytes} per font entry instead of one blob) and more import UI (attach multiple files to one font entry, tag each with weight/style). Deliberately deferred out of the initial implementation.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #31 (custom fonts per map file), which imports a single style per font entry with bold/italic synthesized by the renderer.
This would let a custom font entry bundle multiple files — Regular/Bold/Italic/Bold Italic — so those weights/styles render with real glyphs instead of synthesized fake bold/italic.
Bigger data model than the single-style version (list of {weight, style, bytes} per font entry instead of one blob) and more import UI (attach multiple files to one font entry, tag each with weight/style). Deliberately deferred out of the initial implementation.