-
Currently `Splitter.fixedLength` splits strings based on chars. It would be nice if the splitter had a configurable encoding, such as utf-8, for codepoints.
-
Whenever we add a new icon, the code points for other icons change, which breaks our CSS whenever we try to reference icons directly from the stylesheet (e.g. in a `:before { content: "\f137"; }` rule…
-
I seem to be running into some issues with generating an atlas from a character set where it includes Japanese characters.
I can reproduce this with every font I've tried so far, but as a test cas…
-
This project has gone through several evolutions, and I am using it for several projects. I'd like to go back and add tags to specific places in the code and document the state of the repo at each of…
-
I first reported this bug to fontspec https://github.com/latex3/fontspec/issues/497 but was told it's an engine issue.
I hope this is the right place.
I personally don't consider this high prior…
-
Neither here nor powerline/fonts has any documentation of what codepoints are supposed to be provided with which glyphs by fonts. This makes it virtually impossible for font authors to add support.
…
-
Trying to follow the instructions in this repo for setting up a codepoints.json file. The README says there are two options:
```js
pathOptions: {
json: './misc/icon-codepoints.json'
},
…
-
The application halts slow machines/devices quite a lot, so perhaps we should split the index into smaller parts - possibly with various-size chunks, so we can adapt to faster/slower machines and netw…
-
this will help when the icons are not configurable for some programs like exa
-
According to #453, several glyph support standards require that some existing ligature glyphs be accessible from dedicated Unicode codepoints:
- [ ] U+FB01 Latin Small Ligature FI `f_i`
- [ ] U+FB…