XSF Communications Team - 2025-04-20

Benson, I just realised that the XMPP logo looks rather squashed in the new SVG. Or maybe the blue part is missing? That's an issue I've noticed when using the XMPP logo SVG elsewhere too; not sure why

https://disroot.org/upload/06804900-4941-77c0-9b51-fb4239660933/xmpp_banner_newsletter.svg

How does this look? I used Archivo which is the OFL-licenced font closest to the XMPP logo that I could find (and the one I used for the xampu wrapping/flyers) ✏

The SVG includes the original text (hidden) so it can be customised, as well as a stroked version for compatibility

https://disroot.org/upload/0680492b-26bc-77bc-93c3-a735b9a5a944/xmpp_banner_announcements.svg

I see a black area both times

ColoRs do not appear for me. The background seems to be on top. The XMPP logo is taken from https://github.com/xsf/xmpp.org/blob/master/static/images/logos/xmpp-logo-text.svg with color modifications, can check size again if needed.

Black area where? Can you send a screenshot?

Try viewing in a browser.

The markup seems ok, but it renders black for some reason, perhaps try to export again.

https://disroot.org/upload/06804969-677a-7978-90b9-5da54e86ad79/298e7ce3-c598-4048-920f-401c447e1099.png

This is how it looks in my browser

Can you send me a screenshot of how it's displaying in yours, so I understand what the problem is?

> The markup seems ok, but it renders black for some reason, perhaps try to export again. I edited the SVG directly, so there's no export option ↺

i.e. it is already in the target format

https://disroot.org/upload/06804977-e1ec-7ebc-9fd1-9f734a3692d6/O7oIIFsHS6qQxgld-sFh7Q.jpg

https://disroot.org/upload/06804979-6e19-7c34-9d5a-77102ce4d2d3/JY5zo_cVTz-8Rw18iN4YGg.jpg

😮

Second image is after hiding background layer

That's weird

Looks like every colour got replaced with black?

Yes.

Wait let me send PNGs for now so you can review the designs at least 😛

https://disroot.org/upload/06804980-4b00-767c-a542-a42725cb627f/xmpp_banner_newsletter.png

https://disroot.org/upload/06804980-b78d-7874-add8-1428a8a1b0fd/xmpp_banner_announcements.png

https://disroot.org/upload/06804981-1c2e-71bc-bcd0-b4645076b215/xmpp_banner_specs.png

If you make changes to the svg in a git repo, that is easier for me.

Shall I make a PR to your fork? https://github.com/bkmgit/xmpp.org/tree/newsletter-logo-svg

Since your SVG hasn't yet been merged to the main XSF repo

> Shall I make a PR to your fork? https://github.com/bkmgit/xmpp.org/tree/newsletter-logo-svg That would be great.

Would suggest using dark green or other colors with high contrast. For example navy instead of light blue and maroon instead of orange for the new symbols.

I think emus wanted pastels?

If the xmpp font is changed, would need to change it everywhere. It is probably a good thing to do as license is unknown, but may need more feedback. Font for other text can be changed more flexibly.

I took the XMPP stroked text from the existing logo. Only the "newsletter" and other text following it was changed

But I agree that it would be good to choose a clearly licenced font for XMPP in general

Benson, while committing my changes, I noticed a new style towards the end saying `path { fill: black; }` and `@media(prefers-color-scheme: dark) { path { fill:white; }}`. Perhaps that was causing the issue? No idea where it came from / why my Inkscape added it

One sec, let me push the changes and then you can review more easily

Ok. For the specs, rather than repeating the logo, maybe 'XEP' could be written instead?

https://github.com/bkmgit/xmpp.org/pull/1

> Ok. For the specs, rather than repeating the logo, maybe 'XEP' could be written instead? I was thinking about that too ↺

Thanks.

I only uploaded the newsletter one for now. When you find the fix, let me know and I can apply it to the others as well to add to the PR

Please make logo -> text change then using a font of your choice.

> Please make logo -> text change then using a font of your choice. Is it okay to just do it like that? This is the official XMPP logo we're talking about, so it seems like rather a radical change 😅️ ↺

Like does it have to be discussed somewhere first

Meant for spec file, not XMPP font

Oh lol

Yeah, will do that

I see you "merged" my SVG. Is it working for you now?

The other thing is maybe I should say "XSF Announcements" instead of "XMPP Announcements"? As the other one I was asked to make is "XMPP Community Announcements"

svg appeared ok in inkscape.

Responsive svgs are nice for presentation, but it is usually better to apply the color changes directly to the elements, rather than as an end change.

Maybe it was saved as an Inkskape svg and not a regular one?

> Responsive svgs are nice for presentation, but it is usually better to apply the color changes directly to the elements, rather than as an end change. I have no clue where that responsive style came from. Feel free to remove it if you think it breaks things! ↺

> Maybe it was saved as an Inkskape svg and not a regular one? I didn't know there was a difference 👀️ ↺

Can add responsiveness to output svgs, once done with other logos and text.

I usually use https://crates.io/crates/svgcleaner to convert the CSS into SVG attributes after Inkscape did the opposite action.

All colours being black is a typical case of the SVG using CSS, and the web server being configured to disallow inline CSS in its Content-Security-Policy header.

% curl -sIL https://disroot.org/upload/06804900-4941-77c0-9b51-fb4239660933/xmpp_banner_newsletter.svg | grep content-security content-security-policy: default-src 'none'; frame-ancestors 'none';

That was it.

badrihippo, it’s weird that your browser doesn’t respect that header, it does a lot to improve security, so if you disabled it you might want to reconsider.

> All colours being black is a typical case of the SVG using CSS, and the web server being configured to disallow inline CSS in its Content-Security-Policy header. 👍 ↺

I didn't disable it; in fact I was using LibreWolf that I'd expect to have had all the security related issues thought through 🤔️

It rendered fine in Epiphany as well

Anyway, I just realised there is in fact a "Plain SVG" export option in inkscape

https://disroot.org/upload/06804ac8-926d-745c-9e27-b796355fbb79/xmpp_banner_announcements.plain.svg

Does this render fine for you?

badrihippo, the only difference is whether it includes elements and attributes from the sodipodi and inkscape namespaces or not.

It still keeps styling in CSS instead of as attributes.

Just run svgcleaner on it.

Ah okay

https://github.com/RazrFalcon/svgcleaner

Is that the one you meant?

Yes.

I'm getting "Error: Unsupported token at [some line or the other]" unfortunately

Maybe my SVGs are more broken than I thought 😕

https://disroot.org/upload/06804af2-c136-7c8c-9b86-67ecad88a1e4/xmpp_banner_specs.optimised.svg

How about this "optimised SVG" where I told Inkscape to convert styles into SVG values, and then manually deleted those autodark things at the end?

Works fine. :)

Great! Benson, expect to soon see another PR heading your way 😉

badrihippo, which token was unsupported btw?

I didn't bother to check

But I can still do it, since I have the originals

Ah, it was the @media

You know what, let me just manually strip that stylesheet at the end. I'm pretty sure that's what's causing all the trouble. And after that I can run it through svgcleaner anyway just to be safe

Less painful than manually doing the "export" thing each time 😅️

I am posting this message, in case someone would want to argue for utilizing DOAP with news readers. https://github.com/lwindolf/liferea/issues/1430 *Add feed support for DOAP* ✏

Interestingly, the yaxim one you linked there rendered in a nice layout in my LibreWolf. (I unfortunately can't say the same for the Gajim one, which just printed out the XML directly): https://yaxim.org/doap/yaxim.rdf.xml

badrihippo, that’s thanks to an XSLT stylesheet, see the second line of that file.

You can request Gajim to add it too.

I see that now! Interesting

Gajim seems to have a similar stylesheet too

Just that it's not working for some reason 🤔️

Oh wait it is

When I load it directly (as opposed to trying to get the "raw" file from GitLab): https://gajim.org/files/gajim.doap

I supposed GitLab is adding a `Content-type: text/plain` or something

badrihippo. You would have to change the file extension to ".xml". It appears that browser vendors of big organizations do not want to support XSLT, so they sabotage it. gemini://woodpeckersnest.space/~schapps/journal/2024-06-08-the-assault-for-html-and-http.gmi gemini://woodpeckersnest.space/~schapps/journal/2024-12-04-publishing-sites-with-pure-xml-instead-of-html-and-xhtml.gmi gemini://woodpeckersnest.space/~schapps/journal/2024-06-11-xml-is-the-most-purposful-language.gmi

badrihippo: Can you push the original source svgs to git? Can optimise the svgs, but these are much more difficult to edit. For example, font and layer information are lost.

Have indicated a possible modification for XEP announcement see https://github.com/bkmgit/xmpp.org/pull/2 - though feel free to modify or not use.

Makes sense. Your modification looks good. I'm not signed in to GitHub at the moment but I'll commit the source SVGs and do a new push tomorrow