dodexahedron

I'm a fan of this by the title at least. Will love to see it later when I get back to work on things again.

I agree @tig that naming should be same as or similar to existing standard nomenclature, and do like the Padding, Margin, Border, etc naming better than Bounds, Frame, etc as...

The 10-contributor minimum also seems potentially difficult to clear for some otherwise good projects. Also, is that 10 ever or 10 as members of the project? And is it an...

So... As I'm analyzing this, I'm noticing there are some invalid test cases (which I think was probably already known, based on comments around those tests). In particular, the cases...

The new implementation of the FindHotKey method that I have is partially complete, in that it works seemingly correctly for BMP values, but still needs me to make the fixes...

Ugh. Sorry the formatting didn't come out like I wanted with that. Some things didn't get indented which should have and some got indented which shouldn't have. Here is the...

And here is the slightly modified second part, which is the fallback to full unicode, with the index reset fix applied: ```csharp if (!hotKeySpecifier.IsBmp || (curHotPos >= 0 && !Rune.GetRuneAt...

I'm totally going to benchmark this against the TextElementEnumerator, too, now that we have a cross-platform guarantee of consistent and correct behavior with it (which we didn't have when supporting...

Also, about TextElementEnumerator and the StringInfo class... It uses ICU, now, which means it uses the current "gold standard" unicode implementation, and will evolve with Unicode, unlike certain methods and...

> TL;DR. > > However, i scanned it and > That said, it's dorky that `HotKeySpecifier` is a Rune. The only valid values are those typable on a keyboard with...