Fini Jastrow f9f3612e80 Update Font Logos to 1.0.0 ... [why] Before Font Logos 1.0.0 there was no stable-codepoint guarantee, and the later revisions (0.18) reassigned the codepoints. That makes updating for us very hard, because we would have to resort the icons or follow the codepoint changes. With 1.0.0 this changed. That new major release introduced not only a codepoint guarantee, but it also shifted the codepoints from the F100 region to the F300 region, where we put them anyhow (in most cases). That is one subset less with 'dynamic base codepoint'. The reassignment of codepoints in Font Logos kept the codepoints stable for the icons we already have in release 2.1.0. But at the moment the 2.2.0 Release Candidate (which updated Font Logos with commit 557b8da) have added glyphs, which are on different points as compared with the Font Logos 1.0.0 release. What I want to say, we need to get this straight, before our 2.2.0 RC turns into a Release 2.2.0. Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>		2022-08-18 11:16:44 +02:00
..
scripts	Update Font Logos to 1.0.0	2022-08-18 11:16:44 +02:00