Add icon for hacklang

[4e554c4c]

Description

Please explain the changes you made here.

Requirements / Checklist

• Read the Contributing Guidelines
• Verified the license of any newly added font, glyph, or glyph set

What does this Pull Request (PR) do?

I downloaded the Hack icon from hacklang.org whose source is on github and is licensed CC BY 4.0. Then edited it to be monochrome/font friendly in inkscape, added it to original-source.otf in fontforge as U+E535, and modified font-patcher and friends to support the changes.

How should this be manually tested?

Any background context you can provide?

What are the relevant tickets (if any)?

Similar PRs: #862 #833 #429

Closes: #904

Screenshots (if appropriate or helpful)

[4e554c4c]

I have just been told this icon was already added to seti-ui upstream: https://github.com/jesseweed/seti-ui/blob/master/icons/hacklang.svg
might want to use that icon instead

[Finii]

Hmm, their latest release is still 0.8.3 0.8.1 from 2015.
Yet they talk about 1.0.0 in the readme.
Do you have a clue how they get that into atom?

Edit:
Obviously npm? Ah at least they have release tags, but no releases. Hmm.

[Finii]

Maybe the complete Seti stuff should be updated?

We have 59 'Seti & custom' at the moment, they have 168...

---

Space-wise ... we start at E5FA and the next set starts at E700 -> 262 codepoints

[4e554c4c]

microsoft/vscode@8023f20 this is the VSCode commit including the Hack icon from Seti UI, it looks like they just update the .woff font and give names to the codepoints

[4e554c4c]

It seems like VSCode pins a certain commit of that repo any time they update, they don't depend on releases

[Finii]

Ah, I found the font :-}

https://github.com/jesseweed/seti-ui/tree/master/styles/_fonts/seti

[Finii]

Quick comparison

Notably the C and C++ icons look not very nice with new seti (personal opinion). Some other icons got nice updates.

[Finii]

And that again reminds me, which I already mentioned somewhere else, that we should generate the original-source from the svgs in the release workflow.

[Finii]

@4e554c4c Maybe you are inclined to have a look at the PR above (931), that does away with the manual labor on glyph updates/inserts.

[4e554c4c]

@Finii I think I actually prefer the icon from the seti repo. How should I import it?

[Finii]

@Finii I think I actually prefer the icon from the seti repo. How should I import it?

Thank you. I would rather update all/most of Seti and add the 'new' Seti icons while being at that. Now with the autogen that is a breeze ;-)

At some point in the future we need a v2.3.0-RC1 :-> so that you can already try the new icon.

[4e554c4c]

ok, if that's coming in the near future this commit shouldn't be necessary
thank you :)

[Finii]

Thank you; without your info about Seti I would not have come round to finally implement auto-rebuilding and thinking about updating Seti - at all.