kenmcd
kenmcd
> I notice that it's missing all ligatures. Character Set = Unicode character code points. Most ligatures have no code points. Sounds like you expected a Glyph Set. I _may_...
OK, here is the Glyph List. Too big for GitHub 10MB limit. Fira.Code.Glyph.List.v6-pre-release.2021-02-18.pdf (31MB, PDF) [https://workupload.com/file/2YxjzsmmA7s](https://workupload.com/file/2YxjzsmmA7s)
> U+23b0 and U+23b1 should align to make a single brace, but they don't Fira Code v6.002 does not have those characters. So you are seeing a fallback font -...
The context-aware punctuation makes sense for most users normal cases. When is "+-+why+-+" going to be used? I think most users would leave it as-is.
Windows uses the Segoe UI **ratio** character (2236) for the time. Source Code Pro (v2.038) does not have this character.
A similar issue was reported with the Cascadia Code font and Excel: https://github.com/microsoft/cascadia-code/issues/523 According to that discussion it may be related to when the words include accented characters. But that...
> Here is the status of the current support of these Unicode ranges in Source Code Pro (based on SourceCodePro-Regular.otf version 2.030): > ## Braille Patterns > code point character...
> Long story short, would be excellent if Source Code Pro would carry a glyph for permyriad ("‱") A curiosity question ... how/where is this character used? What is the...
Same results when tested on LibreOffice v7.0.3.1 (x64) on Windows 10. The TTF versions installed with LO (v2.030/v1.050) work fine. The OTF versions (v2.030/v1.050) export DummyName to the PDF. Tried...
I don't understand. The name tables are identical in SourceCodePro-Regular `.otf` and `.ttf` files. Both have only `platformID="3"` . And the `.otf` does _not_ work and `.ttf` works fine. Minion3-Regular...