The logo of ro.wikipedia.org is different that that of en.wikipedia.org (different stroke/color for the puzzle lines). This can be seen by opening https://ro.wikipedia.org/wiki/Ajutor:Bun_venit and https://en.wikipedia.org/wiki/Help:Introduction in different tabs and changing between them in order to see the differences.
|Open||None||T150618 Provide HD logos for all projects|
|Open||None||T274778 Certain classic Wikipedia logos are blurrier than the logo on English Wikipedia (e.g. ro.wikipedia.org)|
We actually do (well, for some projects). :-). @Legoktm recently rewrote the way logos are maintained, see https://github.com/wikimedia/operations-mediawiki-config/tree/master/logos. In the config yaml file, some of the projects (including rowiki) do have path to vector logos on Commons set (and were recently regenerated). The good question is how to easily create PNGs out of the SVG. Right now, the management script simply asks Commons to provide an URL to the PNG, which...apparently doesn't work well in all cases.
Personally speaking, it's how I always updated logos, and usually it worked well. I'm personally happy to modify the download function to use something else to get the PNGs, I'm unsure what procedure to pick through. Before Legoktm's change, there was no such thing as centralized logo management, and the way to update the PNG was not standardized at all.
In the future, I would love to see the commons keys fully populated in the yaml config file linked above for all projects, and a reliable way to generate the PNGs, which would make logo management easy.
Does this make sense?
Looks like a good plan. :) Let's work backwards from it.
I'm comparing these files (the default previews) and don't see any difference between the globes in them.
The same URLs are returned by the API the script us using (see the sandbox), so I would say that this is not the script that was used to generate the logos at the last update. Maybe all we need is a bulk update and see what happens (i.e. what and/or how many logos change)? We can then decide if a bulk update is in order or we just update the communities that complain (ro, maybe cs). I don't have a specific threshold in mind, but I would say that if there are a few changes, we should update the logos even if the community did not complain.
That URL certainly was used. rowiki's logo was updated in 3ffd059, and I'm pretty sure @Legoktm just used the script he wrote when making the commit (as regeneration via the new yaml file was the commit's purpose).
I just made a quick flipping tool at https://people.wikimedia.org/~urbanecm/tmp/T274778-flip-rowiki.html. It flips two PNGs every 1.5 seconds, set to https://upload.wikimedia.org/wikipedia/commons/thumb/5/55/Wikipedia-logo-v2-ro.svg/135px-Wikipedia-logo-v2-ro.svg.png and https://en.wikipedia.org/static/images/project-logos/rowiki.png by default (just change the textfields if you want to play with it). I can't spot a difference on those two logos.
I see no difference between them. However, I see a difference on those two logos:
The difference in blurriness of the logo and spacing between characters of the text "Wikipedia" is noticeable
@Ciencia_Al_Poder I agree. with you. However, enwiki.png was generated using a different source SVG (as it's a different project). The good question is why did rowiki's SVG produce a wrong result, and how to fix it.
Also adding in @Gilles, who recently recompressed all Wikimedia logos, and created the new compress pipeline.
The 2x logos on en.wp, ro.wp and cs.wp all look fine to me, I'll have access to a 1x monitor to test those logos later.
I never regenerated the enwiki logos, probably we should. It's basically impossible to figure out where and who generated PNGs using what that I just trust the SVGs as the canonical true logo (unless they're wildly different, as is the case on a few wikis).
The logos I get are https://ro.wikipedia.org/static/images/project-logos/rowiki.png and https://en.wikipedia.org/static/images/project-logos/enwiki.png .
Screen resolution on this one 1960x1080, scaling is 100%.