Dark-background / cleaner "official" logo variations

HP, I’ve discovered, is using the Python Powered logo in their HPLIP Toolbox (Linux printer management app), and boy are they whiffing it:

It seems clear they did the transparency themselves, for all of those logos, and they did it from white-background files without any regard for the possibility of them being placed on dark backgrounds.

I’ve been to the logos & trademarks section of the website, and I’ve read the FAQ, so I know that both outlined and color-altered variations of the logo(s) are acceptable without approval. I figured I’ll just whip something up and hand it off to HP in the hopes I can convince them to replace that abomination with something that doesn’t suck. (Ideally, in the original SVG format, since they’re using PyQt5 for the GUI and Qt has excellent support for SVG icons; there’s no real reason to ever use bitmaps in a Qt interface unless for some wrong-headed reason you actually want to.)

I’ve already downloaded the Python Powered logo SVG. While I can easily drop out the white background to make it transparent, that won’t solve the problem that the gray “Python” will look horrible over the “Adwaita dark” theme’s default window color. I can also easily swap the the “Python” word color from gray to white, although then it’s a dark-theme-only logo which I’d rather avoid. so, a transparent version with an aesthetic, white outline (one of the explicitly never-needs-approval options for using Python logos, per the FAQ) is probably the way to go.

Two things I thought I’d mention here, though:

  1. Since dark-mode UIs are currently in fashion again, the PSF might consider expanding the set of official ready-made logo options made available. Either:

    1. Including dark-background versions as alternatives (where the “python” gray has been swapped to a light color), or
    2. Adding a white outline to the official logos so that they’re compatible with a wider range of background colors.

    Right now, the only official options are the 3-color renderings against a solid white background. Everything else is left to the discretion of the downstream designer, which kind of invites horror-show situations like the HP use.

    The PSF is more than welcome to whatever I end up submitting to HP once it’s done, if you’d like.

  2. The color issue aside, can we get some clean SVG files for these logos? That Python Powered logo SVG I linked to? That’s a 176K file, and despite the metadata claiming it was saved from Inkscape, it’s absolutely lousy with proprietary Adobe Illustrator vendor cruft! Not to mention, there are entire layers of invisible crap just dumped into it. Including at least two separate copies of what appears to be a spot-color chart; one sits awkwardly on top of the graphic (partially obscuring it), the other is completely outside of the page area. There’s even an embedded copy of the entire Verdana webfont in an internal CSS stylesheet. #ForSomeReason! Despite all of the visible text being rendered as paths (and not typeset with Verdana anyway).

Dropping out the invisible layers, the proprietary Adobe crap, and all of the other cruft, I exported an Optimized SVG from Inkscape that brought it down from 176K to 13K, despite there being zero visible changes.

(Here, have that SVG, complete with background transparency enabled. I left the snakes’ eyes as solid white circles rather than knocking them out, because that felt more in keeping with the spirit of the logo-usage guidelines.)

(Edit: Dammit, Discourse! Well, that’s unhelpful. But at least there’s a link.)

Of course, an Inkscape Optimized SVG export also jetissons file metadata that would be better to preserve, like authorship credits. Which is why I’d prefer an official source… but with files that contain a more curated set of options, and not Adobe’s kitchen sink.


Please put them in contact with the PSF Trademark Committee to get this sorted and approved.

They will most likely be accepted, but you will still have to get approval for such derivatives. We don’t want these to spread uncontrolled (as has already happened in a lot of cases).

Regarding the SVG for the Python powered logo: Thanks for the research. We were not aware of this and will look into correcting the file.

(I am co-chair of the PSF Trademark Committee)

Ah, OK, thanks. It looks like I was reading portions of the FAQ and/or the Logo Usage Guidelines a bit too liberally. (Or at least, completely ignoring the fine print at the bottom of the first page of said LUG.)

I should mention, in case it makes any difference (probably not), that HPLIP is a free and open-source project distributed under OSI-approved licenses. It’s associated with a commercial entity, but not “commercial use” per se, at least not in the way I’ve generally understood the term. HPLIP is packaged in most Linux distros, including libre-only flavors such as Fedora.

Yeah, honestly if even dropping out the background is an alteration requiring approval, then IMHO the PSF has to supply reasonably-formatted, dark-background-compatible transparent “unaltered logo” files. So that everyone who simply wants to use it in a situation exactly like HP’s about box drop-in doesn’t have to (a) alter it (clumsily) to remove the rectangular white background, and then (b) come begging for the PSF’s permission. That just seems unsustainable, and to nobody’s benefit really.

Bug report in HPLIP’s Launchpad project: Bug #2002010 “HPLIP's use of the Python Powered logo requires PS...” : Bugs : HPLIP

Despite that being their official/only channel for support requests and bug reports, they basically never actually respond to anything reported there. It’s not at all clear to me that anyone at HP even sees those bug reports anymore. So I don’t know how much good it will do.

But hey, I tried. ¯\_(ツ)_/¯