Improve favicon

[kelson42]

We have only a minimal favicon but we should have a full favicon support for all possible devices. See https://realfavicongenerator.net/favicon_checker?protocol=https&site=library.kiwix.org%2Fcontent%2Fgutenberg_fr_all%2FA%2FHome.html

[benoit74]

@eshellman, is it still appropriate to use this logo : https://commons.wikimedia.org/wiki/File:Project_Gutenberg_logo.svg converted in the various formats needed ?

@kelson42 @rgaudin could you point a scrapper already adding appropriate sizes / companion files (manifest, ...) so we could reuse the code?

[kelson42]

openzim/phets has it implemented but this is in Typescript. AFAIK, no Python scraper has implemented this so far.

[eshellman]

[rgaudin]

@eshellman could you share the source of those images? Or at least higher resolution images. We'd need 512x512 for the large one and 48x48 for the simplified version (according to that website).

Is it only somewhere? Who's the author/license?

Finally, should the light color on the edges be removed (ie. have a rounded square on top of transparent background) ?

[eshellman]

I'll track that down. I have a transparent edge version of the png too.

[kelson42]

@eshellman Thx, I guess we have now the data material to move forward!?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.

[benoit74]

Nope, as mentioned and detailed here gutenbergtools/gutenbergsite#24 (comment) we would benefit from an online file + a file in higher resolution.

[benoit74]

Good online resources to understand files / resolutions needed / recommended / expected:

• https://mobiforge.com/design-development/adding-favicons-in-a-multi-browser-multi-platform-world
• https://web.dev/icons-and-browser-colors/
• https://www.emergeinteractive.com/insights/detail/The-Essentials-of-FavIcons/
• https://evilmartians.com/chronicles/how-to-favicon-in-2021-six-files-that-fit-most-needs

Should we :

1. use RealFaviconGenerator API at https://realfavicongenerator.net/api/non_interactive_api everytime the scraper runs in order to generate proper data with explicit settings
2. generate HTML / files with RealFaviconGenerator once and embed it in the scraper code (meaning we will have to run it again at a regular interval)

I prefer option 2 because it reduces greatly our dependency on an online service which might disappear + allow us to easily switch to another one / tweak the result if needed + it allows more easily to upscale the source image used to generate other ones manually with AI or other tools manually before starting the process

[benoit74]

I upscaled the image with https://imgupscaler.com/ (randomly chosen, no strong experience on those tools) and it gave very decent result even if some zones are a bit blurry. Resulting image is 516x516 ... sic

[mrcook]

By the looks of things this is an Albion Hand Press:

I'm sure the font would be easy to reproduce. Your favourite search engine would likely produce an un-watermarked image.

[eshellman]

wow, that's pretty good!