User talk:JoKalliauer

	SpBot archives all sections tagged with {{Section resolved\|1=~~~~}} after 7 days. For the archive overview, see User talk:JoKalliauer/Archiv.

A barnstar for you!

	The Graphic Designer's Barnstar
	For cleaning up many drawings. Ma▀▄Ga 16:26, 28 August 2018 (UTC)[reply]

Thank you! :-D

The Error is not really important, since they are rendered correctly by librsvg (the Rendering-Libary of Wikimedia), "just" browsers show a warning, and stops loading the file, also they should just ignore the unknown attribute. To avoid this Warning you could correct the sourcecode of the SVG with any text-editor by adding xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" anywhere in the <svg >-tag, or alternatively you could delete everything containing inkscape: (f.e. inkscape:transform-center-y="-23.229832" or inkscape:connector-curvature="0"). (I did both.)

Example of original file:

<?xml version="1.0" encoding="UTF-16"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<!-- Creator: CorelDRAW X8 -->
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="1931px" height="1141px" version="1.1" style="shape-rendering:geometricPrecision; text-rendering:geometricPrecision; image-rendering:optimizeQuality; fill-rule:evenodd; clip-rule:evenodd"
viewBox="0 0 7229557 4273050"
 xmlns:xlink="http://www.w3.org/1999/xlink">
   <g id="g3138" inkscape:transform-center-y="-23.229832">
    <polygon id="path3475" class="fil5" points="2626654,4004654 3005125,4004654 3005125,4030993 2626654,4030993 " inkscape:connector-curvature="0"/>
    <polygon id="path3475_0" class="fil5" points="3383591,4004654 3005120,4004654 3005120,4030993 3383591,4030993 " inkscape:connector-curvature="0"/>
    <polygon id="path3475_1" class="fil1" points="3383587,4004654 4135251,4004654 4135251,4030993 3383587,4030993 " inkscape:connector-curvature="0"/>
   </g>
</svg>

Example of fixed file

<?xml version="1.0" encoding="UTF-16"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<!-- Creator: CorelDRAW X8 -->
<svg xmlns="http://www.w3.org/2000/svg" xml:space="preserve" width="1931px" height="1141px" version="1.1" style="shape-rendering:geometricPrecision; text-rendering:geometricPrecision; image-rendering:optimizeQuality; fill-rule:evenodd; clip-rule:evenodd"
viewBox="0 0 7229557 4273050"
 xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape">
   <g id="g3138">
    <polygon id="path3475" class="fil5" points="2626654,4004654 3005125,4004654 3005125,4030993 2626654,4030993 "/>
    <polygon id="path3475_0" class="fil5" points="3383591,4004654 3005120,4004654 3005120,4030993 3383591,4030993 "/>
    <polygon id="path3475_1" class="fil1" points="3383587,4004654 4135251,4004654 4135251,4030993 3383587,4030993 "/>
   </g>
</svg>

You could use https://validator.w3.org/check to check if everything is ok.

I edited, cleaned up much more, which is unnecessary, and on its own not worth uploading a new version.

In my first corrections I deleted the CSS-code and implemented it into the SVG, but since this might be unwanted, for further editing, in my later corrections (since 21:16, 27. Aug.) I decided to keep the CSS-code.

— Johannes Kalliauer - Talk | Contributions 07:47, 29 August 2018 (UTC)[reply]

Well, I doubt I will mess with code. I saw that you cleaned up some drawings of mine with text converted to curves, bringing back text. I don't know what is the problem with text: is it a application (Inkscape or Corel) or is it a rendering on Wikipedia. Very frustrating. So feel free to improve any of my drawings uploaded at Commons. Thanks again, and keep up good work.--Ma▀▄Ga 18:33, 1 September 2018 (UTC)[reply]

Administrator

čeština ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ English ∙ español ∙ فارسی ∙ suomi ∙ français ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ italiano ∙ 日本語 ∙ 한국어 ∙ македонски ∙ മലയാളം ∙ Plattdüütsch ∙ Nederlands ∙ português ∙ português do Brasil ∙ русский ∙ sicilianu ∙ slovenčina ∙ slovenščina ∙ svenska ∙ +/−

Herzlichen Glückwunsch, JoKalliauer! Du hast jetzt die Rechte eines Administrators auf Commons. Nimm dir bitte einen Moment Zeit, um dir die Seite Commons:Administratoren und die in Verbindung mit der Beobachtungsliste stehenden Seiten durchzulesen (insbesondere Commons:Administrators' noticeboard und Commons:Deletion requests), bevor du damit beginnst, Seitenlöschungen, Accountsperrungen oder Änderungen am Seitenschutzstatus bzw. an den geschützten Seiten selbst durchzuführen. Der Großteil der Bearbeitungen eines Administrators kann durch andere Administratoren wieder rückgängig gemacht werden, mit Ausnahme der Zusammenführung von Versionsgeschichten, die deshalb mit spezieller Obacht behandelt werden muss.

Wir laden dich herzlich ein, mit uns auf IRC Kontakt aufzunehmen: #wikimedia-commons @ irc.freenode.net. Es gibt auch einen Channel für Commons-Admins, der für sensiblere Themen sowie zur Koordination unter Admins genutzt werden kann. Du findest zudem in dem Commons:Ratgeber zur Administratorentätigkeit vielleicht eine nützliche Lektüre.

Bitte überprüfe, ob du in der Commons:List of administrators und den jeweils nach Datum oder Sprache sortierten Listen eingetragen wurdest, und ergänze deine Daten andernfalls.

I would suggest you to use new rights only in areas of your expertise or obvious cases at beginning. If you'll have doubts you should dig into pages like Commons:Copyright rules by territory, only mark problematic files and leave final decision for other administrators. --EugeneZelenko (talk) 14:01, 17 June 2019 (UTC)[reply]

Auch nen herzlichen Glückwunsch von mir, hatt ich gar nicht gesehen! Habitator terrae 🌍 20:08, 23 June 2019 (UTC)[reply]

Congrats! I just forgot to pass by and vote, but I'm happy for your adminship. If you need help on some administrative stuff, feel free to ask. Cheers! --Ruthven (msg) 15:17, 24 June 2019 (UTC)[reply]

Thank you for disfaking

Hi Johannes, for your conversions of Fake SVG to true SVG, you are awarded as a disfaker with that barnstar. -- sarang♥사랑 13:43, 27 November 2019 (UTC)[reply]

Du kannst ihn naturlich auch an wurdige disfaker weiterverleihen! Wie geht es dir mit deiner Familie? -- sarang♥사랑

@Sarang: Herzlichen Dank für den BarnStar. :-)

Meinen Eltern geht es gut, mein Vater wird im September rückoperiert werden und sie kommen gut alleine zurecht, auch wenn wir sie fast jedes Wochende besuchen. — Johannes Kalliauer - Talk | Contributions 18:08, 27 November 2019 (UTC)[reply]

Die upload-Vorschau

Hallo Johannes, da bei dir alles gut aufgehoben ist und du auch eine gewichtige Stimme hast:
in Commons_talk:Upload#Preview_image habe ich einen Beitrag verfasst, und dann noch in den proposals darauf hingewiesen; erfahrungsgemäß nimmt sich jedoch niemand solcher Petitessen an.
Falls auch du meinst, dass ein tatsächliches Vorschaubild sinnvoll sei und wiederholte Fehl-uploads vermeiden hilft, kannst du die Sache weiter verfolgen und den richtigen Leuten nahelegen. Gruss -- sarang♥사랑 07:29, 14 July 2021 (UTC)[reply]

Ja das nervt mit auch schon lange. (Ich weiß auch nicht wem ich es nahe legen soll, vl. schreibe ich ein phabricator-ticket, wo es versumpern wird.)

Als high-end-user verwende ich

lokal einen c-librsvg2.40.21-renderer (alternativ zu meinem Linux verwendeten rust-librsvg2.50.6)
User:Rillke/SVGedit.js
Commons:Commons_SVG_Checker bzw. https://svgcheck.toolforge.org/index.php

Für eine Durchschnits-userïn scheidet 1 aus, weil sie es installieren muss, ist auch nicht so straight-forward, weil c-librsvg2.40 alte Bibliotheken braucht die nicht mehr gewartet werden und ein sicherheitsrisiko darstellen (libcroco0.6).

Für eine Durchschnits-userïn scheidet 2 aus, weil sie commons.js editieren muss.

Commons:Commons_SVG_Checker ist imho mühsam und scheitert bei Dateien größer ~5MB, https://svgcheck.toolforge.org/index.php schafft etwas größere Dateien.

— Johannes Kalliauer - Talk | Contributions 13:51, 14 July 2021 (UTC)[reply]

BackgroundImage filter antialiasing pixel artifacts

On the left half, antialiasing pixel artifacts appear at boundaries of elements with a filter using BackgroundImage with a transparent background. On the right half, when the background is white, artifacts are absent

Hi Johannes Kalliauer,

May I bother you to report this bug on Phabricator as reported on en:Wikipedia:SVG_help#SVG_multiply_blending, please?

Thanks in advance,
cmɢʟee ⋅τaʟκ 13:05, 2 November 2021 (UTC)[reply]

Yes I will report it on phab:, however I will close it as stalled, since Wikipedia cann't fix it, except by changing the renderer phab:T40010.

The bug does not occur in any current svg-rendering-libary (rust-librsvg2.52,rendersvg,Inkscape,batik). Since c-librsvg is depreciated and not maintained any more, reporting it upstream (at rust-librsvg) is undesired.

So it is imho a sub-task of RFC: Re-evaluate librsvg as SVG renderer on Wikimedia wikis, which most likely won't happen before Upgrade Thumbor to Buster (imho User:GDubuc_(WMF) is responsible for the upgrade).

— Johannes Kalliauer - Talk | Contributions 14:02, 2 November 2021 (UTC)[reply]

Thanks a lot. BackgroundImage is obsolete anyway, but it's good developers are aware of it. cmɢʟee ⋅τaʟκ 14:09, 2 November 2021 (UTC)[reply]

Editing error in c:File:2022 Russian invasion of Ukraine.svg

I have reverted your edits in this file as they had removed the entire text from it when opened in its full size. Viewsridge (talk) 19:40, 12 April 2022 (UTC)[reply]

@Viewsridge: If you open the svg it is your local rendering, so it is the fault of your system not of the file. Please read Help:SVG#systemLanguage_processing and check File:SystemLanguage.svg for a simple example.

Do not revert the file, otherwise you break the French version of the file. — Johannes Kalliauer - Talk | Contributions 19:44, 12 April 2022 (UTC)[reply]

File:Ukr Inv Debug.jpg

This is how the file appears on my end when opened in full screen, it could be a system issue on my end but it could also be the same for several others. It's probably best the best to keep it in its former embedded form. Viewsridge (talk) 19:52, 12 April 2022 (UTC)[reply]

@Viewsridge: I will add a default language, but it is also used now in french-wiki, therefore give me some time to fix it. No the former breaks the french version, which is used in the french wikipedia. — Johannes Kalliauer - Talk | Contributions 19:55, 12 April 2022 (UTC)[reply]

@Viewsridge: what shows File:SystemLanguage.svg if you open the svg-file? Most likely your are not on an English system. — Johannes Kalliauer - Talk | Contributions 19:58, 12 April 2022 (UTC)[reply]

en shows adnd my system language is in English. Viewsridge (talk) 19:59, 12 April 2022 (UTC)[reply]

Did you open https://upload.wikimedia.org/wikipedia/commons/e/e1/SystemLanguage.svg ? — Johannes Kalliauer - Talk | Contributions 20:03, 12 April 2022 (UTC)[reply]

When opened in full screen it's giving me "other" although my system uses American English. Viewsridge (talk) 20:05, 12 April 2022 (UTC)[reply]

It might have to do with some browser extensions I use such as UBlockOrigin, however the important thing is that this format disables text for certain viewers and I happen to be one. It's best to keep a separate file for the French translation as it is done with German, Italian, Russian and other translated version. Viewsridge (talk) 20:05, 12 April 2022 (UTC)[reply]

No it has nothing to do with UBlockOrigin, only with your browser-settings, if your browser is "en-US "it should use "en" and not "other". If this is the case is a browser-bug, try another browser. — Johannes Kalliauer - Talk | Contributions 20:08, 12 April 2022 (UTC)[reply]

Your latest upload from 20:06 has fixed it, now the text appears again in full screen. Viewsridge (talk) 20:10, 12 April 2022 (UTC)[reply]

Still it was your browser fault not of the svg. And in this case svgs should definitely not be uploaded in different languages as done till now, because that is impossible to keep them up to date, as you see. Since most files are outdated it shows the importance of one single multilingual file. For more infos please read Commons:SVG_Translate_tool and User:Glrx#Translations:_internationalization_and_localization. — Johannes Kalliauer - Talk | Contributions 20:16, 12 April 2022 (UTC)[reply]

Indeed the current method of translation is quite useless as they lack updates, although the issue of the text not appearing for users who might have unknown system problems is not a valid excuse to use a broken file either. Nevertheless your latest updates has fixed it on my end. Viewsridge (talk) 20:19, 12 April 2022 (UTC)[reply]

e/c The file versions are messy, and the file may need substantial rework. There may not be a good solution on Commons.

The SVG file version of 19:42, 12 April 2022 has an unusual structure. The French version is a separate svg element at the end of the file and has an absurd use of systemLanguage="fr": the attribute is used not only in the parent text elements, but also the child tspan elements. Although systemLanguage="de" is present near the beginning of the file, there is no Germann text.
The SVG file version of 19:33, 12 April 2022 does not have a child svg element, but it has many switch elements with only a default clause. The only systemLanguage attributes are for Spanish: systemLanguage="es". French is absent.

The file demonstrates weaknesses in Commons SVG processing. Updated versions of the file are needed as the conflict develops, but making those updates are hindered because most graphics applications probably cannot handle multilingual files (Inkscape can). There are also several separate language-specific files that would need updates (e.g., File:2022 Russian invasion of Ukraine - de.svg). Glrx (talk) 20:50, 12 April 2022 (UTC)[reply]

@Glrx: I know I did it in a messy and dirty way. Maybe above I was to harsh for an admin. If noone else changes it I will try to improve it within the next days. (But I'm too busy.) Thanks for checking the file. — Johannes Kalliauer - Talk | Contributions 20:55, 12 April 2022 (UTC)[reply]

We are volunteers, and time is limited for everybody. Friday, Saturday, and Sunday were 14-hour days for me, and I spent most of Monday recovering. I do not see you abusing your admin bit. You did some content edits and backed them up with reasons. Similarly, Viewsridge made content edits and gave reasons for them. You both talked to work things out. That's the way it is supposed to happen. Glrx (talk) 22:42, 12 April 2022 (UTC)[reply]

Just a note. This multilingual file is cooperatively updated without much trouble. Many users have added translations with SVG Translate. SVG Translate is apparently more robust that I expected: it may allow simultaneous translations by different users. All those id attributes may have a significant purpose. In addition, users update the map's graphics with Inkscape (probably the only graphics editor that will tolerate switch translations). Problems do develop, but they are not outrageous. It is an interesting education. Glrx (talk) 17:20, 26 April 2022 (UTC)[reply]
@Glrx: I already noticed that many users added translations. What I do not understand why (almost) nobody tried to translate it before your edits, however after your edits so many people added more languages. Do you know why? I think SVG-translate had worked before my edits. — Johannes Kalliauer - Talk | Contributions 06:31, 27 April 2022 (UTC)[reply]
That question is excellent. I just noticed a complicated SVG file that would be difficult to translate, but one would still expect users to try translating it. I can see some possible explanations. People who were interested in the map may not have known about SVG Translate. Your reply post about using SVG Translate may have informed them about SVG Translate (IIRC, the OP was the first to use SVG Translate on the file). Once people start uploading translations, the upload comment advertises SVG Translate, so more people would learn about it. Until your edits, MediaWiki would not offer the "render this image in (language)" selection. That comment may have also informed people. Even if users knew about SVG Translate, SVG Translate would be difficult to use. SVG Translate would present a daunting number of possible translations (maybe 1200). SVG Translate should never have presented The first 600 of those because an ancestor's systemLanguage="fr" would prevent the display of descendant translations. That would give the SVG Translate user an unusual experience. The user might find some text to translate, add the translation in their language, and then notice that SVG Translate updated its image display but the new image did not show the translation the user just added. The user could do a lot of work without changing anything. A change would only occur if the user edited the labels from 600 to 1200, and it is unlikely that the user would notice the labels that far down. There may also be a healthy reluctance to use SVG Translate. If the file were being edited with Adobe Illustrator, then edits with SVG Translate could be reverted or lost during the next graphics edit. Your question is interesting. Glrx (talk) 16:49, 27 April 2022 (UTC)[reply]

If this were not so funny, I would cry

I vectorized a PNG using a clipping path, filter, and textPath. I expected that more would work. Rings disappear, rect disappear, WIKIDATA is partially filtered but color is lost.

Wikidata faux stamp (78 kB)
Using random process, but has librsvg bugs. (3 kB)
SVG 1.1 (12 kB)

Glrx (talk) 01:56, 21 May 2022 (UTC)[reply]

@Glrx: I replaced font-family="Arial, sans-serif" with font-family="Liberation Sans,Arial, sans-serif" since local rendering is more similar to Wikimedia-Rendering. — Johannes Kalliauer - Talk | Contributions 09:40, 21 May 2022 (UTC)[reply]

I recommend to use https://svgworkaroundbot.toolforge.org/ for c-librsvg2.40-bug-fixing.

However the textPath-bug-fixing you need e.g. https://github.com/RazrFalcon/resvg/tree/master/usvg or Inkscape. — Johannes Kalliauer - Talk | Contributions 11:14, 21 May 2022 (UTC)[reply]

Thanks for everything.

After I did the vectorization, I discovered File:Wikidata Stamp Round Light.svg, an original SVG that weighs in at 2.2 MB. The fonts in its source are Gill Sans and Sans. Very few fonts support extra-bold font weights.

I used RGB(#, #, #) because the color picker I use produces decimal RGB values. I meant to check the specification to see if it should be rgb(#, #, #), but I misled myself. It worked on Chrome and Firefox, and the functional color specification comes from CSS 2.0, so I do not expect capitalization to matter. (I know that librsvg does not handle HSV colors.) I saw zebras instead of horses.

Anyway, thanks for sorting it all out.

Glrx (talk) 17:56, 21 May 2022 (UTC)[reply]

Thank you for cleaning up some of my myriad messes.

Danke. Glrx (talk) 18:38, 3 June 2022 (UTC)[reply]

@Glrx: Sorry for overcrowding your watchlist.

I uploaded several files to Category:Renderings_of_SVG_test_suite_files_by_Glrx. Do you get a notice everytime I'm quoting you? Does it also happen if I use the template {{U}}?

Please check the files at User:JoKalliauer/SVG_test_suites#test_files_by_User:Glrx

— Johannes Kalliauer - Talk | Contributions 19:04, 3 June 2022 (UTC)[reply]

You are not overcrowding my watchlist at all. I need not watch the files, and while reviewing several files today, I realized that they did not explain their context.

Thank you for uploading more PNG renderings of SVG files. Many files have exotic tests, but there should be better support. Even obvious constructs such as e^−x² fail. I should submit some tests to both CanIUse.com and the official SVG test suites. It looks like librsvg is going backwards with interpreting switch. I think Gnome closed the issue about passing the language preferences in the command line, but I will have to check.

Today, your changes appeared on my watchlist. Three edit summaries appeared in my notifications.

Some of the tests are for SVG Translate and have no problems with rendering.

Some files include some SVG 2.0 extensions such as refX on a symbol. That translate="no" attribute is from SVG 2.0 via HTML 5 which got it from the Internationalization Tag Set. Maybe I should start using version="2.0" in those files.

I'm also coming across validation false negatives. The SVG 1.1 switch element may have a visibility presentation attribute, but the W3C validator flags the attribute as an error.

I will look over the renderings more carefully later, but a meeting is coming up.

Glrx (talk) 20:05, 3 June 2022 (UTC)[reply]

Good news

I am happy with Phab:T309426. I reported it on 28 May, and the fix should go live next week. Kudos to TheDJ. Glrx (talk) 22:37, 10 June 2022 (UTC)[reply]

The fix has gone live. Glrx (talk) 14:54, 22 June 2022 (UTC)[reply]

More good news. Phab:T271000 (about SVG Translate) has been marked "in development". Glrx (talk) 16:13, 23 June 2022 (UTC)[reply]

SVG bug workaround

Hello!

File:Africa.svg suffers from phab:T35245 according to Commons:Commons SVG Checker. Do you think you can make a workaround? Jonteemil (talk) 21:34, 31 July 2022 (UTC)[reply]

@Jonteemil: Jumping in here.

I think the simple answer is no.

Some example SVG:

<text transform="matrix(0.99947183,0,0,-1,506.354,522.846)"
         style="font-variant:normal;font-weight:normal;font-size:5.11199999px;font-family:Benguiat;-inkscape-font-specification:Benguiat-Book;writing-mode:lr-tb;fill:#000000;fill-opacity:1;fill-rule:nonzero;stroke:none"
         id="text19762"><tspan
         x="0 3.3943679 5.0302081 8.4910316 10.126872"
         y="0"
         sodipodi:role="line"
         id="tspan19764">U.A.E</tspan><tspan
         x="-141.53084 -137.95244 -134.88524 -132.02251 -128.87863 -125.40247"
         y="-59.007816"
         sodipodi:role="line"
         id="tspan19766">CYPRUS</tspan><tspan
         x="-125.05486 -123.41901 -120.24957 -116.9779 -113.60397 -110.43454"
         y="-39.934944"
         sodipodi:role="line"
         id="tspan19768">ISRAEL</tspan><tspan
         x="-99.080788 -96.422546 -92.332947 -89.061264 -85.564659 -82.190735"
         y="-31.990896"
         sodipodi:role="line"
         id="tspan19770">JORDAN</tspan><tspan
         x="-38.426903 -35.052982 -31.576824 -27.257183 -23.883265 -22.247423"
         y="-31.970448"
         sodipodi:role="line"
         id="tspan19772">KUWAIT</tspan><!-- SNIP --></text>

Some of the text wants to be conventionally spaced (e.g., "SAUDI ARABIA"). That can be achieve by just deleting all but the first x coordinate in a tspan. (That's what I would expect librsvg to be do, but it is doing something else.) However, some text (e.g., "SAHARA") wants to be spaced out ("SAHARA"). One could put each character in its own tspan, but that would make the file difficult to use in other contexts.

In the long run, I think such a tool would not be very useful. It would frustrate SVG Translate.

The appropriate fix is to get the WMF renderer to do the right thing.

Glrx (talk) 03:53, 2 August 2022 (UTC)[reply]

@Glrx: Eventhough The appropriate fix is to get the WMF renderer to do the right thing. of course is correct I think the reason to why the several workarounds exist is because the "appropriate fix" isn't that easy or fast to make, or am I wrong?Jonteemil (talk) 13:02, 2 August 2022 (UTC)[reply]

@Jonteemil:

The observation "isn't that easy or fast to make" is a sore point. Small changes have been delayed, and now the task looks huge. There are many SVG bugs that would be fixed by upgrading to the current version of librsvg. IIRC, WMF's version is about 4 years behind the current release. Of course, there are reasons. WMF needs to be deliberate and conservative because reliability is important. Initially, WMF could not upgrade to the new version because it required Rust support, something that was not in the standard operating system release. But now WMF finds itself several operating system releases behind, and the newer systems have Rust support. However, so much time has elapsed that another language that WMF depends on (Python) has been upgraded and requires WMF code base changes. In the middle of all of this chaos, the WMF developer responsible for the image scalers retired and was not replaced. Add to that WMF's desire to upgrade the server architecture. So WMF is now in a huge effort to catch up. I suspect SVG is lost in the larger mess.

The librsvg renderer has also undergone incompatible changes. There are new issues with processing multilingual SVG files.

The amount of work is not large; half a page of code. Given a recent version of Debian that supports Rust, the path is straightforward. Switch to resvg (which would give use textPath support) and modify the calling code to pass $lang as a command line argument rather than an environment variable. To retain librsvg, Gnome would need to take a $lang command line argument (something they have considered and may have already implemented). A less desirable workaround would just pass truncated langtags in the LANG environment variable (e.g., zh-Hans → zh). (There's an even better XSLT option.)

A few months ago, WMF claimed it will have a more recent version of Debian running soon.

Glrx (talk) 14:26, 2 August 2022 (UTC)[reply]

I'm wondering why this image is not affected by phab:T36947, it uses font-sizes of ~5px.

@Glrx: Thanks for answering. librsvg uses x="0" if the value in x=" is invalid, compare the SVG with this png

@Jonteemil: I added maaaany <tspan , but as Glrx pointed out this is not a good solution, but still better than path-Text (Text converted to Path).

@Jonteemil: I do not recommend to use fonts such as font-family="Sanvito", font-family="Tiepolo" font-weight="bold", font-family="Benguiat", I recommend to change the font of the pdf to one of the ones listed on meta:SVG_fonts. — Johannes Kalliauer - Talk | Contributions 15:38, 2 August 2022 (UTC)[reply]

I got married

We got engaged in Oct 2021 at the Vienna Zoo, after feeding giraffes^{[Wedding 1]}.

I married in April 2022.^{[Wedding 2]} (In Februar 2022 we decided to marry in March 2022, before I move to the US for working at M.I.T., but we both got Covid, and postponed the wedding two weeks.)

Few Photos of the wedding can be found on Instagram.

↑ Photo on Facebook. www.facebook.com. Retrieved on 2022-10-02.
↑ Verena Wachter & Dr. Johannes Kalliauer (in de-AT). Langenlois. Retrieved on 2022-10-02.

— Johannes Kalliauer - Talk | Contributions 02:58, 2 October 2022 (UTC)[reply]

Many congratulations, and best wishes on your new life in the USA. It's been a pleasure working on SVG with you. Cheers, cmɢʟee ⋅τaʟκ 12:59, 2 October 2022 (UTC)[reply]

Congratulations. The giraffe is beautiful, and I envy both of you because I've never had the opportunity to feed one. (Giraffes have an incredible circulatory system.)

The Border Cafe in Harvard Square shut down due to Covid, but Mary Chung's Suan La Chow Show is close by. Walking the Esplanade loop via Longfellow and Harvard Bridges was always peaceful. Fall is the best time in New England.

You have done good work here. Enjoy your family, your new surroundings, and good luck.

Glrx (talk) 16:21, 2 October 2022 (UTC)[reply]

Deine Meinung

war mir immer wichtig, und meist konnte ich mich anschliessen. Wenn ich gelegentlich mal was anders sah ist das ja vollkommen natürlich - es wãre seltsam wenn immer 100% Übereinstimmung bestünde.
Wenn du mal ein wenig Zeit dafür hast wüsste ich gerne deine Ansicht, ehe ich die Sache weiter verfolge.
Da hatte jemand die Idee Vorlagennamen zu internationalisieren, mit Unmengen redirects in dann natürlich doch nicht allen Sprachen.
IMHO sollten Vorlagen nicht in jeder Benutzersprache aufgerufen werden können! Es soll ein einheitlicher Aufruf erfolgen, und nicht zB die Vorlage By je nach Lust und Laune mit den redirects "von", "de", "del", "od", "fra", "ад", "কর্তৃক", "על ידי" etc.
{{User}} muss man wohl verstehen wenn man in den Commons rumtut - Utente, Gebruiker, Usario, Benutzer geht vielleicht noch - aber bei fernöstlichen oder schon bei slawischen Begriffen hätte ich meine Schwierigkeiten und müsste grossen Aufwand betreiben.
Ein "i18n/piros", "I18n/červený", "I18n/kırmızı" oder "I18n/красный" wird nicht jeder sofort als die Farbe "rot" erkennen - 'i18n/red' ist schon viel eher OMA-tauglich, und die Texte bleiben wartbar.
Ich bin der Meinung das sollte nicht gemacht werden - was meinst du, Johannes? -- sarang♥사랑 18:12, 20 March 2023 (UTC)[reply]

@Sarang: Ich fühle mich geehrt, dass du meine Meinung so wertschätzt. Dennoch hier bin ich überfragt und sehe ich als eine Stilfrage die in COM:LP/de geregelt sein sollte.

Es gibt für mich zwei legitime Sichtweisen:

Eine praktikable Sichtweise: Den Großteil der Nutzerînnen (inkl. uns zwei) wird alles in Englisch bevorzugen, als wenn jede Nutzerîn die Vorlagen in der eignen Sprache verwendet.
Wenn man aber auf Fairheit, Gleichberechtigung und Anti-Diskriminierung wert legen würde, sollte man auch auf Sprachengleichheit Wert legen und jede Sprache gleichwertig behandeln. (Bei Fotos sollte auf der Beschreibungsseite für Templates z.B. die offizielle Landessprache verwendet werden.)

Auf der Welt gibt es ca. 7000 Sprachen, weshalb die zweitere Option schwer möglich ist und kleinere Sprachversionen diskriminieren werden würden, daher sehe ich noch eine dritte (eher theoretische) Option, für mehr Sprachengerechtigkeit: Dass Esperanto statt Englisch die Basissprache auf Commons sein sollte.

Mir ist klar, dass weder du noch ich uns über Esperanto freuen würden, weil wir beide derer nicht mächtig sind. Aber jemand der nicht Englisch kann, würde sich mit Esperanto mehr willkommen heißen, weil dann ja jeder die Sprache übersetzten muss bzw. sich extra für Commons angeeignet haben muss.

Ich persönlich habe große Probleme mit rechts-nach-links-Schriften, heißt aber nicht dass ich es aus moralischen Gründen gut finden würde diese zu beschränken.

So sehr ich die idealistische Basisdemokratie in Wikimedia begrüße, könnte eine Diskussion darüber ein zeit-tot-schlagender Flame-War werden, ich versuche daher aus pragmatischen Gründen mich da herauszuhalten bzw. so weit es geht den gelebten Regeln zu folgen.

Wenn du eine fundiertere Meinung von der Commons-community haben willst, kannst du bei Commons_talk:Language_policy eine Diskussion starten.

— Johannes Kalliauer - Talk | Contributions 20:37, 20 March 2023 (UTC)[reply]

Danke, das hilft mir weiter. ich hatte es bisher nur vom praktikablen POV gesehen - dass Editieren gravierend erschwert wird, wenn es mit den redirects ausufert. Mit der Gefahr von invisiblen edits wenn jemand nur gegen einen (seinen) redirect austauscht.
Der Einwand mit Esperanto macht mich denken dass dass ein redirect, eben in eo, durchaus sinnvoll sein kann; es gibt noch andere linguas francas ausser en, vor allem es und fr, aber das Englische ist nun mal historisch der Wiki-Ursprung, und es erscheint mir sinnvoll. Ich gehe heute auf einige Wochen nach Korea, dort können viele (vor allem jüngere) en, aber meines Wissens niemand eo.
In den Commons mache ich praktisch alles, vor allem natürlich Vorlagen, in Englisch und denke dass es so verständlich ist. Aber aus der oben skizzierten redirect-Problematik werde ich mich nun auch raushalten - sollen sich andere drum kümmern -- sarang♥사랑 07:45, 21 March 2023 (UTC)[reply]

File:Flag map of the world.svg

Je voudrais vous demander si le drapeau français entre (File:Flag map of the world.svg) dans ce fichier doit être mis à jour vers la version utilisée à partir de 2020 2401:E180:8841:37E9:EF05:9A8C:C603:2B5E 05:52, 20 May 2023 (UTC)[reply]

La couleur bleue n'est pas officiellement définie.

File:Flag_of_France_(lighter_variant).svg utilise fill="#002395"
File:Flag of France (1794–1815, 1830–1974, 2020–present).svg utilise fill="#002654"
https://www.gouvernement.fr/charte/charte-graphique-les-fondamentaux/les-couleurs définit fill="#000091"

Pas de consensus => pas de changement

Veuillez discuter sur File_talk:Flag_map_of_the_world.svg

— Johannes Kalliauer - Talk | Contributions 02:54, 22 May 2023 (UTC)[reply]

SVGOMG

User TSamuel hat wieder begonnen, seine destruktiven "compressings" durchzufuhren. Kann er nicht mal eine kurze Zeit geblockt werden, um ihm zu zeigen dass sein Tun unerwunscht ist? -- sarang♥사랑 07:55, 21 May 2023 (UTC)[reply]

@Sarang:

Er hat dieses Kalenderjahr 14 SVG-Dateien die Dateigröße verringert.

Ist es legal was er macht:
- Meiner Meinung nach nein.
Gibt es festgeschriebene Regeln die er verletzt:
- Jein
- Help:SVG guidelines wurde vermutlich noch nie (auf Commons:Administrators'_noticeboard) ausjudiziert, wobei ich glaube schon, dass es vor den SVG-Leitfaden, auf dem Anschlagbrett mal etwas dazu besprochen wurde.
- Admins können nicht Experten in allem sein (Lizenzrecht, Konfliklösung, Dateiformate, SVGs, ... ) und daher könnte Commons:Administrators'_noticeboard auch nicht der geeignet Platz sein das auszudiskutieren, wenn nicht rechtzeitig SVG-Experten die Sachlage verständlich darstellen
- Help:SVG guidelines hat bewusst Graubereiche um keine Sonderfälle zu schaffen wo die guideline falsch liegen würde, was aber die Durchsetzung tw. schwer machen kann

Eine etwas philosophische Antwort von mir:

Ich war früher sehr pedantisch sich für das Gute in aller Schärfe einzusetzen, heutzutage akzeptiere ich alles was in einem gewissen Midset Sinn machen kann. Selbst mit dem gleichen Wissenstand kann man mit unterschiedlichen Prioritäten zu unterschiedlichen Schlüssen kommen.

Ich mache ein anschauliches überspitztes Beispiel, warum man manchmal am Besten ist nur zu nicken und lächen und jeden so sein zu lassen wie er ist.

Als Kommunist kann man sich fragen, ob man nicht viele Obdachlose/Arbeitslose/Kranke/Schwache form Hungertot rettet, wenn man wenige Kapitalisten umbringt.
Als Kapitalist kann man sich fragen, ob man nicht durch den Wohlstandsgewinn viele zukünftige Generationen vorm Hungertot rettet, wenn man wenige Kommunisten umbringt.

Die Schlussfolgerung die ich daraus ziehe, ist dass das Gehirn des Menschen zu beschränkt um gewisse Schlussfolgerungen ziehen zu können und der de:Bestätigungsfehler dazu führt, dass man je mehr man sich mit einer Sache beschäftigt, desto falscher man liegen kann.

Wenn mich etwas aufregt, akzeptiere ich die Situation zuerst (dass es User gibt die SVG-Dateien unbedacht verkleinern, dass die Datei unlesbar ist), bevor ich versuche etwas zu verändern. Wenn man als externer Manager hinsieht wie man das Problem in einem Computerspiel lösen würde, dann hat man (i) bessere Laune und (ii) bessere Changen etwas zu verbessern. Wenn ich etwas mache, dann mache ich es gründlich und fundiert und mir persönlich sind das ein paar SVG-Dateien nicht wert. (Wie du siehst schreibe ich auch einen viel zu langen Text für etwas viel zu unwichtiges.) Wenn ich mich in 10 Jahren frage worauf ich stolz bin und worin ich mehr Zeit investieren will, würde ich eher sagen dass meine Tanzleistung stolz bin, als dass ich stolz bin dass ich mich auf Commons mit Nutzern mit Meinungsverschiedenheiten rumgeschlagen habe, damit Commons einige leserlichere SVG-Dateien hat. So gemeinnützig zweiteres auch klingen mag, halte ich einen toleranten umgänglichen konfliktvermeidenden Umgang mit den Mitmenschen als nützlicher und über Generationen weitereichender für die Menschheitsfamilie, als wenn Commons etwas besser sortiert ist.

Da TSamuel verwarnt wurde und sich nicht einsichtig zeigt, rechtfertigt sein Verhalten meiner Meinung nach sehr klar eine Sperre, jedoch sehe ich mich auch etwas befangen.

Dennoch wenn ich TSamuel's Antwort lese, kommt für mich die Frage auf, was der Sinn von "Category:SVG_simplified_symbols" ist. Die Kategorie braucht eine Beschreibung die erklärt (i) welche Dateien hier einkategorisiert werden sollen (ii) was mit "simplified" gemeint ist (iii) warum TSamuel's Dateiverkleinerungen nicht hineinfallen (iv) was der Sinn der Kategorie ist (v) was man in der Kagegorie findet (vi) wann diese Kategorisierung für den Leser nützlich ist.

Ich mache gerne Gedankenexperimente und versuche Menschen zum (selbstständigen) Denken anzuregen, ich versuche eine Richtung vorzugeben. Selbst wenn ich Freunden voll und ganz zustimme, kontere bei Freunden tw. trotzdem mit überspitzten&vereinfachten Ansichten, damit diese selbstständig fundierte Entscheidungen treffen können und sich auch in alternative Sichtweisen hineindenken können.

PS: Ich hab einen noch einen backlog bei E-Mails und Commons/Phabricator, liegt daran, dass nächste Woche ein Sponsormeeting ist und danach US-Westküste und danach nach Europa und ich gehe in Privatwirtschaft.

— Johannes Kalliauer - Talk | Contributions 02:04, 22 May 2023 (UTC)[reply]

Nun habe ich wieder viel Zeit von dir mißbraucht - nicht direkt meine Absicht, aber immer der Fall wenn ich mich an dich wende.
Zumindest habe ich nun der Kategorie die (längst fällige) Erklärung verpasst. Sie enthielt noch einige "re_inkscaped" Symbole, die hab ich entfernt bzw. tw. reverted.
Finden lassen sich diese Kategorien recht einfach durch Eingabe von cat:svg s in das Suchfeld.

Das kann eine substantielle Änderung werden, wenn du in die Privatwirtschaft wechselst, wie ich interpretiere in Europa / ;
mit der Nebenwirkung dass Wikimedia zurückstehen müssen wird. Aber: Alles Gute dazu ! -- sarang♥사랑 07:39, 22 May 2023 (UTC)[reply]

Danke fur deine Verdeutlichung in SVG simplified symbols. Das Problem ist leider dass TSamuel, Kwamikagami & Co gar nicht in die Kategorie sehen. Trotz der Bitte "nicht mit Tools" fallen sie uber die Dateien her, und belassen alle Parameter auf der Beschreibung & Kategorisierung des vorherigen Zustandes. Naturlich ist es viel einfacher, SVGOMG laufen zu lassen, als eine Beschreibung zu aktualisieren. Fur SVGOMG braucht man nichts von Wikimedia oder von SVG zu verstehen - und glaubt dann sogar, was Sinnvolles beigetragen zu haben. -- sarang♥사랑 15:37, 22 May 2023 (UTC)[reply]

Zu einem Aspekt in deiner Mail von 16:56: ich bin selbst nicht so glucklich uber die Kurzparameter, meist noch ohne Lang-Alternative. Ich habe einige hundert andere Vorlagen neu erstellt, und sie haben i.a. deutliche, verstandliche Parameternamen. Nicht gerade allzu lang, aber so an die 6 bis 8 Zeichen; wobei es auch trotz deutlicher Namen ganz ohne Vorlagenbeschreibung schwer ist. Beim 'Igen' wird wenigstens dem Anwender vom script weitgehend erspart, sich mit den Namen auseinandersetzen zu mussen.
Die Anfange des 'Igen' liegen ca. 10 Jahre zuruck, heute wurde ich vieles anders machen (vor allem: mit LUA).
Es gibt noch andere schlimme Vorlagen die viel verwendet werden. Und dass dasselbe verschieden heisst (user, editor, author, ...) ist auch nicht gut verstandlich. Aber an Bestehendem was zu andern ist sehr, sehr schwierig. -- sarang♥사랑 16:04, 22 May 2023 (UTC)[reply]

File:Matlab icon.png

When I uploaded File:Matlab Logo.png almost 16 years ago, I did not think the official logo was below COM:TOO. That is why I chosen to just write matlab code to create similar plot, and I challenged I can slightly alter angles or shades to make it less similar. I do not like it when my uploads are deleted and this seem like safer option. I do not have strong opinion on File:Matlab icon.png, except that it is a bit redundant to the old file. One way, to determine if it is ok or not could be to nominate it for deletion or ask at Commons:Village pump/Copyright. Jarekt (talk) 16:55, 24 December 2023 (UTC)[reply]

Happy new year

Wishing you a happy 2024 cmɢʟee ⋅τaʟκ 17:28, 31 December 2023 (UTC)[reply]

@Cmglee: Thank you very much! You too. I'm so impressed by all your animated SVGs, I don't know anyone on a similar level like you. Very kind of you, thinking about me. I didn't know the code {{filepath:test.svg}} before. I think your userpage is the most impressive I've ever seen. — Johannes Kalliauer - Talk | Contributions 17:12, 1 January 2024 (UTC)[reply]

My pleasure and thank you very much for your kind compliments, Johannes. Likewise, I'm very impressed with your work with rsvg and other infrastructure.

It's a pity Wikipedia has no direct support for SVG animation, though filepath can also be used to link a thumbnail directly to the SVG, like this one.

If you ever have any requests for animated SVG, let me know and I'll see what I can do. Tschüss, cmɢʟee ⋅τaʟκ 06:10, 2 January 2024 (UTC)[reply]

Mir auch. Glrx (talk) 19:20, 2 January 2024 (UTC)[reply]

De-adminship warning

Dear JoKalliauer, I am writing to inform you that you are in danger of losing your admin rights on Commons because of inactivity.

If you want to keep your adminship, you need both to sign at Commons:Administrators/Inactivity section/Feb-Mar 2024 before 13th March (UTC), and also to make at least five further admin actions in the following six months, if you fail to do so you will automatically lose your rights.

You can read the de-admin policy at Commons:Administrators/De-adminship.

Thank you! -- CptViraj (talk) 20:47, 12 February 2024 (UTC)[reply]

Done Thank you for the note. I will try to be more admin-active — Johannes Kalliauer - Talk | Contributions 22:07, 16 February 2024 (UTC)[reply]

File:Office of Strategic Services.svg

Hi, please correct a spelling mistake in the emblem File:Office of Strategic Services.svg: it has "STRATEGIG" but should be "STRATEGIC". It might be helpful to link to a source that confirms the design, such as this. Also, I am unclear that you should claim copyright: I think it should be tagged with {{PD-USGov}}, or with a more specific tag in Category:PD-USGov license tags. Thanks, Verbcatcher (talk) 00:04, 8 March 2024 (UTC)[reply]

@Verbcatcher: The Source-Image is public domain, the vectorization needed some creative/intellectual abilities, therefore the vectorization can in this case (=how I vectorized) imho claim copyright. Anyhow, please feel free to edit the description-page as you think it is best. I don't care about any copyrights I might have on this image.

The source-image I used is not available under this link, and I do not have the time to check for an updated source.

I recommend reading https://de.wikipedia.org/wiki/Wikipedia:Grafikwerkstatt/Archiv/2017/Unerledigt#Logo_des_OSS. If you can't understand german you can use google translate: https://de-m-wikipedia-org.translate.goog/?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp&_x_tr_hist=true#Logo_des_OSS

— Johannes Kalliauer - Talk | Contributions 12:53, 8 March 2024 (UTC)[reply]

Thank you for correcting the svg file.

It is arguable to claim copyright for vectorization work. Whether this is valid would probably depends on whether the changes in the image exceed the threshold of originality, and on whether the SVG source code is hand-written or automated. There is a related discussion at Help:SVG#Copyright, but it does not give clear guidance.

I have replaced {{tl|PD-USGov}} with {{PD-USGov}}, which looked like your mistake. I added a subheading to indicate that this applies to the original design, otherwise the public domain claim would conflict with your cc-by-sa-4.0 claim. I did not find an applicable template for this, which might suggest that vectorization copyright is rarely claimed.

Regards, Verbcatcher (talk) 14:54, 8 March 2024 (UTC)[reply]

@Verbcatcher: Thanks for the link to Help:SVG#Copyright, and thanks for fixing my mistake. I changed the copyright of the vectorization from cc-by-sa-4.0 to {{self|CC0|PD-self}} based on your argumentation. — Johannes Kalliauer - Talk | Contributions 19:23, 1 April 2024 (UTC)[reply]

Problematic svgs

JoKalliauer, I have found some drawings that can't be displayed (File:Mogorjelo tlocrt.svg, File:Micevac tlocrt.svg, File:Sv mihovil preko tlocrt.svg, maybe more). I have tried tool you advise me a long time ago, but with no success. Do you have any idea what's wrong? Ma▀▄Ga 09:12, 15 August 2024 (UTC)[reply]

First file is missing inkscape namespace and is UTF-16.

Second file is missing inkscape namespace; fixed.

Third file is missing inkscape namespace; fixed.

Glrx (talk) 16:26, 15 August 2024 (UTC)[reply]

@Glrx, thank you for fixing two files. What can I do to fix the first one? Ma▀▄Ga 18:51, 15 August 2024 (UTC)[reply]

@MaGa: I think the quick fix is to revert to the previous version that used text rather than curves. (I'm biased in favor of text.) Otherwise, it is convert the file to UTF-8 and add the namespace declarations. That's simpler than it sounds. Glrx (talk) 19:18, 15 August 2024 (UTC)[reply]

@Glrx, I like text also, but rendering fonts can be very bad, that's reason I'm converting text in curves. I really don't know what happened with this files, they was correct all the time. Ma▀▄Ga 19:24, 15 August 2024 (UTC)[reply]

File:Ceska-suverenita-logo-velke.png

File:Ceska-suverenita-logo-velke.png has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that.

The file you added may soon be deleted. If you have written permission from the copyright holder, please replace the copyvio tag with {{subst:OP}} and have them send us a free license release via COM:VRT. If you disagree that the file is a copyright violation for any other reason, please replace the copyvio tag with a regular deletion request.

Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.

Afrikaans ∙ العربية ∙ asturianu ∙ azərbaycanca ∙ беларуская ∙ беларуская (тарашкевіца) ∙ български ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Zazaki ∙ Ελληνικά ∙ English ∙ español ∙ euskara ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ italiano ∙ 日本語 ∙ 한국어 ∙ Lëtzebuergesch ∙ македонски ∙ മലയാളം ∙ मराठी ∙ Bahasa Melayu ∙ Malti ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ Plattdüütsch ∙ Nederlands ∙ norsk nynorsk ∙ norsk ∙ polski ∙ português ∙ português do Brasil ∙ română ∙ русский ∙ sicilianu ∙ slovenčina ∙ slovenščina ∙ српски / srpski ∙ svenska ∙ தமிழ் ∙ тоҷикӣ ∙ ไทย ∙ Türkçe ∙ українська ∙ oʻzbekcha / ўзбекча ∙ Tiếng Việt ∙ 中文（简体） ∙ 中文（繁體） ∙ +/−

Yours sincerely, Grandmaster Huon (talk) 15:58, 5 September 2024 (UTC)[reply]

@Grandmaster Huon: Please check source: https://commons.wikimedia.org/wiki/Special:PermanentLink/332594271 including https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom&TicketNumber=2018122710003855 — Johannes Kalliauer - Talk | Contributions 05:41, 8 September 2024 (UTC)[reply]

OK, undelete it and add VRT permission. Grandmaster Huon (talk) 20:19, 8 September 2024 (UTC)[reply]

[1] Photo on Facebook. www.facebook.com. Retrieved on 2022-10-02.

[2] Verena Wachter & Dr. Johannes Kalliauer (in de-AT). Langenlois. Retrieved on 2022-10-02.

[Wedding 1]

[Wedding 2]

User talk:JoKalliauer

Contents

A barnstar for you!

Administrator

Thank you for disfaking

Die upload-Vorschau

BackgroundImage filter antialiasing pixel artifacts

Editing error in c:File:2022 Russian invasion of Ukraine.svg

If this were not so funny, I would cry

Thank you for cleaning up some of my myriad messes.

Good news

SVG bug workaround

I got married

Deine Meinung

File:Flag map of the world.svg

SVGOMG

File:Matlab icon.png

Happy new year

De-adminship warning

File:Office of Strategic Services.svg

Problematic svgs

File:Ceska-suverenita-logo-velke.png

Navigation menu

User talk:JoKalliauer

A barnstar for you!

Administrator

Thank you for disfaking

Die upload-Vorschau

BackgroundImage filter antialiasing pixel artifacts

Editing error in c:File:2022 Russian invasion of Ukraine.svg

If this were not so funny, I would cry

Thank you for cleaning up some of my myriad messes.

Good news

SVG bug workaround

I got married

Deine Meinung

File:Flag map of the world.svg

SVGOMG

File:Matlab icon.png

Happy new year

De-adminship warning

File:Office of Strategic Services.svg

Problematic svgs

File:Ceska-suverenita-logo-velke.png

Navigation menu

Search