这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@Finii
Copy link
Collaborator

@Finii Finii commented Oct 20, 2022

Description

They have added quite some more icons that people request/expect here also.

Unfortunately they seem to have no versioning anymore. So we update to this version

jesseweed/seti-ui@fd20793

Requirements / Checklist

What does this Pull Request (PR) do?

It adds a lot of new icons, existing/old ones are marked yellow in the following image.
The old codepoints are kept.
As they do not have stable codepoints that raises no additional issues for us (see here)

image

How should this be manually tested?

Any background context you can provide?

What are the relevant tickets (if any)?

Screenshots (if appropriate or helpful)

Finii added 11 commits October 19, 2022 08:31
From master branch, commit
jesseweed/seti-ui@fd20793

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Add "_nf" suffix to our own svgs.
Add our icons database

Adapt filename in icons database
Just change the filenames of the custom icons to include the new "_nf"
suffix.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Some icons are now existing twice.

* Their crystal icon looks wrong (rotationwise), compare with https://github.com/crystal-lang/crystal
* Their C logo misses the standard's hex shape
* Their C++ logo misses the standard's hex shape
* Their Elixir icons has a dent in the reflextion?
* Their Elm icon is colored
* Their Git Folder is not a folder
* Their Kotlin icon is colored
* Their Puppet icon is more correct
* Their Pursescript icon is identical
* Their Windows icon is more modern

That means:

* Do not include their crystal, elixir, elm, kotlin, purescript
* Do not include our puppet, windows
* Keeping both c, c++, git-folder

[note]
Keeping their old files around with changed suffix to find this commit
in the future on updates.

Reuse old icons that were labeled as 'seti' but have been vanished as
new custom types with appropriate file naming.

And remove 'red' versions of icons. We have a black and white font...

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Outline fonts are a bit picky about the embedded svgs.
Best is if there is only one path.

Ungrouped and path merged in Inkscape manually.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Some of the svgs still render incorrect in fontforge.

[how]
Different issues, for example wrong direction of the sub-path and still
(forgotten?) multiple layers, etc. Manually tinker until they work.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This still had a path direction mismatch.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
$ ./optimize-original-source.sh doit

Checking for SVG simplifications
  Files might be MODIFIED by this run ('doit' specified)
Found 177 svgs in ../../src/svgs
Simplification for ocaml.svg (5249 -> 3604) 68%
Simplification for apple.svg (3228 -> 2302) 71%
Simplification for pug.svg (5507 -> 4243) 77%
Simplification for jenkins.svg (13014 -> 6406) 49%
Simplification for firefox.svg (6276 -> 4640) 73%
Found 5 svgs to simplify

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
@Finii Finii force-pushed the feature/update-seti branch from 7bfc87e to 7ffc6d9 Compare October 20, 2022 10:01
@Finii
Copy link
Collaborator Author

Finii commented Oct 20, 2022

Original table here: #365 (comment)

image

After the PR we go from E4FA to E5AA. That will be shifted on patching to E5FA to E6AA, with a small (expansion) gap of 55 future icons to codepoint E700 where Devicons destination starts.

The end codepoint needs to be shifted, now all new icons are patched in.

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants