Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not really related: to get VSCode to support comments, jsdocs, other syntax highlighting features using different fonts, you will probably have to use the extension vscode-custom-css from be5invis: https://github.com/be5invis/vscode-custom-css

Mine is:

  .mtki {
    font-family: 'IosevkaNFM-ExtraLightItalic', monospace !important;
    font-style: italic !important;
    color: #757575 !important;
  }

  .comment {
    font-family: 'IosevkaNFM-ExtraLightItalic', monospace !important;
    font-style: italic !important;
    color: #757575 !important;
  }

  .comment:not(.punctuation) {
    font-family: 'IosevkaNFM-ExtraLightItalic', monospace !important;
    font-style: italic !important;
    color: #757575 !important;
  }
Which looks like the last picture in this comment: https://github.com/microsoft/vscode/issues/36512#issuecommen...

Just be prepared to experiment a lot, VSCode's (Electron's?) font handling is buggy.

Why are font features so difficult to support correctly?



  Why are font features so difficult to support correctly?
Because the standards are mostly a result of slapping the name "OpenType" on existing behavior. There's maybe three or four ways to encode any given piece of information. The standards are a mess.

You can identify a font as italic in four different places with varying semantics. Off the top of my head, three different places to mark a font as bold (and this may not jive with the weight). Three different ways to specify vector glyphs (five if you include 'COLR' and SVG). Raster glyphs? Do you want PNG, JPEG, TIFF, or raw bytes? Should the raw data be bit or byte aligned?

The result of that complexity is that fonts often have all sorts of conflicting information. Depending on what behavior you're referring to specifically I'd be that the fonts themselves may be to blame. TrueType style glyphs specifically put a lot of burden for getting the hinting right on the font designer. CFF/CFF2 doesn't.

Noto went full Google. Noto Display was abandoned a few years ago. In their own words it's not intended to be what most folks would consider a display font so there's no good replacement. The metadata in last release is all kinds of fucked up.

Names are a hilarious shit show, what constitutes an appropriate name varies from font to font leaving app makers to come up with their own magic and leaving font selection a huge mess. Plus names can be encoded in any number of encodings. Apple still has MacRoman encoded strings in some of their fonts. Is Arial Black the black weight of Arial or a whole new font family?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: