Siji Icons (really nice windowing icons)
I really like the look of these icons and they have really good windowing icons which is something that nerd fonts is missing right now:
https://github.com/stark/siji
@math0ne Thanks for the suggestion! So this would be another new glyph set. I can see your point regarding this having some good icons
There is a also a TrueType fork of it: https://github.com/fauno/siji, which should be easier to integrate.
@FlorianFranzen Yes thanks that would be easier and faster to add :smile:
So is there an update to this? What would be needed to make a PR?
nice to see siji font lovers here :) 5 years later I still have hope inside me <3 @ryanoasis
So is there an update to this? What would be needed to make a PR?
From my perspective what needs to be solved is the on which codepoints to put these.
In the ttf it occupies 0xE00 - 0xE276 (with no gaps).
Compare https://github.com/ryanoasis/nerd-fonts/wiki/Glyph-Sets-and-Code-Points#overview to see what has already been taken.
Then there is a limit of possible codepoints unicode blocks that we can utilize because only some are 'free' [1]. You see that there is not much space left in the PUA, especially for a set containing ~0x300 symbols. A possibility would be to use PUA-A instead, but then maybe we should have a decision on Material Design (and its relocation) first.
[1] https://en.wikipedia.org/wiki/Unicode_block
And then, for this concrete font ... the glyphs have a distinct low-res pixelated look: Is this really an improvement over similar icons that we already have, that are vector-ish?

This will of course break when Siji is incorporated...:

The question is, will there be any audience left if they have to change their Stlarch setup? Probably not?
Closing because transferred to https://github.com/ryanoasis/nerd-fonts/discussions/1095
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.