Knaan when I get older original

User talk: JoKalliauer

Script [edit]

Hello Johannes, when I edit a lot I can easily overlook something; unfortunately occurs occasionally. Although I know that the script always need to be checked. With the 2D rotated Auflager.svg I was amazed that you categorized it as a "flag". Then I saw: the Perhelion script was trying to come up with a good suggestion for that topic to find - and was delighted to land a supposed hit in the word "Auer" ... The same thing almost happened to me with another support! Sometimes it can be so fun with our self-made AI. Good luck again! - sarang♥ 사랑 15:32, 14 August 2018 (UTC)

Is there actually a list of the abbreviations, although I've been editing for a long time I know s = d by heart, for the rest I trust the script due to a lack of knowledge. - Johannes Kalliauer - Talk | Contributions 21:45, 14 August 2018 (UTC)

Hello Johannes, now I have made the table you longed for. It is pre-sorted according to the codes. I hope you can handle this stuff better now; Perhelion and I may come up with an even better editing aid. - sarang♥ 사랑 16:29, 28 August 2018 (UTC)

Shit now I have no more excuses if I edit wrong. ;-). Thanks! - Johannes Kalliauer - Talk | Contributions 07:51, 29 August 2018 (UTC)

A barnstar for you! [Edit]

The Graphic Designer's Barnstar
For cleaning up many drawings. Ma▀▄Ga 16:26, 28 August 2018 (UTC)
Thank you! :-D
The error is not really important, since they are rendered correctly by librsvg (the Rendering-Library 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 source code of the SVG with any text editor by adding anywhere in the tag, or alternatively you could delete everything containing (f.e. or). (I did both.)
Example of original file:
<?xml version="1.0" encoding="UTF-16"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" ""><!-- Creator: CorelDRAW X8 --><svgxmlns=""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=""><gid="g3138"inkscape:transform-center-y="-23.229832"><polygonid="path3475"class="fil5"points="2626654,4004654 3005125,4004654 3005125,4030993 2626654,4030993 "inkscape:connector-curvature="0"/><polygonid="path3475_0"class="fil5"points="3383591,4004654 3005120,4004654 3005120,4030993 3383591,4030993 "inkscape:connector-curvature="0"/><polygonid="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" ""><!-- Creator: CorelDRAW X8 --><svgxmlns=""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=""xmlns:inkscape=""><gid="g3138"><polygonid="path3475"class="fil5"points="2626654,4004654 3005125,4004654 3005125,4030993 2626654,4030993 "/><polygonid="path3475_0"class="fil5"points="3383591,4004654 3005120,4004654 3005120,4030993 3383591,4030993 "/><polygonid="path3475_1"class="fil1"points="3383587,4004654 4135251,4004654 4135251,4030993 3383587,4030993 "/></g></svg>
You could use 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)
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 an 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, September 1, 2018 (UTC)

Fixing phab: T35245 in (R) -Citronellal Structural Formula V.1 1.svg [edit]

Hi. Jü is having trouble converting their files from ChemDraw to SVG. This specific problem can be solved by iteratively replacing with, but I don't know how to wrap that into a user-friendly script that runs on Mac OS. Do you happen to be familiar with Mac or do you know anyone, who is? Thanks. TilmannR (talk) 14:12, 16 March 2019 (UTC)

You (and @ Jü :) can use or should it run in terminal and / or offline?
is a nice code, I use a similar code in my code, maybe I'll change it (and name you and this URL in a comment of the source code).
@ TilmannR: I don't have Mac, therefore I can't test it and I don't know the problem. I took a short look at and And I think the options are different and there is no?
- Johannes Kalliauer - Talk | Contributions 21:31, 17 March 2019 (UTC)
@JoKalliauer: When I upload (R) -Citronellal Structural Formula V.1 1.svg to SWAB (S.vgW.orkA.roundB.ot), the "Convert to SVG" download yields a completely unmodified file.
Okay, I now know that SWAB can't handle Inkscape SVGs. Why can't it? And please display an error message or at least mention such a strong limitation on its website.
If you want to use that regex in a general purpose tool, you need to be careful about the whitespace. E.g. won't match, if is preceded by a tab or line break. It also doesn't handle comma-separated coordinates. might work, but I didn't test it.
I don't know whether Jü uses the terminal and / or whether they are working offline, but anyone who uploads images to Commons has to be online at least sometimes. :) TilmannR (talk) 00:14, 18 March 2019 (UTC)
I will take a look at it. Yesterday it worked, but on my computer it shows the line breaks differently than in my browser.
The reasion why Inkscape-SVG don't work is because of the line breaks. Sed only reads per default line-by-line. I will change the code.
- Johannes Kalliauer - Talk | Contributions 07:40, 18 March 2019 (UTC)
@TilmannR: Firefox changes the carriage return (\ r) / newline (\ n) on Windows as well on Ubuntu, therefore when I download 29-Citronellal_Structural_Formula_V.1_1.svg everything works. With wget the download seems to work, but then swab does not work. I assume the file contains carriage return as well as newline, therefore FF thinks it is Windows-formated and deletes all carriage returns without newlines, but since it was created on Mac most linebreaks are carriage returns.
However I decided to remove all carriage returns completely and replace all newlines (including following spaces) with a single space repaired, so swab (nice name ;-)) should work now even for "Inkscape SVG (* .svg)" s.
Since my Operating System / Browser seems to modify the file while downloading, can you please check if it works now?
- Johannes Kalliauer - Talk | Contributions 16:30, 18 March 2019 (UTC)
Great. It seems work now. TilmannR (talk) 18:49, 18 March 2019 (UTC)

Administrator [edit]


A welcome present for our new administrator from your colleagues ...

Congratulations, JoKalliauer! You now have administrator rights on Commons. Please take a moment to read through the Commons: Administrators page and the pages related to the watchlist (in particular Commons: Administrators' noticeboard and Commons: Deletion requests) before you start dealing with page deletions, account suspensions or changes to the page protection status or to do it yourself on the protected pages. Most of the edits made by an administrator can be undone by other administrators, with the exception of the merging of version histories, which must therefore be handled with special care.

We cordially invite you to contact us on IRC: # wikimedia-commons @ There is also a channel for Commons admins, which can be used for more sensitive topics and for coordination among admins. You may also find useful reading in the Commons: Guide to Administrator Activity.

Please check whether you have been entered in the Commons: List of administrators and the lists sorted by date or language, and if not, add your details.

I would suggest you to use new rights only in areas of your expertise or obvious cases at the 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)
Also, congratulations from me, I had never seen! Habitator terrae🌍 20:08, 23 June 2019 (UTC)
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)

Thank you for disfaking [edit]

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)

Of course, you can also lend it to worthy disfakers! How are you with your family - sarang♥ 사랑

@Sarang: Thank you very much for the BarnStar. :-)
My parents are fine, my father will be operated on again in September and they can do just fine on their own, even if we visit them almost every weekend. - Johannes Kalliauer - Talk | Contributions 18:08, 27 November 2019 (UTC)

SVG request [edit]

Hello Johannes, I could also ask in the workshop, but first you - only there if you can't: vectorize the graphic Ice Nucleation Mechanisms.png so that all texts above, left and below are either embedded or without any text. It's easy, with Inkscape or something. Unfortunately I still can't use Inkscape ... - sarang♥ 사랑 16:00, 3 February 2020 (UTC)

I decorated it: File: Ice_Nucleation_Mechanisms.svg, but now I have seen that there was already an SVG: File: Ice_Nucleation_Mechanisms_fr.svg
In addition, the PNG does not lack the approval / OTRS ticket?
Learn Inksape:
  1. de: User: JoKalliauer / WikiConWorkshop (right are links (not left / right, but links ;-)) where it is explained what you have to do)
  2. Youtube German (I looked at it, I think it's good)
  3. Youtube English (I don't know, but it looks good at first glance)
    1. Inkscape Lesson 1 - Interface and Basic Drawing
    2. Inkscape Lesson 2 - Shape Tools and Options
    3. Inkscape Lesson 3 - Fill and Stroke Settings
    4. Inkscape Lesson 4 - Groups, Levels, and Object Selection
    5. Inkscape Lesson 5 - Document Properties and Exporting PNG Images
    6. Inkscape Lesson 6 - Text and Fonts
    7. Inkscape Lesson 7 - Drawing Lines and Paths vs Objects
    8. Inkscape Lesson 8 - Free Hand Drawing Tool
    9. Inkscape Lesson 9 - Bezier Tool and Nodes
Inkscape is easy to learn in one hour (excluding installation)
- Johannes Kalliauer - Talk | Contributions 22:29, 3 February 2020 (UTC)
Thank you, Johannes. So far, my interest in mastering Inkscape & Co has been low, because I have intentionally limited myself to simple, hand-drawable graphics. I know my way around all the better!
It is with this file that Pierre_cb created this fake. There was a discussion because he deleted a number of my categorizations of his fakes and I then wanted to take care of correct vectorization; switch-internationalizable, if at all.
Thanks to your help, this is now possible, I can now expand the lyrics. And your training documents will certainly help others, I will also point this out to Pierre - I will delve into it myself when I a) have time and b) a need arises again.
In this context there are two files, Jet Stream diagram es.svg and Jet Stream diagram fr.svg; both contain incorrect translations or conversions from miles to km. I have extended the "original" Jet Stream diagram.svg to include the languages ​​es and fr with correct conversion, and changed the previous uses to the original. The two files are no longer in use and will never be used again, but can be confusing because of the incorrect values. Since there is the multilingual variant, it makes little sense to maintain the two monolingual variants, they also lack any educational or encyclopedic value. I think that's why they should go, Pierre also gives his blessing to the deletion - in this situation there is no longer a need for deletion discussion?
I hope that you have little grief around you at the moment, and look forward to further good cooperation with you - sarang♥ 사랑 07:02, 4 February 2020 (UTC)
Ice Nucleation Mechanisms.svg can now also speak French in addition to (corrected) English, and Ice Nucleation Mechanisms fr.svg has been replaced by the original and is no longer necessary; So actually no more reason to keep this failed fake - that was our intention to replace fakes and get rid of them? You can do that as mine speedy- Make a request for this - sarang♥ 사랑 09:59, 4 February 2020 (UTC)
@Sarang: Pierre's files are bad-svgs (really bad), but they are not purely fake containers as they contain real copyable / translatable text.
For me, Fake-SVG is really just an SVG that can be exported 1: 1 loss-free as a raster image (e.g. with (and is then smaller), i.e. as soon as two images are inside , or the picture has been rotated (with jpg often also at 90 ° / 180 ° / 270 °), or there is one inside, for me it is a bad-svg and no longer a fake.
Commons: Criteria for speedy deletion / de would be for me
  1. if it were a {{Duplicate}}, but it's not an exact copy, so Duplicate won't work.
  2. if the uploader agrees, the file may not be older than 7 days for Speedy.
Ice Nucleation Mechanisms.svg is unfortunately still affected by phab: T36947, even if you removed the tag. () under 20 is very often problematic, from really over 25 I am not aware of any problems. (Take a look at the thumnails in the 120px preview, the text in the legend is too long.) I have to fix that.
If I get through phab: T243893, phab: T36947 should also be fixed. But I have too little idea to be a part of the discussion.
I was with my parents on WE, everything is going so far there. The only thing is that I should finish my PhD by the end of April.
- Johannes Kalliauer - Talk | Contributions 20:02, 10 February 2020 (UTC)
Well, in the regular way, via delete discussion, these redundant files cannot be removed. I can do it differently.
And as a non-admin, I have a little more freedom of fools.
I didn't notice the phab: T36947 error, but the space is already tight at, the tighter it gets at and even more at; I would have to reformat to avoid overlapping. Your classification Fake :: Bad seems plausible to me, I will adopt it.
I wish you all the best with your title work, and that it continues to go so far with the relatives. - sarang♥ 사랑 08:09, 11 February 2020 (UTC)

User: JoKalliauer / Optimization [edit]

Tach, Jo. Would you have a problem if I went through User: JoKalliauer / Optimization and corrected some typing errors that I noticed? (And put an anchor at the beginning on the DTD line below.) - Speravir - 23:02, 26 June 2020 (UTC)

@Speravir: Yes please, I am dyslexic and I look forward to corrections, including content. ;-)
Because you're talking about DTD. Please read Help: SVG # cite_ref-noDTD_5-0 and in the reference the section "Optional doctype declarations" through:

"Beyond the specificities of (X) HTML processing, Doctype declarations in XML languages ​​are only useful to declare named entities and to facilitate the validation of documents based on DTDs. This means that in many XML languages, doctype declarations are not necessarily useful."

doctype declaration is mMn a pure source text editing (which would be forbidden in de.wikipedia, see w: de: Help: Kleine_Änderungen # Was_keine_kleinen_Änderungen_sind).
So neither inserting nor removing should be recommended to mMn, see e.g. Commons: Be_bold.
Personally, I always add a DTD if the file is valid with DTD (i.e. does not contain any editor data). But my essay should show that it is often more important to keep the editor data in order to allow easy further editing and the file is accepted for the fact that the file is invalid. If a file is damaged, I recommend inexperienced users to validate the file.
PS I am glad that someone came across this site. ;-)
- Johannes Kalliauer - Talk | Contributions
You referred me to it recently yourself , and I saved it right away. I referred to the site myself yesterday, which is why I thought of the little mistakes I had noticed.
If you want to see a few more examples with renderer errors: I just recently happened to have three in a short time that produced an error message in Firefox: Button CodeMirror active.svg, Button CodeMirror inactive.svg and Bundeswappen Österreich 2020.svg (on the latter you could Commons: Help desk # Bundeswappen Österreich are of interest where there is no longer a response from the inquirer).
- Speravir - 22:47, 27 June 2020 (UTC)
I'm very forgetful, I referred you to the page on Commons: Help_desk / Archive / 2020/05 # SVG_rendering_issue.
These are not rendering errors, but the three files mentioned are "damaged" / invalid. Special: Contributions / SVGWorkaroundBot is intended to fix rendering errors, but it can fix such XML processing errors, see the last edit of SVGWorkaroundBot.
If I upload a damaged file again, I optimize it right away, but that could also be made minimally invasive (like you) and add xmlns: inkscape = "".
In Category: Pictures_showing_a_librsvg_bug_ (overwritten_with_a_workaround) there are 545 files, most of them (guess> 500) have been bugfixed by me.
Thanks for your edit, there were several sloppiness errors inside, which I cannot blame on dyslexia.
There is a question as to whether the page should not be formally documented: Help_talk: SVG # Tidying_up_section_links_to_a_user_page. (I find the topic too controversial, too file-dependent, to be turned into a guideline.)
- Johannes Kalliauer - Talk | Contributions 20:22, 28 June 2020 (UTC)

File: Oryzalin.svg [edit]

Hello Jo, I can't use your method to cut this graphic above and below so that the edges are the same size as right and left. No matter what I am at viewbox the graphic remains square. What am I doing wrong? --Leyo 15:59, 17 July 2020 (UTC)

@Leyo: Note it doesn't say but (case sensitive), at least I made the mistake once and didn't understand it for a long time (mostly all attributes are written in lower case in svg).
As written on User_talk: Danmichaelo # I_would_like_to_expand_CropTool_with_svg-support the day before yesterday, I wrote a script when I run it in a Linux with ( and Oryzalin.svg are in the same folder as the current Terminal-Working-Direktory), so I get I
<svg viewBox="-100 500 2000 200" fill-opacity="1" xmlns:xlink="" color-rendering="auto" color-interpolation="auto" stroke="black" text-rendering="auto" stroke-linecap="square" stroke-miterlimit="10" stroke-opacity="1" shape-rendering="auto" fill="black" stroke-dasharray="none" font-weight="normal" stroke-width="1" xmlns="" font-family="'Dialog'" font-style="normal" stroke-linejoin="miter" font-size="12" stroke-dashoffset="0" image-rendering="auto">
So the SVG is widthxheight = 2000x200, where the top has also been offset by x, y = -100.1000 (i.e. 100 on the left and 1000 on the top)
Note: If you open this in Inkscape you will see the "paper size" (the 2000x200), in browsers it will be shown centered so that the whole picture is centered, so in that case the width will be decisive and the areas will also be relevant that are outside the "edge of the picture" (ie what Inkscape calls the edge of the paper). So it's best to change the browser window size, once in portrait mode to see the width and once in (extreme) landscape mode to see the height.
In order to switch off this browser factor, the best way to render the image is with Commons: Commons_SVG_Checker, alternatively, it would also be possible to write, then in browsers you will not see the image dimensions beyond that:
<svg viewBox="-100 500 2000 200" width="2000" height="200" fill-opacity="1" xmlns:xlink="" color-rendering="auto" color-interpolation="auto" stroke="black" text-rendering="auto" stroke-linecap="square" stroke-miterlimit="10" stroke-opacity="1" shape-rendering="auto" fill="black" stroke-dasharray="none" font-weight="normal" stroke-width="1" xmlns="" font-family="'Dialog'" font-style="normal" stroke-linejoin="miter" font-size="12" stroke-dashoffset="0" image-rendering="auto">
- Johannes Kalliauer - Talk | Contributions 03:59, 18 July 2020 (UTC)
So to make the picture borderless you would have to call.
<svgviewBox="32.349214 90.709473 1117.6508 811.29199"width="1117.6508"height="811.29199"fill-opacity="1"xmlns:xlink=""color-rendering="auto"color-interpolation="auto"stroke="black"text-rendering="auto"stroke-linecap="square"stroke-miterlimit="10"stroke-opacity="1"shape-rendering="auto"fill="black"stroke-dasharray="none"font-weight="normal"stroke-width="1"xmlns=""font-family="'Dialog'"font-style="normal"stroke-linejoin="miter"font-size="12"stroke-dashoffset="0"image-rendering="auto">
- Johannes Kalliauer - Talk | Contributions 04:18, 18 July 2020 (UTC)
Thank you for your detailed explanation! Nevertheless, the interaction of viewBox and width / height remains "surprising" for me (when clicking on Preview, the displayed graphic often does not change as expected). But I've now managed to make the edges evenly narrow. The edges of structural formulas should never be completely removed, as they would otherwise "stick" to the thumb frame, for example. --Leyo 07:50, 20 July 2020 (UTC)
With viewBox I would set the last two numbers to be identical to width / height, for example:
Otherwise you fit a picture in the ratio 1118x840 into a picture 1100x820 and thus with (default) the viewBox is 1091.38095238x820 and the remaining 8.61904761905 px are divided into right and left 4.30952380953
If you really want to distort the picture you have to show off.
You can find an explanation at which is graphically illustrated at ratio
I gave you the effective image dimensions: if you want to add 10 margins everywhere, for example, you have to calculate with the respective values ​​-10 -10 +20 +20. (The accuracy I give is nonsense, as you should round mMn to whole numbers, as you did.)
- Johannes Kalliauer - Talk | Contributions 19:28, 20 July 2020 (UTC)
Actually, I didn't want to have a difference between the information in the viewBox and the width / height, but otherwise I couldn't get it right. But now I have taken over your information (rounded).
As you can see, a tool for cutting SVG with a mouse would be very useful for technically limited users like me. ;-) --Leyo 09:42, 21 July 2020 (UTC)

Strange failure [edit]

Hello Johannes, because I don't really know who could be responsible for something like that, I turn to you with this interesting error. The [[File; Instruction should actually display a file, optionally in a specifiable px size. This bug doesn't do that with certain sizes, instead a kind of icon and the fileSurname displayed:


I have not yet investigated further with which files and parameters this occurs. Incorrect displays when the sizes of some SVG files are too small are known, but this is new to me. I discovered it at Small lymphocyte (4) .svg, there it is indicated by the {{Attrib}} as follows: This image includes elements that have been taken or adapted from this file: Hematopoiesis (human) diagram en.svg. Other occurrence: