chellomere

You should get some, they are rad

I have one that I bought in 2013. Has fallen to the floor countless times, still works like day 1.

It is a killer combo!

I'm happily running an Intel NUC as TV computer since 2013, and it's awesome for exactly the reasons you state. I invested in it when I realized how fully crap the "smart" features of my Samsung TV are. The ultimate controller for it is a combo keyboard and touchpad, I have the Logitech K400r.

The NUC is starting to show it's age now with its 4th gen i5, and I'm in the process of replacing it with a mini PC with an Intel N100.

It would make sense that a code editor could use a more limited subset of text rendering that could be more optimized.

Perhaps a bit surprisingly, Microsoft actually has pretty good documentation on OpenType. Here's info on what shaping applies to "standard" scripts:

https://learn.microsoft.com/en-us/typography/script-development/standard

And here's the landing page for the latest OpenType spec:

https://learn.microsoft.com/en-us/typography/opentype/spec/

Specifically for ligatures, you're looking for the liga feature which is specified in the font's GSUB table.

HarfBuzz does opentype shaping, that is, transforming strings of unicode characters to lists of glyphs with positioning. The significance of this can be hard to understand for someone used to the latin script, as that needs very little shaping - kerning is often the only thing that's absolutely necessary.

But in complex scripts, most notably the Indic, there's a lot going on. Unicode characters can merge into one glyph under circumstances, or one character can split into several, and relative positioning in both the x and y axis is imperative.

A reason that OpenType shaping is complex is that part of the rules for what to do will be found in the font, and part will need to be hard-coded in the code implementing it.

If you're going to roll your own text renderer, you'll have to care about the following areas:

• Rasterization/rendering to bitmaps, including hinting (notoriously difficult, old-style TrueType hinting instructions are bytecode, so you'll be writing a tiny VM for this)
• Shaping (Kerning at a minimum, full OpenType shaping for international support)
• BiDi (for full international support, primarily Hebrew and Perso-Arabic)
• A caching system for rendered text glyphs and shaped text runa, as it will be too slow to perform this each time you want to render some text

Let's just say that I do not recommend going this route unless you're prepared to spend a lot of time on it.

Y'know, you can turn off auto correction. It's the first thing I do with any keyboard on any smartphone.

Bon appetite!

Hey man, there's worse things to be than point of sales!

What kind of socks do you need for Linux Mint? Are any mint green ok?

Cool, I'll just whip out my peptide printer and try it out!