User talk:TilmannR/Archive

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Hi I saw you reduced the file size of File:Preimages_of_the_circle_under_map_f(z)_=_z*z+0.25.svg very much, how did you do it? Did you have a tool vor that? (By the way you broke the file: You reduced the size of the circles and the blue points are now black.) JoKalliauer (talk) 22:18, 18 May 2018 (UTC)


Hi. Thanks for noticing the errors. After seeing the author's call for help at the Graphics Village Pump, I simply opened the file in a text editor to see what's wrong with it and edited it down to the current version with regex substitutions. Of course regexes can be a bit tricky and the older version of the file is so slow to render that I didn't check for deviations as thoroughly as I should have.

Using a WYSIWYG editor like Inkscape didn't seem appropriate due to the size and complexity of the image and I'm new to the whole SVG editing thing, so I haven't made or found any good tools yet.

Regarding the size of the circles: What are the guidelines for acceptable differences between versions of a file? Yesterday I fixed some problems with Extragalactic_Distance_Ladder.svg and while doing so removed a bunch of gradients and broken shadows to make the file more easily editable. If such changes aren't acceptable, I better revert and reupload as a new file. TilmannR (talk) 06:18, 19 May 2018 (UTC)

I had another look at Commons:Overwriting_existing_files. I must have missed the "When in doubt, [...] upload as a new file." last time I read it. TilmannR (talk) 07:12, 19 May 2018 (UTC)

thx for reducing the size. Your result is great. Could you describe the detailes of you reducing procedure ? What text editor, what patterns, ... I would like to put it on the image page at the section : "postprocessing." Thx again --Adam majewski (talk) 17:23, 19 May 2018 (UTC)
I'm glad you liked my edit. I'm new to Commons and getting this kind of feedback is quite encouraging. (The text editor I used was Notepad++[1], but that's not particularly relevant.) I don't remember each individual pattern I used, but the main culprit definitely were lines like <use xlink:href='#gpPt6' transform='translate(600.3,998.2) scale(0.45)' color='rgb(190, 190, 190)'/>. There are 12141 of those, each about 100 characters long, so approximately 1.2 MB in total. A short regex for that is e.g. <use[^>]*190, 190, 190\)'/>, but the real solution to superfluous elements is to not generate them at all. Apparently it's possible to avoid generating points by setting their point_type to -1. If I was more familiar with Maxima, I'd fix the script, but I'm not, so I won't. TilmannR (talk) 21:03, 19 May 2018 (UTC)
In general if I would optimise a SVG I would not accept such visiual differences, as in your edit.
Compare:
I compare the previews, because the SVG can be rendered in every browser differently
  1. You changed in the headline two spaces to one space (most likely on purpose)
  2. In the original file all four kinds of circles in the legend (the same in the picture) were rendered bigger
  3. The Gray area (from the gray lines) near the blue circle are brighter/smaller, as if the lines would be thinner.
In this specific case it is in my opinion ok, because the uploader ask for a file-size-reduction. (otherwise not)
I have this opinion, because I got some reverts: File:Liberty_Bell_icon.svg#filehistory File:Carte_occitan_limousin.svg#filehistory File:Empty_bucket.svg#filehistory
JoKalliauer (talk) 09:44, 20 May 2018 (UTC)
Hmmm... Interesting. Seems like the main reason for the reverts was the removal of width and height attributes.
Sarang (the user, who did the reverts) appears to be fine with minor changes in visual appearance. Compare File:Circle_area_Monte_Carlo_integration.svg before and after Sarang's edit.
The text in the summary of Liberty_Bell_icon.svg confuses me:
"It would be very easy to edit this file to W3C-valid within a few seconds, but this is of no use, the mere formal errors don't disturb.
Please let it just as it is, don't upload any new version".
Why would preserving the current file be more important than fixing the errors?
Does this mean that minor improvements to SVG files are generally discouraged?
E.g. reducing the size of the Empty_bucket.svg from 100 KB to 400 Bytes could be considered irrelevant and therefore undesirable.
On the other hand Category:SVG_simplification_techniques and Category:SVG_files_to_be_drawn_by_hand seem to imply that we're supposed to code golf SVGs to minimum size.
TilmannR (talk) 12:56, 20 May 2018 (UTC)
Thanks for mentioning Circle area Monte Carlo integration.svg, so I would say now your edits are great, also it has some minor visible changes.
The "confusing text", was added by Sarang: https://commons.wikimedia.org/w/index.php?title=File%3ALiberty_Bell_icon.svg&type=revision&diff=265455143&oldid=265454526 Sarang added it after Sarang reverted my edit. I had a short discussion about it User_talk:Sarang/Archive/2017#W3C_valid on Sarang's Talkpage (in German). Sarang said that not all W3C-errors are problematic, and I think this file should show a high number of W3C-errors on purpose. (I think reuploading also needs some CPU-time for the servers.) Problematic errors, which won't render correctly, or which are not editable should be fixed, but otherwise there seems to be no reason to fix them.
Generally editing files not by the original author should have a better reason, than just minor file reduction, or removing unproblematic errors.
I think Empty bucket.svg should show on purpose the difference between Tool-made-svg and Text-editor-made-svg (compare with Full bucket.svg).
I think it is case dependent, and there are no guidelines for optimisation, therefore everyone has different onions on it. Generally SVG simplification techniques and SVG files to be drawn by hand should be used to have easily editable files.
I think the examples might not have been the best, maybe File:Dojikko2.3.svg is a better example of what might get reverted (see Perhelions's edits). (My edits did some visible changes on purpose, because the file was corrupt and some elements didn't render before.) Previews above 600px might won't work in all previous versions.
Generally if you are unsure: Sarang has more experience than I have, maybe ask Sarang. But as said before you did a great work. I just wanted to explain why did't improve more in my edit. JoKalliauer (talk) 14:37, 20 May 2018 (UTC)

regex

Thx for describing how you have used regex.Can you describe what was the idea ?

If I understand correctly :

  • finding the most frequent pattern : "There are 12141 of those, each about 100 characters long, so approximately 1.2 MB in total"
  • and remove or group them : "real solution to superfluous elements is to not generate them at all."

Is it general method for all svg ?


I have make the section about size of svg file in help. You can add/change some things.

TIA. --Adam majewski (talk) 17:22, 21 May 2018 (UTC)

"Can you describe what was the idea ?" What exactly do you want to know? Could you please rephrase the question.
"Is it general method for all svg ?" No, it's not useful for all SVGs. Removing elements only makes sense, when those elements don't contribute to the image. For example: File:Dashed_line_p6.svg is unnecessarily large. In fact it could be more than 200 times smaller! None of its elements is inherently superfluous though, so deleting them would destroy the image, but the dashed strokes are encoded inefficiently. Such a problem cannot be solved with regexes, it cannot be solved with simple optimizers. It's a problem that requires a certain kind of intelligence.
I don't think I have anything to add to the "Reducing the file size" section, but personally I wouldn't recommend the removal of code formatting. Line breaks and indentation make SVGs much more readable and they usually have a negligible impact on file size and rendering time.
TilmannR (talk) 22:33, 21 May 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 16:59, 4 March 2019 (UTC)

Platonic solid STL licenses

Indeed - there is nothing creative in this work, so I changed the licence as you suggested. Polimerek (talk) 22:38, 3 June 2018 (UTC)

This section was archived on a request by: TilmannR (talk) 17:00, 4 March 2019 (UTC)

Autopatroller

Hi, I gave you the autopatrol right. Thank you for your contributions. Regards, Yann (talk) 19:14, 27 August 2018 (UTC)

This section was archived on a request by: TilmannR (talk) 17:00, 4 March 2019 (UTC)

Kepler–Poinsot STL

Is File:Great icosahedron.stl the only STL file of a Kepler–Poinsot polyhedron you have uploaded, or did I miss the other three? If you have uploaded them under different names, I suggest creating redirects. If not, it would be great if you do. Greetings, Watchduck (quack) 11:48, 9 September 2018 (UTC)

@Watchduck: I had uploaded all stellations of the icosahedron and exactly one of them happens to also be a Kepler–Poinsot polyhedron. I just uploaded the dodecahedron stellations (and as a bonus the stellated octahedron). Thanks for the suggestion. TilmannR (talk) 23:51, 9 September 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Warning removed

@Fma12: @Yann: Hi! "USD Bitonto Calcio.svg" was originally uploaded by AltHis_En (Log: [2]). I merely fixed a rendering issue and validation errors. Marking me as a copyright violator for this seems unfair. I don't remember the file having a deletion request or missing a license. (I cannot view the info of a deleted file. Maybe I overlooked something? If I did, please tell me, so I can avoid future mistakes.) Being held responsible for somebody else's copyright violation would severely discourage me from fixing broken files in the future. (Honestly, I probably wouldn't complain, if I wasn't so proud of keeping a spotless record throughout all my work for the Illustration Workshop. And thank you very much for doing all this administrative work. ) TilmannR (talk) 21:26, 20 September 2018 (UTC)
Fine, I removed the warning. Regards, Yann (talk) 04:05, 21 September 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Not accepting request anymore?

@TilmannR: Why do you never accept my requests again in the Illustration workshop?--Jeromi Mikhael (talk) 08:43, 24 October 2018 (UTC)

@Jeromi Mikhael: I'm very sorry.
  • I don't have as much time for illustration requests as I used to.
  • Your requests tend to take a lot of time and effort.
  • I have already accepted more request from you than from any other user.
It is quite unfortunate that the other graphists seem to be disinterested in your requests, but there's not much I can do about that. TilmannR (talk) 10:26, 24 October 2018 (UTC)
Ok. Thanks. No problem. --Jeromi Mikhael (talk) 10:27, 24 October 2018 (UTC)
By the way, does my last two files uploaded good enough?--Jeromi Mikhael (talk) 14:33, 26 October 2018 (UTC)
@Jeromi Mikhael: Coat of arms of North Ossetian ASSR.svg and Coat of arms of the North Ossetian ASSR (1940-1978).svg? They look fine to me.
Please note that the copyright of the design of a coat of arms and the copyright of the specific image that depicts a coat of arms are different things. The design is often non-copyrightable, but the image might be. In this case the original file had the cc-by-sa-3.0 license. You should honor that by naming Pianist as one of the authors and adding the appropriate license tag. TilmannR (talk) 16:29, 26 October 2018 (UTC)
Noted. Thanks--Jeromi Mikhael (talk) 16:39, 26 October 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Source of derivative work is not properly indicated: File:Wildpark Müden Logo.svg

[Warning removed.] Ronhjones  (Talk) 23:49, 9 November 2018 (UTC)

@Ronhjones: Wildpark Müden has no contributions other than the upload. They didn't even add their logo to the relevant article. I predict that they won't fix the source & author and the image will be deleted.
Would you recommend that I continue to fix broken SVGs like this one or should I leave them alone? Getting my talk page flooded with warnings isn't fun. TilmannR (talk) 03:24, 10 November 2018 (UTC)
I can only suggest to see if you think the image is valid enough to stay. An obvious logo with an "own work" is probably doomed. If it's not an original file that you upload, I would remove any warning with an edit summery like "original file not my upload". It's the script that is used for the placing of banners on the file page, also does the warning automatically. Ronhjones  (Talk) 11:28, 10 November 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

SVG with embedded raster graphics

I wanted to highlight the difference between embedded-PNG and plain-PNG: embedded for PNG-24, PNG-32, PNG-48, PNG-64 and plain for PNG-8 (palette variant: 2-256 colors). Correct me if I'm wrong. This clarification for future image uploads. Waiting for your reply. Hello!--Grasso Luigi (talk) 10:56, 16 November 2018 (UTC)

Hello, I would like to know your opinion on the new upload image in File: Sec-butyl-nitrite-2D-dimensions.svg to have a pure vector SVG. So to understand the template {{BadSVG}} and also to disable. I would appreciate your answer. Thank you.--Grasso Luigi (talk) 16:50, 20 November 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Request

Can you do my 2 last requests at the Commons Illustration Workshop? I think it is not hard.--Jeromi Mikhael (talk) 08:32, 23 November 2018 (UTC)

This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Thanks for your motivation!

Thanks for your motivation! Finally, I can make (eh....) one logo of a political party! Please help me to fix the sun! Upload over it if you have done.--Jeromi Mikhael (talk) 09:07, 26 November 2018 (UTC)

@Jeromi Mikhael: It's great to see how much progress you've made. I replaced the sun with a circle and filled the hands with white. I used a clip path to make sure that everything effortlessly fits into the red circle. TilmannR (talk) 15:26, 26 November 2018 (UTC)
Please also help to fix this one! I make it based on [3], but real pictures confuse me. Is the shield behind the word "Тошкент" red or white? I need your opinion. One more. The building on top of the sun can be seen in a more detail here.--Jeromi Mikhael (talk) 07:55, 28 November 2018 (UTC)
@Jeromi Mikhael: "надпись "ТОШКЕНТ" на белом фоне" [4] TilmannR (talk) 08:10, 28 November 2018 (UTC)
@Jeromi Mikhael: The building can be seen in even more detail here. :) TilmannR (talk) 08:29, 28 November 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Lion rampant question

Hi TilmannR. Please find response from Celbusro here. It would appear he created this svg lion rampant. Regards Newm30 (talk) 10:17, 27 November 2018 (UTC)

@Newm30: Thanks. I've adjusted the authorship information of my derivative work. It would be nice, if Bruce of Skelton arms.svg mentioned the source of the lion in it's summary. That way people who reuse it won't mistakenly attribute it to you. TilmannR (talk) 11:21, 27 November 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

SVG image thumb not visible

Hi TilmannR. I have seen that you fixed the problem with File:Illu_mouth_new_eu.svg. Could you tell me how you fixed it? My friend Koldo Biguri has had the same problem with File:Illu01 head neck eu.svg, and I haven't been able to fix it. --Xabier Armendaritz (talk) 13:06, 29 November 2018 (UTC)

@Xabier Armendaritz: I couldn't find out what the problem was and just recreated the image in Inkscape. But your message motivated me to give it another try and I just found out how to fix it: Wikipedia:SVG_help#Missing_embedded_JPEG_images. Change the MIME type from "jpg" to "jpeg". (My original fix only works accidentally, because I was using a PNG instead of a JPG.) TilmannR (talk) 20:20, 29 November 2018 (UTC)
Thank you very much for your explanation! --Xabier Armendaritz (talk) 22:09, 29 November 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Thank you for your minimum SVG vectorial. I had a question: why does the black rectangle appear in the middle of the files (pure vectorial but not as minimal) uploaded by me? Is it necessary to change which part of the source SVG to avoid it? Waiting for your reply. --Grasso Luigi (talk) 09:17, 5 December 2018 (UTC)

@Grasso Luigi: The problem is the "flowed text" created by Inkscape. Read Help:SVG#Black_rectangle_(Flowed_Text_bug) for more information. TilmannR (talk) 09:28, 5 December 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Thank, you! — D Y O L F 77[Talk] 15:47, 19 December 2018 (UTC)

@Dyolf77: I'm glad I could help. You can find information about the black rectangles and many other SVG rendering quirks on Help:SVG#Black_rectangle_(Flowed_Text_bug). TilmannR (talk) 15:55, 19 December 2018 (UTC)
Reading it . — D Y O L F 77[Talk] 16:00, 19 December 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Sprache

sprichst du Deutsch? do you speak german? --Mrmw (talk) 21:13, 21 December 2018 (UTC)

@Mrmw: Sure. Do you want me to translate something? TilmannR (talk) 09:31, 22 December 2018 (UTC)
@TilmannR: nein, ich hab aber einige fragen - von welcher wikipedia kommst du? von der deutschen? wieso hast du dort weder benutzer- noch diskussionsseite?
ich habe mehr durch zufall dateien von dir gefunden:
beide sind gut gezeichnet und mich würde interessieren mit welchem programm du sie gezeichnet hast?
die wichtigste frage ist aber, wieso diese beiden (und vermutlich noch andere) von dir erstellten dateien in den artikeln nicht ersetzt sind? nicht mal in den deutschen artikeln
--Mrmw (talk) 13:46, 22 December 2018 (UTC)
@Mrmw: Ich komme tatsächlich von keiner Wikipedia. An meinen Statistiken lässt sich leicht ablesen, dass ich fast ausschließlich auf den Commons tätig bin. Ich habe Freude am Erstellen von Vektorgrafiken, nicht so viel Freude am Schreiben von Artikeln. Ich habe keine Diskussionsseite im Wiki, weil dort noch niemand mit mir diskutiert hat. Ich habe keine Benutzerseite, weil ich nicht glaube, dass ich eine brauche. (Und so ein Redlink in der Signatur sieht doch auch schick aus. :) ) Meine Grafiken sind üblicherweise in Inkscape erstellt, mit SVGOMG vereinfacht und im Texteditor per Hand weiter optimiert. Große Ausnahme sind Overwrites von kaputten SVGs, die sich in wenigen Sekunden allein im Texteditor fixen lassen. Meine Dateien sind nicht immer verwendet, weil ich nicht aufdringlich erscheinen möchte, und weil das Verwenden von Grafiken (im Gegensatz zum Erstellen von Grafiken) etwas ist, was die Autoren auch selbst hinbekommen, falls sie meine Grafiken für hinreichend hochwertig erachten. (Dafür gebe ich mir auch Mühe mit der Kategorisierung und dem Setzen von {{Vva}}-Templates.) TilmannR (talk) 14:41, 22 December 2018 (UTC)
@TilmannR: danke für deine antwort, beeindruckend
vva ist mir geläufig - aber ist es nicht so, dass ein autor von sich aus hinter die grafik sehen muss (kontrollieren) ob eine vektor-grafik verfügbar ist? verstehe mich nicht falsch, ich finde es nur schade, dass deine arbeit, die ich gut finde, nicht gleich zur anwendung kommt - sowas ist doch schade
ich selbst benutze auch inkscape und habe zum teil auch schon mit svgomg vereinfacht - nur bin ich dabei recht unsicher, welche vereinfachungen am sinnvollsten zu verwenden sind
zum teil waren im w3c-check nach der vereinfachung fehler im test - wie testest du deine svgs bevor du sie hochlädst? es gibt wohl auch fehler/warnungen die man ignorieren kann?
gern wüsste ich auch mehr darüber wie man per hand am sinnvollsten die svgs editiert und auf fehlersuche geht - wie du eben schreibst im texteditor - hast du dazu literatur oder tutorials im netz die du empfehlen kannst? wie hast du dir das wissen angeeignet? try and error?
--Mrmw (talk) 16:45, 22 December 2018 (UTC)
@Mrmw: Uff! Viele Fragen...
Ja, Autoren werden nicht automatisch über Vektorversionen informiert, wenn sie nicht gerade die Rastergrafik in ihrer Watchlist haben.
Du kannst meine Bilder gerne in Artikel einfügen, wenn dir das wichtig ist.
Zu SVGOMG: Die Vereinfachungen, die die Dateigröße am meisten beeinflussen ohne das Aussehen des Bildes zu beeinflussen, sind am wichtigsten. Ich schalte immer "Compare gzipped" aus um die tatsächliche Dateigröße zu sehen und schalte "Prettify markup" und "Sort attrs" ein, damit die Datei im Texteditor lesbarer wird. Ansonsten sind die Standardeinstellungen schon ganz in Ordnung.
Zum W3C Validator: SVGOMG lässt Dinge, die es nicht erkennt, einfach in der Datei um nichts kaputt zu machen. Dazu gehören dann manchmal auch Dinge, die der W3C Validator nicht erkennt.
Inzwischen checke ich meine Dateien kaum noch mit dem W3C Validator. Wenn man sich lange und intensiv mit SVG auseinandersetzt, ist relativ klar was "erlaubt" ist und was nicht.
Letztendlich sind alle Validationsfehler irrelevant, solange man sich sicher ist, dass das SVG trotzdem richtig gerendert wird. Wenn man sich nicht sicher ist (oder aus Ehrgeiz null Fehler möchte) sind natürlich alle Validationsfehler wichtig, aber alle Warnungen trotzdem irrelevant.
Wie man SVGs am sinnvollsten per Hand editiert: Sorge erst dafür, dass die Datei klein und lesbar wird (also z.B. SVGOMG mit "Prettify markup" verwenden) und nutze dann dein Verständnis über den Aufbau von SVGs um zu erreichen was du erreichen möchtest. Mehr habe ich dazu eigentlich nicht zu sagen. Um mehr über SVGs zu lernen, einfach googlen. MDN ist eine recht zuverlässige Quelle. w3schools geht auch. Und auf jeden Fall Help:SVG und Wikipedia:SVG_help durchlesen, denn manchmal werden auch korrekte SVGs nicht korrekt gerendert.
TilmannR (talk) 18:09, 22 December 2018 (UTC)

(talk page stalker)@TilmannR: Ich glaube du meintest nicht die Commons-Statistiken sondern die Globalen: sulutil:TilmannR. Für reine Texteditor-fixes würde ich dir User_talk:Rillke/SVGedit.js#Install raten, man erspart sich das herunter und hinaufladen, sondern bearbeitet direkt im Browser (und man kann auch Highlightning aktivieren).

@Mrmw: Es gibt Fehler und Warnungen die man absichtlich drinnen lasst. Beispielsweise: Ein Hilfsgitter oder Hilfslinien sind laut W3C-SVG1.1-DTD invalid. Sie zu entfernen verändert zwar nicht das Rendering, aber der nächste der bearbeitet hat diese Elemente nicht mehr, daher sollte man das mMn drinnen lassen. User:Glrx spricht sich auf User_talk:JoKalliauer#Re:_if_you_scrubb_a_svg_please_make_the_file_valid_on_your_own dafür aus, dass aria-label (Wenn ein Text zu Flächen konvertiert wird, dass der Textbuchstaben noch als Text vorhanden sind), und data-name (Bennenung von Elementen, dass man es wiederfindet) erhalten bleiben, auch wenn beide zu Fehlern führen. Ich bin oft zu perfektionistisch und lösche zu viele Fehler.

Es gibt auch valide SVG 1.2 und valide SVG 2.0 Dateien, die bei SVG 1.1 immer invalide sind. Beispielsweise vector effect ist ein zusätzliches Attribut, dieses Attribut soll erhalten bleiben auch wenn es zu Category:SVG_files_with_multiple_W3C-errors führt.

@TilmannR: Es gibt auch wichtige Warnungen, beispielweise wenn man eine Datei ohne DoctypeDefinition (DTD) schreibt kommt die Meldung: Consider adding a lang attribute to the html start tag to declare the language of this document., wenn man DTD gemäß User:Quibik/Cleaning_up_SVG_files_manually hinzufügt, dann wird die Datei iA. "strenger" geprüft, hier wird auch darauf hingewießen, wenn type="text/css fehlt.

Bei SVGO (bzw SVGOMG) habe ich schon einige Fehler gemeldet: github.com/svgo/issues SVGO/SVGOMG wird aber nicht mehr aktiv gewartet. Früher habe ich SVGOMG verwendet mit folgenden Einstellungen de:Benutzer:JoKalliauer/Inkscape-SVG-Speichern#Wie_komprimiere_ich_die_Dateigröße, mitlerweile verwerwende ich SVGO mit verschiedenen Batchskripten (konvertiere CSS?, entferne Rastergrafiken?, erhalte Bemerkungen (Kommentrare, ID-Namen,..)?, Metadaten? )

Bei Wikipedia-SVG-Hilfeseiten finde ich de:Wikipedia:Probleme_mit_SVGs am besten.

 — Johannes Kalliauer - Talk | Contributions 14:27, 29 December 2018 (UTC)

@JoKalliauer: Dankeschön. Wie immer sehr präzise, gründlich und hilfreich. TilmannR (talk) 21:36, 29 December 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Black Box Issue

Hello!

I saw your edit on the Australian 2016 map, first off, thank you so much for fixing that, so quickly after I uploaded it as well! I've been having issues with saving my files as SVG ever since I got a new laptop, and its causing corruption issues and black boxes in some of my older maps.

How did you go and fix the issue exactly? I'd be curious to know so I can prevent further situations!— Preceding unsigned comment added by DrRandomFactor (talk • contribs)

@DrRandomFactor: Hi. A lot of the broken SVGs on Commons have the same problem: The program, which turns the SVGs into PNG thumbnails, ignores all <style> tags, which don't have the type="text/css" attribute. Technically that attribute isn't necessary. It's just one of the quirks of the particular version of librsvg used by Wikimedia. You can fix the problem by opening the SVG in a text editor and adding the attribute manually. The SVG editing program you're using probably has a setting to save SVGs entirely without CSS, which would also solve the problem. You can learn more about various SVG rendering problems by reading Help:SVG and Wikipedia:SVG_help. (Please remember to sign your posts with ~~~~.) TilmannR (talk) 11:57, 29 December 2018 (UTC)
@DrRandomFactor: TilmannR is correct, but this issue can be detected without understanding SVG-code:
 — Johannes Kalliauer - Talk | Contributions 13:41, 29 December 2018 (UTC)
@JoKalliauer: That's interesting. Based on Help:SVG#cite_note-2 I had assumed that a missing type attribute wasn't a validation error, because it MUST default to "text/css" anyway. Recommending the Validator and Checker to newcomers is definitely a good idea. Thanks for reminding me. TilmannR (talk) 19:43, 29 December 2018 (UTC)
@TilmannR: You are right, that's why I said you are correct, and I know thats a (in my opinion helpful) Bug of Validator: Accoring to https://www.w3.org/TR/SVG11/styling.html#StyleElementTypeAttribute (which is as far as I know the official guideline): If a ‘type’ is not provided, the value of ‘contentStyleType’ on the ‘svg’ element shall be used, which in turn defaults to "text/css". Therfore not specifying should be allowed, but maybe because it might lead to problems (like Rendering with librsvg), they gave out an Error, with a wrong explantation, that beginners know what to change. But if you check the same file without &doctype=SVG+1.1: W3C takes the result of validator.nu and clames it as its own, which does not mention anything (related to style): https://validator.w3.org/check?uri=https ... (Simple_Map).svg
 — Johannes Kalliauer - Talk | Contributions 23:02, 29 December 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

AutVec

I want to explain the reason why the Template {{AutVec}} should be preferable be used, as Special:Diff/332708641 you did.

User:Sarang told me on User_talk:Sarang/Archive/2017#Autor-Feld: Im Author= sollten tatsächlich nur Autorangaben stehen, alles andere stört bei der maschinellen Auswertung; das Auswerteprogramm verkraftet die verschiedenen Schreibweisen.

specifying who did what should not be used for example:

is according to User:Sarang undesirable. (See: Special:Diff/252409016/264584457 for this example.)

I don't know why it should be computerreadable, maybe there are bots to find possible copyright-violation depending on the author, or for statistiks. @Sarang: Can you explain why the autorfield should be "maschinenlesbar"?

 — Johannes Kalliauer - Talk | Contributions 00:18, 30 December 2018 (UTC)

@JoKalliauer: I was using something like *derivative work: [[User:TilmannR]], because that's what derivativeFX generates, but apparently that tool is obsolete. {{AutVec}} is an easy case, once you've been made aware of its existence. (Is there an Introduction to Templates or Template Overview page somewhere? E.g. I only found out about FakeSVG this Thursday, because you used it in the Illustration Workshop. That's a rather inefficient way to learn.) It'd be nice if there was a similar template for arbitrarily many authors with arbitrary roles.
I'm not a fan of the summary of Poutre definitions de.svg. The authorship information is all over the place: You're the "author", Bbanerje and Cdang are "sources", you and Bbanerje made "modifications" ("Changed french to english", "Changed english to german"). It would be very difficult to write a program, which understands all of this. Therefore the authorship information is arguably not machine readable. Is it really correct to not list Bbanerje and Cdang under "author"? I've been searching through the guidelines and policies and didn't find much about this issue. In theory you could add the names of other authors as a parameter to the license template (e.g. {{Cc-by-sa-4.0|Example Name}}) or you could add a {{Credit line}} to the image information, neither of which appear to be commonly used. Is there no official recommendation this? TilmannR (talk) 03:14, 30 December 2018 (UTC)
I now changed the Autor according to scientific papers: I named all authors of them starting from the most important author to the last important author, that should be botreadable.
I don't think there is a guideline, since everyone uses as they like and it not a copyright-violation, and therefore it is "no problem", to make it differently, also different Wikipedians have a different point of view.
I have some Templates collected on my userpage. There is a official Collection: Commons:Templates (maybe {{FakeSVG}} should be added)
But you won't find {{FakeSVG}} anywhere explained, since it is quite new. I whised it in June this year, that Administrators know that there is something foul with FakeSVG, and Sarang created it, see User_talk:Sarang/Archive/2018#BadSVG_in_FakeSVG_und_sinnvoll_eingebundes_PNG_trennen? for details. It is unclear if FakeSVG should be deleted, see User_talk:Perhelion/Archive/2018#Löschpolitik_von_Bad_SVG.
But you could find templates like {{FakeSVG}} in Category:SVG_marker_templates or Category:Image_cleanup_templates.
 — Johannes Kalliauer - Talk | Contributions 09:09, 30 December 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Language

As somebody already asked earlier #Sprache, naming the language skills helps others to contact you in the correct language. I personally would prefer Esperanto per default on Commons, also I cannot speak a Esperanto at all, since commons is a multilingual project, and should be fair between languages. (Just my personal (idealistic) point of view.)

I think Commons:Guide_to_adminship#Initial_setup (de) might be a good guideline also for not administrators, which recommends to use language- babels (you could also use them on your talk-page). There are many Admins without babel. (And I think it is also there right to keep the language-skills private.)

Since you are (one of) the most active User on Commons:Graphic_Lab/Illustration_workshop, this might be helpful for other. (But don't feel pushed to do anything, just a side remark, because I don't know if you prefer English/German.)

 — Johannes Kalliauer - Talk | Contributions 00:18, 30 December 2018 (UTC)

@JoKalliauer: That's the main problem with constructed languages: Nobody knows how to use them. And if any constructed language was used as much as a natural language, it would probably evolve, shift and adapt like a natural language, so you'd end up with multiple natural dialects of your constructed language.
I'm aware of Babel, but since I prefer to use English, and since this preference should be obvious to anyone, who ever read anything I've written on Commons (except for that one section in German), I don't think I'd get anything out of using Babel. I also don't like the idea of putting a numeric label on my language proficiency. In every language I know there are things that are easy to talk about and things that are difficult to express. Distinguishing between a native language and a native-level second language is just silly. TilmannR (talk) 03:39, 30 December 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

local illustration workshops

FYI:

Except the Workshops on Commons (Commons:Graphic_Lab/Illustration_workshop,Commons:Graphics_village_pump) there are also local Workshops f.e. de:Wikipedia:Grafikwerkstatt, en:Wikipedia:Graphics Lab/Illustration workshop, en:Wikipedia:SVG_help.

PS:You know the librsvg-bugs very well, and you are a good drawer. (Thanks for all your works they are great.) In Category:Pictures_showing_a_librsvg_bug_(unsolved) are several files I cannot get fixed, maybe you want to take a look at it.

You seem to be very engaged, therefore I just want to inform you about things in you area of interest that should be done.

 — Johannes Kalliauer - Talk | Contributions 00:18, 30 December 2018 (UTC)

@JoKalliauer: I'm aware of the other workshops. Is there a way to receive notifications for new requests? Checking all of those sites, only to find that nobody requested anything, is mildly annoying. Am I really supposed to fix those files? Aren't they needed to demonstrate the bugs? Or is there a different category for the broken SVGs that aren't supposed to get fixed? I vaguely remember something like that. TilmannR (talk) 04:04, 30 December 2018 (UTC)
how to recive Mails when new request are comming
You could add the related sites to your watchlist and change the Preferences in de:Special:Preferences and en:Special:Preferences, that you recive an E-Mail when the site get changed after your last visit.
I know it is not the best solution.
I "can't" use it in de.wikipedia since I am watching to many pages, therfore I use the Watchlist (Beobachtungsliste).
All files containing a librsvg-Bug should be in Pictures showing a librsvg bug
If the file is reduced to a minimal example it can be used for Pictures demonstrating a librsvg bug, then it should be Pictures showing a librsvg bug (SVG replaced), since you should know how it should look like.
But if it is a well known bug with enought examples and file is a file should be used in articles it should be Pictures showing a librsvg bug (overwritten with a workaround).
Files in Pictures showing a librsvg bug (unsolved) are SVGs without workaround (only PNG or SVGs with reduced features). Finding a workaround will be helpful for other pictures that have the same bug. If the librsvg is needed (f.e. Pictures demonstrating a librsvg bug) you should upload to a new file, otherwise you can overwrite it.
So in Generall all files should be in Pictures showing a librsvg bug (SVG replaced) or in Pictures showing a librsvg bug (overwritten with a workaround).
There are few exeptions:
 — Johannes Kalliauer - Talk | Contributions 10:32, 30 December 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Prism...

Hi. Just upload your version on top of File:Prism, frustum, prismatoid and scutoid.svg. Glrx (talk) 17:00, 3 January 2019 (UTC)

@Glrx: Okay. TilmannR (talk) 17:05, 3 January 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Bro......

@TilmannR: Fail. I can't recreate the sun's rays and wheat, also the gear.--Jeromi Mikhael (talk) 11:27, 4 January 2019 (UTC)
@Jeromi Mikhael: ✓ Done. TilmannR (talk) 22:54, 4 January 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Ancient Orient Basemap

Hi TilmannR, thanks a lot for your attempted fix in this file.

My end goal is a gallery of the situations in 2600 BCE, 2500 BCE, ... 400 BCE, 300 BCE; according to Middle Chronology - but for that, I need a master file. This here is it, a container with 24 maps in one.

However, it looks like the layering was seriously disturbed in your fixing attempt: I have each century in its own layer, 18th century BCE was the one that was currently put on visible. After your edit, all elements of the visible layers were in a group, per layer; all elements of the invisible layers where gone; there was no evidence of any layer structure left. So while the fix worked on the surface; it made things worse.

What you call "flowed text" is really disturbing and I'd like to edit it out of the file eventually. I have tried several approaches, but it seems once I put a text beyond a font-size of ~20, the Commons-Display turns it into an ugly box very unlike the Inkscape view. Loaded directly in my browsers just doesn't display these same texts at all. So, what's the trick behind that and how do I achieve "regular text" instead of "flowed text"? I'd appreciate your hint so I can apply it there. --Enyavar (talk) 14:13, 10 January 2019 (UTC)

@Enyavar: Sorry for breaking your file. I should have been more careful during optimization. In Inkscape's "Text" menu there's a "Convert to Text" option, which converts flowed text to regular text. TilmannR (talk) 15:02, 10 January 2019 (UTC)
Thank you for your helpful tips; I converted the texts following your hint and now they look fine! Also, don't be sorry for nothing - there was no harm done. I have kept the local files; the upload is mostly to have a version history if I manage to break or delete my offline files. Also, my file description might have suggested that this is already a completed work.
Once I produced a final version, I think it might be prudent to delete the working-versions of the master file. Do you agree? --Enyavar (talk) 20:47, 10 January 2019 (UTC)
@Enyavar: I have no strong opinion on the matter, but let me play devil's advocate:
  • The amount of storage taken up by the files is negligible in the grand scheme of things.
  • The works-in-progress document how your images were made, which is nice.
  • The time that an administrator would take to read and execute your deletion request could be spent on deleting harmful files instead.
TilmannR (talk) 05:21, 11 January 2019 (UTC)
@Enyavar: Sorry for reuploading! I did not see that you already uploaded it on your own.  — Johannes Kalliauer - Talk | Contributions 10:16, 12 January 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Fake SVG tag

Tilmann, you put a FakeSVG notice on my file about the "Supreme Isosceles Trigon". I was having trouble keeping the text aligned with the geometric construction so, in Inkscape, I converted the image into a bitmap (Inkscape has a command which does that). The conversion seems to have solved the text alignment problem. Should I have used some other solution for the text alignment problem? Scott Gregory Beach (talk) 14:19, 16 January 2019 (UTC)

(talk page stalker)
@Scott Gregory Beach: You might want to check your files on Commons:Commons_SVG_Checker then you will get the error:
This means <tspan x="2914 3100">ab</tspan> should be replaced with <tspan x="2914">ab</tspan> or with <tspan x="2914">a</tspan><tspan x="3100">b</tspan>
You might should reupload File:Supreme_Isosceles_Trigon.svg as original SVG, and TilmannR or I will fix it.
 — Johannes Kalliauer - Talk | Contributions 17:34, 16 January 2019 (UTC)
Thank you Johannes. I will try to fix the problem in the way that you have recommended. Scott Gregory Beach (talk) 17:44, 16 January 2019 (UTC)
Johannes (and Tilmann), I was not able to fix the problems with the original version of the file. I recreated the file as a PDF and then I uploaded that PDF file; see https://upload.wikimedia.org/wikipedia/commons/0/0d/Supreme_Isosceles_Trigon.pdf The PDF file is much smaller than the original SVG file. Please delete the original SVG file. Scott Gregory Beach (talk) 01:54, 17 January 2019 (UTC)
@Scott Gregory Beach: An optimized SVG (1312 bytes) is actually quite a bit smaller than that PDF (20967 bytes). TilmannR (talk) 04:59, 17 January 2019 (UTC)
Tilmann, You changed the triangle corners into perfect miter joints. Thank you. That looks great! Scott Gregory Beach (talk) 15:07, 17 January 2019 (UTC)
@Scott Gregory Beach: You're welcome. TilmannR (talk) 18:17, 17 January 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Need help on fixing map

Hello!

Thank you for fixing the 2003 Scotland Election map I uploaded today! I also uploaded another one for 1999, and that one uploaded with the colours intact but it messed up the spacing on the ridings and the map looks wonky now as a result. Would it be possible for you to take one of the earlier uploads and fix it?

https://commons.wikimedia.org/wiki/File:Scotland_general_election_1999_-_Results_by_Constituency.svg

Also, how exactly does one go about fixing these? Illustrator always makes my maps look like this when I upload and its annoying! Is there a step-by-step on how to fix this? I know there is code involved, but Im garbage at that!

Thank you so much — Preceding unsigned comment added by DrRandomFactor (talk • contribs)

@DrRandomFactor: Hi. Simply open the SVG in a text editor, look for <style> (it's usually near the beginning of the file) and replace it with <style type="text/css">. You can read more about SVG rendering quirks on the SVG Help page. I believe Illustrator has an option for saving SVGs without CSS, which would also fix the problem. You can check whether your SVG will render correctly by using the Commons SVG Checker.
And please sign your posts on talk pages with ~~~~. TilmannR (talk) 11:40, 25 January 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

BANDIERA DELLA GIOVINE ITALIA.SVG

THANK YOU FOR FIX IT (AND FOR PREVIOUS INFORMATIONS ABOUT FIXING OPERATIONS: "<style type="text/css">", ...)

CIAO!!! FDRMRZUSA (talk)

@FDRMRZUSA: You're welcome. TilmannR (talk) 20:52, 25 January 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Thank-you for File:Strouhal_de_corps_2D,_Blevins_et_autres.svg

thanks, dear TilmannR, for having changed my file so that the texts appear. I wonder what mistake I made in Inkscape (with which I'm starting) ... Regards, Bernard de Go Mars (talk) 20:52, 27 January 2019 (UTC)

@Bernard de Go Mars: Hi. The problem was flowed text. You can convert it to regular text with the "Convert to Text" option in Inkscape's "Text" menu. TilmannR (talk) 02:00, 28 January 2019 (UTC)
Hello TilmannR! Thank you for this tip! Obviously, after converting to text, you have to get the text to put it back in place (especially for the vertical text that disappears from the screen). Thanks again for the link! Another thing I'm wondering is how to make a multilanguage svg image (like we can place multilanguage notes with annotator). That's my goal, but I do not know if it's possible ... Regards, Bernard de Go Mars (talk) 10:32, 28 January 2019 (UTC)
@Bernard de Go Mars: You can make a multilingual SVG by using the <switch> tag.
More info: Commons:Translation_possible/Learn_more#Multiple_translations_within_one_SVG_file.
Example: Prism, frustum, prismatoid and scutoid.svg.
I don't know an easy way to create switch tags with Inkscape. You might have to create them by editing the SVG in a text editor. TilmannR (talk) 11:43, 28 January 2019 (UTC)
Thank you for your answer. I did some tests with the Switch; but in fact I do not know where to place the text between switches; according to https://tools.wmflabs.org/svgcheck/index.php, there are a lot of errors and nothing is displayed ... We must understand that we, non-computer scientists, are disabled people ... Sincerely, Bernard de Go Mars (talk) 14:17, 28 January 2019 (UTC)

@Bernard de Go Mars: Here's an example from Prism, frustum, prismatoid and scutoid.svg:

<switch transform="translate(877.5 78)">
  <text systemLanguage="ast">prismatoide</text>
  <text systemLanguage="ca" x="-20">prismatoide</text>
  <text systemLanguage="de">Prismatoid</text>
  <text systemLanguage="en">prismatoid</text>
  <text systemLanguage="es,pt" x="-20">prismatoide</text>
  <text systemLanguage="fr" x="-20">prismatoïde</text>
  <text systemLanguage="it" x="-20">prismatoide</text>
  <text systemLanguage="ms">prismatoid</text>
  <text systemLanguage="nl">prismatoïde</text>
  <text systemLanguage="pl">pryzmatoid</text>
  <text systemLanguage="ru">призматоид</text>
  <text systemLanguage="zh">拟柱体</text>
  <text>prismatoid</text>
</switch>

As you can see, you can place text elements with systemLanguage attributes anywhere between <switch> and </switch>. If you upload your image, I can tell you exactly why it doesn't get displayed correctly. TilmannR (talk) 14:38, 28 January 2019 (UTC)

Thanks for your answer. But, as I wrote (as a disabled person), I dont know the place where I must put this code. I made a first step, but Wikimedia Commons refuse my file. You may download it (even as text) on my Fluid Mechanics site : http://perso.numericable.fr/gomars2/aero/Strouhal_de_corps_2D,_Blevins_et_autresWikiCommonsConverti%20en%20texte%20av%20test%20traduction.svg
I believe there is a lot of errors in that first step. Regards, Bernard de Go Mars (talk) 16:45, 28 January 2019 (UTC)
@Bernard de Go Mars: The problem is in line 74 to line 86: There are a <text> element and two <tspan> elements, which never terminate. Every <text> must have a matching </text> and every <tspan> a matching </tspan>, just like any opening parenthesis in a mathematical expression needs a matching closing parenthesis.
I added <switch> elements to Strouhal de corps 2D, Blevins et autres.svg, so it should be easy to translate now. TilmannR (talk) 18:57, 28 January 2019 (UTC)
Great. I'm reviewing my code and I'm translating! (I do not know where the lack of parity of <text> and <tspan> came from) (but I tinker so much that it is not surprising ... See you later ... Regards, Bernard de Go Mars (talk) 20:52, 28 January 2019 (UTC)
II downloaded the new version. There is an error but I think I'll get there! Thanking you, Bernard de Go Mars (talk) 21:16, 28 January 2019 (UTC)
Thank you very much, dear TilmannR, for your precious and fast help. This is how Wikipedia is big !! Regards, Bernard de Go Mars (talk) 21:36, 28 January 2019 (UTC)
Hello, TilmannR! Lost in my coding prowess, I did not notice that you had improved the design of my sections. This shows that you are a master of SVG and the result is much better. But there is a small problem with the green "profile" of the top. His curious leading edge did not come from a drawing error on my part. You will see in the file http://perso.numericable.fr/gomars2/aero/strouhal_sections_non_circ_blevins1999.png that this form (of aspect ratio 5) is indeed such that I had drawn it. I have no more information on this section than this drawing. As this graph is meant to be universal, I hope you can correct the shape of this "profile" (the others are very good) Note that there is no urgency ... Regards, and thanking you again for your nice contributions, Bernard de Go Mars (talk) 13:53, 29 January 2019 (UTC)
@Bernard de Go Mars: ✓ Done. TilmannR (talk) 20:06, 29 January 2019 (UTC)
Thank you so much. It's a lot of work for you, but the result is very attractive.
We see the form in question also on page 125/234 of this text: https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19950017797.pdf but it is not better described, so we can be satisfied! Regards, Bernard de Go Mars (talk) 21:13, 29 January 2019 (UTC)
TilmannR is a god. Glrx (talk) 21:51, 29 January 2019 (UTC)
:) TilmannR (talk) 21:55, 29 January 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Emblem of Ukrainian SSR

Hi Tilmann. I was wondering can you vectorize this emblem, until i found a modern graphic representation. I was hoping that you could made that, but with several adjustions (e.g. the shield and the wheat ears should be wider, the ribbon should be white). Inscription : ПРОЛЕТАРИИ ВСЕХ СТРАН, СОЕДИНЯЙТЕСЬ!, ПРОЛЕТАРІ ВСІХ КРАЇН, ЄДНАЙТЕСЯ! Thanks.--Jeromi Mikhael (talk) 01:08, 2 February 2019 (UTC)
@Jeromi Mikhael: ✓ Done TilmannR (talk) 16:26, 2 February 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Thanks for fixing my mess!

I tried to dash off a quick svg with Inkscape, failed to fix the flowed test, and noticed only once I'd uploaded it that it was a mess. I was going to upload a fixed version today, only to discover you'd beaten me to it, not ten hours after the original upload. It's things like this that make editing collaboratively a pleasure. Thank you very much! HLHJ (talk) 03:08, 2 February 2019 (UTC)

@HLHJ: You're welcome. TilmannR (talk) 16:27, 2 February 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)

Replace white background from svg files by transparent background

Could you recommend a simple method for a user of Mac OS 13 and Mac OS 14? Best regards, --Jue (talk) 18:29, 8 February 2019 (UTC)

@: I don't use Mac OS, but apparently there's a Mac version of Inkscape: Just select the background rectangle and delete it. If it's part of a group, you can double click the group to step into it. (Assuming that Mac has double clicks. I dunno. Use Google, if necessary.) You might need to step into groups multiple times, if the background is in a group in a group in a group.
If you don't consider installing a WYSIWYG SVG editor a "simple method": SVGs are just XML files. You can open them in your favorite text editor, figure out which node corresponds to the background, and delete it. If you want to change a lot of files, you can write a regex, which matches everything that looks like a background, and replace those matches with nothing. Such a regex might look like <[^>]*fill:(#ffffff|rgb\(100%,100%,100%\))[^>]*>. It just means "look for a < followed by arbitrarily many characters that aren't > followed by fill: followed by either #ffffff or rgb(100%,100%,100%) followed by arbitrarily many characters that aren't > followed by >". Note that this assumes that all white objects belong to the background, have self-terminating tags, and have their color specified in a style attribute as opposed to a fill attribute. In the case of Wikipedia:Grafikwerkstatt#Hintergrund_bei_SVG-Strukturformeln_entfernen all these assumptions were true. TilmannR (talk) 08:46, 9 February 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 17:04, 4 March 2019 (UTC)
File:Flag of Malaysia (vertical).svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Huntster (t @ c) 04:09, 24 February 2019 (UTC)

This section was archived on a request by: TilmannR (talk) 17:08, 4 March 2019 (UTC)

Thanks

Thanks for uploading that SVG of the LA bike share logo. I'm still pretty new to graphics editing - I tried using an online SVG converter to convert the original PNG file of the logo to an SVG, but that didn't seem to work. Thanks again for your help, and hopefully I can learn how to create SVG files on my own in the future. ECTran71 (talk) 07:49, 26 October 2018 (UTC)

You're welcome. I recommend starting off by familiarizing yourself with your tools. Open up Inkscape (or whichever program you're planning to use) and go through every single button and menu you can see. Just experiment and try to understand what they are there for. You should also consider using optimizers like SVGOMG to reduce the file size and clean up some of the superfluous junk that SVG editors tend to generate. Once your SVG file is optimized, it becomes much much easier to edit it "by hand" in a text editor, which is sometimes necessary to circumvent rendering errors or to make very precise changes that would be more time-consuming to do in a WYSIWYG editor. Additional info: Help:SVG. TilmannR (talk) 08:32, 26 October 2018 (UTC)
This section was archived on a request by: TilmannR (talk) 09:34, 8 March 2019 (UTC)

fixing librsvgbugs

I noticed you fixed several files with "Added type="text/css" to <style>" or flowRoot .

How do you find such files? Do you use a bot?

 — Johannes Kalliauer - Talk | Contributions 11:52, 10 February 2019 (UTC)

@JoKalliauer: The Gallery of new files can be filtered by media type and the rate of SVG uploads is usually quite low. TilmannR (talk) 12:57, 10 February 2019 (UTC)
Is it possilbe to filter by size?
How did you find out that File:THU_logo.svg has a missing type="text/css"?
 — Johannes Kalliauer - Talk | Contributions 09:14, 3 March 2019 (UTC)
Logos are much more likely to be missing type="text/css" than other SVGs (presumably because they are just copied from their source instead of being created specifically for the Commons). So when I see one that is completely black, doesn't have "black" in its name, and looks like there should be some color in it, I view it directly in the browser. E.g. Laudamotion.svg is just a black rectangle with black "audamotion" text. What kind of company would use a black rectangle as it's logo? Sometimes you can see the hairline cracks between elements of different colors like in Dapp Life logo.svg.
In theory I could write a bot that automatically downloads all new SVG thumbnails, filters out the completely black ones, downloads their SVGs, searches for <style>, fixes and overwrites it, but I don't feel sufficiently motivated to do so. TilmannR (talk) 11:03, 3 March 2019 (UTC)
Do you know is it possible to search for new svg above 3MB? [5]  — Johannes Kalliauer - Talk | Contributions 14:02, 3 March 2019 (UTC)
@JoKalliauer: [6] Search for filetype:svg filesize:>3072 and append &sort=last_edit_desc to the URL. mw:Help:CirrusSearch TilmannR (talk) 14:46, 3 March 2019 (UTC)
@JoKalliauer: Apparently &sort=last_edit_desc doesn't show most recent uploads, but most recent edits to a file's page. &sort=create_timestamp_desc might be what you're looking for. TilmannR (talk) 15:26, 3 March 2019 (UTC)
@JoKalliauer: I found something hilarious: RTVE Testcard.svg. Have a look at its source, but do not try to render the SVG. :) TilmannR (talk) 23:01, 3 March 2019 (UTC)
You maybe know Large SVG files, some can be compressed (f.e. File:E8out96g16.svg 72MB->5MB), but files with many <circle cann't (except compressing as svgz). There is a similar picture: File:1_42_polytope_7-cube.svg ( 483.840lines and 7.855 circle ) I merged all lines to one path, to reduce filesize, but librsvg seem to not like such long path-data and fails (see history)
I think this RTVE Testcard.svg should be rendered by librsvg and then the PNG should be traced to svg
 — Johannes Kalliauer - Talk | Contributions 17:57, 4 March 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 19:57, 10 March 2019 (UTC)

removing FlowRoot

You often convert FlowRoot to text, I know how it works with

But for File:Wikipedia_article-creation-2_ml.svg they did not work properly. Therfore I want to ask how you convert flowRoot2text?

 — Johannes Kalliauer - Talk | Contributions 21:31, 28 February 2019 (UTC)

@JoKalliauer: Ha ha! That's an excellent question. I had lots of fun with this particular file. :)
I used Inkscape's GUI, which unfortunately converts flowed text in such a way that the resulting regular text has to be left-aligned in order to be in the correct position. It's not really the correct position, when you take librsvg's text rendering quirks into consideration, but I didn't have the patience to fix that.
One of the flowRoots contains three different flowParas. I guess that that's where both Inkscape and your regex fail. If I remember correctly, I used Extensions > Text > Split text... to turn that into individual lines of text.
All in all I feel terrible about the job I did on that image, but at least it's presumably legible now. Of course I don't actually know whether the text is correct, because I don't speak മലയാളം. Thanks to STC19 we'll get to see plenty of "fun" SVGs over the next month. TilmannR (talk) 22:10, 28 February 2019 (UTC)
Thank you for the answer. Actually I had a different problem with Inkscape GUI: Converting changed the fontsize to ~12px (smaller). I now retried and the font-size was constant (just replaced as you said), therfore preprozessing with scour or with svgo, (most likely) leaded to the wrong behaviour in Inkscape (normally preprozessing with optimizer make Inkscapes behaviour better).  — Johannes Kalliauer - Talk | Contributions 07:42, 1 March 2019 (UTC)
@JoKalliauer: Map solar system.svg is a tough one. 225 texts, many of which are transformed, centered, multi-line flowed text. Fixing this by hand is possible, but way too tedious even for me. Maybe we need to write a more sophisticated script that actually calculates the correct positions? TilmannR (talk) 12:17, 3 March 2019 (UTC)
  1. My script only works
    • for text-anchor="start" therefore the text will be replaced for text-anchor="middle".
    • single <flowPara
  2. inkscape ./${file}f.svg --verb=EditSelectAll --verb=ObjectFlowtextToText --verb=FileSave --verb=FileClose --verb=FileQuit works for all flowRoots that can be converted by Inkscape, but as soon as one flowRoot cannot be converted inkscape fails completely. https://bugs.launchpad.net/inkscape/+bug/1748725
 — Johannes Kalliauer - Talk | Contributions 13:21, 3 March 2019 (UTC)
In Inkscape 1.0 this should work with batch-processing, even if some flowRoots are hidden: https://gitlab.com/inkscape/inkscape/issues/120
I compiled 1.0alpha (50f63d05be, 2019-03-10) so from now on I might be able to convert flowRoots using Inkscape. (But I didn't try till now)  — Johannes Kalliauer - Talk | Contributions 21:04, 11 March 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 21:04, 11 March 2019 (UTC)

Fake

Thanks for your notice on File:Welcome_to_Hatillo.svg and another one I made. I'll have to read up on this before I uploaded any other .svg files. Now I'm wondering if all my svg files have been fake. --Level C (talk) 14:56, 10 March 2019 (UTC)

(talk page stalker)
@Level C: All your svg-files are fake and should not be uploaded as svg
 — Johannes Kalliauer - Talk | Contributions 16:32, 10 March 2019 (UTC)
Okay. Now I know.--Level C (talk) 19:11, 10 March 2019 (UTC)
And this one too? https://en.wikipedia.org/wiki/File:7th_World_Scout_Jamboree.svg --Level C (talk) 20:38, 10 March 2019 (UTC)
@Level C: Yes. If you open that file in a text editor, you'll see that this "SVG" consists entirely of a JPEG image. It would have been better, if this image had been uploaded as an actual JPEG file instead. TilmannR (talk) 20:42, 10 March 2019 (UTC)
Would you agree that I should ask these files be deleted?--Level C (talk) 20:46, 10 March 2019 (UTC)
@Level C: As far as I know, being a fake SVG is not a sufficient reason for deletion. But if you upload a JPEG version of the file, the fake SVG can be speedy-deleted as an inferior duplicate. TilmannR (talk) 20:54, 10 March 2019 (UTC)
Okay I'll do that.--Level C (talk) 23:15, 10 March 2019 (UTC)
@Level C: There is no rule how to handle fake-Svgs and different admins will have different opinions on that.
I would distinglish between two cases:
  1. If the file should be vectorized like File:AibonitoFlag.svg, some say you should keep this file and wait till someone vectorizes it properly. (There are different opinons on that.)
  2. If the file can't be vectorized like File:Welcome_to_Hatillo.svg, I don't see any sence keeping the svg
User:Level C since you are the uploader you might decide whatever you prefer.
 — Johannes Kalliauer - Talk | Contributions 20:43, 11 March 2019 (UTC)
I'm with you (I follow). Today I was thinking I would try to learn more about .svg and 'vectorizing' and then reupload proper files. If I can't learn it then I'll delete those that can't be vectorized. Thanks.--Level C (talk) 22:03, 11 March 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 21:53, 26 March 2019 (UTC)
File:Emblema Buenos Aires 2018 youth olympic games.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

186.125.68.9 01:50, 15 October 2018 (UTC)

This section was archived on a request by: TilmannR (talk) 08:56, 4 May 2019 (UTC)

Hi Tilmann

Thanks very much for designing the logos for FindingGLAMs, we've decided to go with number 7. Could you email me your address (J.Cummings@UNESCO.org), we would like to send you a thank you. John Cummings (talk) 13:38, 14 March 2019 (UTC)

@John Cummings: Hi. I uploaded a clean, CC0-licensed version of number 7 to FindingGLAMs logo.svg. Please tell me, if you need any modifications or variations. TilmannR (talk) 16:06, 14 March 2019 (UTC)
Great, thanks :) John Cummings (talk) 17:03, 14 March 2019 (UTC)
@John Cummings and Axel Pettersson (WMSE): Hi. The package arrived today. What a pleasant surprise! Thank you very much. :) TilmannR (talk) 11:10, 8 May 2019 (UTC)
This section was archived on a request by: TilmannR (talk) 04:55, 21 May 2019 (UTC)

The Great Sethahedron.svg copyright changed

Tilmann: I found your message about The Great Sethahedron.svg. I changed the copyright to "public domain" as you requested. You asked, "Could you give me its vertex coordinates?" I do not have those coordinates. A brief video about TGS is posted on YouTube at The Great Sethahedron. Seth was my great grandfather and that is why the name TGS includes "Great". Scott Gregory Beach (talk) 22:10, 16 February 2019 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 03:16, 16 July 2020 (UTC)

Mars elevation STLs

Moved from User_talk:Cmglee

Hi. I noticed that Mars elevation.stl is not quite optimal.

  1. The data is "planetocentric", so I don't believe that using a "WGS84 flattening factor" is actually correct. I'm not 100% sure though.
  2. If you look at a smoothly shaded version of the file, it becomes obvious that the positions of the peaks of your little pyramids aren't correct.
View Mars_elevation.stl  on viewstl.com

I uploaded Mars elevation 2.stl yesterday. It's not quite finished, but I already like it a lot. It's generated via an embarrassingly brute-force method: I use a normalized subdivided Deltoidal icositetrahedron as a base mesh, which leads to more uniform triangle sizes than using a normalized subdivided cube. Then I took nearest-neighbor-interpolated (i.e. not at all interpolated) altitude samples from megt90n000fb.img for a 207.4 MB STL. Finally I decimated the file to a tenth of its original size in Blender. Originally I intended to use an adaptive subdivision approach, but decimation (while being extremely slow and memory intensive) gives excellent results, so I don't feel motivated to do that much additional programming. My texture coordinate calculation seems to be off by one, which causes a small hole in the south pole. A "south hole", if you will. I'm thinking of doing iterated subdivision and decimation to reach an even better mesh. And I should probably use a smarter sampling method for the altitudes.

View Mars_elevation_2.stl  on viewstl.com

TilmannR (talk) 13:09, 24 March 2019 (UTC)

Hi @TilmannR: , Great that you managed to improve on my model; I like it a lot too. I'm no expert at STL or planetary models, and didn't know Blender can optimise STL files – that's a great resource. If I understand correctly, triangulated irregular networks are far more efficient with polygons. Are you familiar with their use in 3D modelling?
I also don't fully understand what you mean by "the positions of the peaks of your little pyramids". Can you please elaborate?
The "more interesting" side of Mars
P.S. Just a minor nitpick: would you mind turning the planet around (keeping the equator horizontal) so that Tharsis and Valles Marineris are visible in the thumbnail, as on the right? Thanks! cmɢʟee ⋅τaʟκ 13:32, 26 March 2019 (UTC)
@Cmglee: Hi. Let's continue the conversation over here. I still don't receive any pings from your talk page.
  • Yes, Blender is a surprisingly powerful tool. One of the most successful open source projects of them all.
  • As far as I can tell "triangulated irregular network" is just geography jargon for "triangle mesh". So, yeah, using an arbitrary triangle mesh is more efficient than using a regular grid, because a grid puts unnecessarily small triangles in smooth regions of the planet and it fails to put vertices at the very edge of sharp cliffs or at the very tip of sharp peaks.
  • By "little pyramids" I mean what you called "subdivide facets with local minima/maxima" in the file history. The center points of these subdivided facets end up far away from where they should be. This is particularly noticeable in the corners of the top and bottom face of the cube when smooth shading is applied, because it makes some triangles face towards the planet, which causes dark lighting artifacts.
  • I'd prefer, if there was a way to control the camera parameters of STL thumbnails, but I guess adjusting the planet's orientation is the way to go for now.
  • I'll create a new Earth and Moon once I've found a more efficient way to create these meshes. If I haven't come up with a better method by Sunday, I'll use the "Blender decimation method" again. TilmannR (talk) 21:29, 26 March 2019 (UTC)
My plan to iteratively subdivide and decimate in order get a better mesh didn't quite work out. The rough parts of the planet require a huge amount of geometry in order to be represented accurately, which leaves only very sparse geometry for the smooth parts and that just doesn't look very good. TilmannR (talk) 03:52, 27 March 2019 (UTC)
Got your ping (wonder why you don't get mine...) Anyway, thanks for trying. If Blender automatically does the equivalent of TIN, perhaps it's simpler just to use Blender for that. By the way, I've since found a better DEM for Earth: the ETOPO1 dataset cmɢʟee ⋅τaʟκ 13:53, 27 March 2019 (UTC)
Thank you so much for uploading File:Earth_dry_elevation_2.stl and File:Moon_elevation_2.stl and rotating File:Mars_elevation_2.stl. They are much more detailed than mine and are simply stunning! Earth is an example where Blender's optimising may be suboptimal though: it loses the faint coastlines visible in mine, such as north of Australia, that makes it easier to identify countries. If only it's possible to tell Blender to weight the coastlines...
And sorry I'm nitpicking again, but would you mind rotating the globe as you did for Mars to show a more interesting thumbnail? I'll leave what to show to you (though I'm partial to showing both the Himalayas and Marianas Trench myself). Thanks in advance!
Lastly, I read that STL unofficially supports a colour for each polygon, but haven't found any viewers that support this. This is something which put me off making more STL models, as they all end up some bland grey. If colour and preferably other material properties like specularity, opacity and reflectivity were supported, I'd be tempted to add more to my list. Cheers, cmɢʟee ⋅τaʟκ 22:38, 27 March 2019 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 03:16, 16 July 2020 (UTC)

WAM logo in Slovak

Hi TilmannR, I saw that you created WAM logo in Malay and I wanted to ask how did you change the handwriting. I want to make Slovak version of logo with "ÁZIJSKÝ MESIAC" instead of "ASIAN MONTH" and I wrote to 林立云 who wrote the original one if he would be able to make Slovak name but he didn't reply. If it would be possible for you, would you be please able to make the Slovak version?

As I said, "ASIAN MONTH" should be changed to "ÁZIJSKÝ MESIAC" and the "WIKIPEDIA" to "WIKIPÉDIE". The order should be reversed, therefore "ÁZIJSKÝ MESIAC" should be first and "WIKIPÉDIE" below.

If you cannot do it, it is okay, I can still wait if he replies but I wanted to speed things up a bit so I can prepare this year's edition of WAM.

Thanks, --Luky001 (talk) 16:00, 4 June 2019 (UTC)

@Luky001: I copied most of the letters from the original image. The "L" and the "U" in "BULAN" are just slightly modified versions of the "T" and the "M" in "MONTH". If I remember correctly, I made the "B" out of two copies of the "O". I don't have any experience in creating calligraphy from scratch, so I recommend waiting for 林立云 to reply.
Or you could make a request at the Illustration workshop. TilmannR (talk) 18:32, 4 June 2019 (UTC)
@Luky001: I am extremely busy these months. I will reply your email and write for you in two weeks. 林立云
@Li-Yun Lin: So?--Luky001 (talk) 06:20, 1 July 2019 (UTC)

@TilmannR: Hi, I have the handwritings from Li-Yun Lin, could you please send me an email (via Email this user) so I can send them to you? I don't want to upload them to Commons since those files shouldn't be here permanently and they are not my work. --Luky001 (talk) 11:17, 19 July 2019 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 03:16, 16 July 2020 (UTC)

Request for wireframe globe

Hi TilmannR,

Further to our correspondence about planetary STL models, I wonder if I can employ your Blender skills to create a wireframe globe based on File:Earth_dry_elevation_2.stl similar to http://grabcad.com/library/earth-globe except that

  1. Land masses have exaggerated raised relief (perhaps thickened about 1 mm for structural integrity) and
  2. Gridlines have 3 thicknesses: 10° multiples are about 1 mm, 30° multiples about 2 mm and 90° multiples about 3 mm.

I'd like to 3D-print a physical model in which I can install lights to illustrate azimuthal projections (File:Comparison_azimuthal_projections.svg), similar to http://imaginary.org/es/node/1254 .

Thanks in advance,
cmɢʟee ⋅τaʟκ 21:25, 25 October 2019 (UTC)

@Cmglee: Hi! I ran into multiple problems:
  • Any islands that aren't touching the grid will be unprintable. Generating support structures by hand would be tedious. Especially Tasmania and various parts of Southeast Asia are problematic.
  • Can your 3D printing software take the union of multiple intersecting parts? Blender's Boolean operations are too unstable.
  • The mesh currently has a radius of approximately 64 arbitrary length units. Unless you give me a conversion factor between arbitrary units and millimeters, it's mathematically impossible for me to complete this task. ;-)
  • Turns out that not every place with an elevation below 0 is underwater. And some places are temporarily wet/dry depending on the tides. Shall I use File:NASA_bathymetric_world_map.jpg or something else?
TilmannR (talk) 22:21, 26 October 2019 (UTC)
Thanks for your very quick response! You raised many good points I haven't thought about, especially the first. I haven't done 3D printing myself; thought I'd send it to a printing service. I'll get back to you after thinking about how to resolve the issues. Thanks again, cmɢʟee ⋅τaʟκ 14:39, 27 October 2019 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 03:16, 16 July 2020 (UTC)

librsvgBug pattern

I would like to sovle phab:T20463 in File:Surface_Tension_Diagram_Buoyancy.svg (on my own).

I know you solved the librsvgBug relating pattern on small thumbs somehow with scaling. Can you link an example? (I know you did it at some immage(s), but I would be quite slow finding it.)

Or can you tell me what to change?

 — Johannes Kalliauer - Talk | Contributions 11:59, 1 March 2020 (UTC)

@JoKalliauer: Oops. I should have read your message more carefully. I already uploaded a fixed version. Sorry.
The problem seems to be that the rasterization fails, when the size of a single tile of the pattern is smaller than one pixel.
The solution is to increase the size of the tiles by manually repeating them (e.g. using two stripes in the pattern definition instead of one).
File:Ducktales2017Logo.svg for example has sixteen circles in the pattern (four clones of a group of four circles), when a single circle would have theoretically been enough.
TilmannR (talk) 07:07, 2 March 2020 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 03:16, 16 July 2020 (UTC)

Hi Tilmann, do you feel like making an STL version of this object? It's a rather obscure representation of this graph, but I think it looks interesting. (And it should be easy to make.) The coordinates and colors I used are in this file. A matching STL of the concertina cube would also be nice. (The coordinates are here.) Greetings, Watchduck (quack) 12:06, 13 June 2020 (UTC)

@Watchduck: Sorry for the delay. I've been quite inactive and for some reason didn't get a mail, when you left the message.
TilmannR (talk) 03:12, 16 July 2020 (UTC)
Danke. In grau ist das Baum-Gebilde natürlich etwas unübersichtlich. Ließe sich das mit den Farben so umsetzen, wie es in dem verlinkten Bild zu sehen ist? Grüße, Tilman mit sechs Buchstaben a.k.a. Watchduck (quack) 19:12, 16 July 2020 (UTC)
@Watchduck: An dem Grau lässt sich leider nichts ändern. Das einzige unterstützte 3D Dateiformat ist STL, welches keinen einheitlichen Standard für Farbinformationen besitzt. Grüße, Tilmann mit sieben Buchstaben aka TilmannR (talk) 08:57, 23 July 2020 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 06:17, 18 September 2020 (UTC)

Flag alterations

@TilmannR: Hello, and sorry for the intrusion, but since you've worked on flag-related files on WC before, I was wondering if you'd be able to help with the improvement of a certain two SVG flag files that I think could do with some adjustments? Snow Lion Fenian (talk) 15:29, 17 July 2020 (UTC)

@Snow Lion Fenian: Unfortunately I'm quite busy these days and do not have time for requests. TilmannR (talk) 08:59, 23 July 2020 (UTC)
@Snow Lion Fenian: can you specify which kind of improvements or which SVGs? (If its fast I would help)  — Johannes Kalliauer - Talk | Contributions 17:40, 23 July 2020 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 06:17, 18 September 2020 (UTC)

I say that the edition you made in Periodic_table, good SVG.svg It was wrong, Elements 95, 96, 97 and 98 exist in nature even if it is by reactions in uranium mines from other isotopes or from contamination by atomic bombs and nuclear accidents. (if I'm the wrong one, correct me) Thanks Once4O4 (talk) 17:32, 14 September 2020 (UTC)

@Once4O4: I made this edit as a Wikipedia Graphics Lab request and the same argument came up at the time. The image reflects the content of the article for synthetic elements. Unless the article's definition for "synthetic" is changed, the SVG shouldn't be reverted. TilmannR (talk) 05:54, 18 September 2020 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 07:09, 11 February 2021 (UTC)

0 × 0 SVGs

I'm not shure who, but there is a possibilty to find files such as File:Kenya_map.svg, do you know how to filter for such files on commons?  — Johannes Kalliauer - Talk | Contributions 20:25, 17 September 2020 (UTC)

@JoKalliauer: You can search for 0×0 SVGs with the advanced search. TilmannR (talk) 06:08, 18 September 2020 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 07:09, 11 February 2021 (UTC)

Hi @TilmannR: , Could you make svg image pls and instead of SLPF write Somaliland Police Force and on both sides instead of RU write SL. and I want to Thank you for making Logo of Somaliland Police Force svg image Many Thanks 🙏🏽 -- — Preceding unsigned comment added by Siirski (talk • contribs) 20:05, 27 March 2021 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 14:59, 16 August 2021 (UTC)

Colors of the flag of Palestine

I don't have any special knowledge in this area, but a few years ago, someone went around changing all the SVG files of flags of Arab countries to use a uniform standardized shade of green. Further back, there was a clash of strong opinions about the shade of blue to be used in Chinese-related flags... -- AnonMoos (talk) 22:32, 20 April 2022 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 02:32, 21 April 2022 (UTC)
File:Flag of Palestine (lighter variant).svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Sakiv (talk) 17:11, 21 April 2022 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 12:21, 25 April 2022 (UTC)

Your barnstar awarding

Danke Tilmann, für den barnstar. Du hast sehr richtig beobachtet dass ich mich vor allem um technische Verbesserungen bemühe. Da ich wegen dieser Verleihung aktuell wieder auf dich aufmerksam wurde, komme ich dir hier nun mit einigen Anmerkungen.

  1. Du erzeugst sehr gute SVG. Gelegentlich wird von dir auch die Beschreibung von Image generation eingebaut, gelegentlich unterbleibt diese Anmerkung. Ich würde dir die generelle Verwendung des script empfehlen, trotz aller dort noch vorhandenen Māngel kann damit viel Aufwand eingespart werden.
  2. user name redlinks: In einer eigenen User page sehe auch ich keinen Vorteil, und wie unzählige andere nicht einmal eine Erfordernis dafür; hingegen sehe ich (im Gegensatz zu dir?) keine Attraktivität an redlinks: meine Beteiligung sehe ich nicht als so wichtig dass mein username derart stark farblich hervorzuheben ist, und ganz generell sollte IMHO jeder link direkt irgendwohin führen, ohne weitere links zu erfordern.
    Deshalb fände ich es besser wenn du eine Pseudo-Benutzerseite einrichtest mit #REDIRECT [[User talk:TilmannR]]. Aber das ist natürlich eine autonome Entscheidung von dir!
    Übrigens, an vielen Stellen - Vorlagen, script, cleanup - werden von mir solche redlinks gebläut, voll automatisch.
  3. Barnstar - technical works.svg: ganz typisch Inkscape, voll von Datenmüll (opacity:0.50000000000000000); von Grund auf neugeschrieben würde sinnvoller Code sicher weit weniger als 10% erfordern. Auch wenn es ohne Nutzen wäre, eine Herausforderung, zumindest eine nette Übung. PX! -- sarang사랑 08:15, 8 May 2022 (UTC)
@Sarang:
  1. Danke für das Kompliment! Soweit ich mich erinnern kann, habe ich noch nie {{Igen}} in meine eigenen Uploads eingebaut.
    • Die Parameter sind nicht menschen-lesbar und ich bezweifle, dass derartig komprimierte Templates besser sind als eine Aneinanderreihung mehrerer einzelner lesbarer Templates.
    • Automatisierbare Tasks (z.B. W3C validation) sollten automatisiert ablaufen. Circa 0 % der Benutzer kennen die entsprechenden Templates/Scripte/Guidelines.
    • Spätestens nach der Optimierung ist irrelevant welches Programm ich für WYSIWYG-editing verwende.
  2. Gute Argumente. Nur habe ich mich vier Jahre lang an meinen Redlink gewöhnt. Und solange ich keine (Pseudo-)Benutzerseite habe, ist genau dessen Abwesenheit ein Ausdruck meiner Individualität.
  3. Tja. Da war wohl jemand hinreichend dankbar um dir etwas in den User Talk zu schreiben, aber nicht dankbar genug um dafür ein neues, handoptimiertes SVG hoch zu laden. Vielleicht nächstes Mal. TilmannR (talk) 14:47, 8 May 2022 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 08:40, 14 September 2022 (UTC)

Update - File:Kandler 1998 Early diversification of life and pre-cell theory.jpg ?

Hi TilmannR,

thank you very much for creating the svg-file https://commons.wikimedia.org/wiki/File:Kandler_1994_Early_diversification_of_life_and_pre-cell_theory.svg in 2018! At that time I was new at Wikipedia and didn’t know how to write and thank you. Now I hope, your discussion page is still active? Do you think it would be possible to make an update? The newer and more detailed version of the pre-cell theory is shown in https://commons.wikimedia.org/wiki/File:Kandler_1998_Early_diversification_of_life_and_pre-cell_theory.jpg. *

I would like to use it instead of the old one. For a timely reply, I would be very grateful , thank you very much. Maya Kandler (Germany)

  • References:

Otto Kandler: The early diversification of life and the origin of the three domains: A proposal. In: Jürgen Wiegel, Michael W.W. Adams (eds.): Thermophiles: The keys to molecular evolution and the origin of life? Taylor and Francis Ltd., London 1998, pp. 19–31. You will find the above mentioned Figure 2.3 on page 22: https://books.google.de/books?id=FtSzl4iastsC&q=Otto+Kandler:+The+early+diversification+of+life+and+the+origin+of+the+three+domains:+A+proposal.+In:+J%C3%BCrgen+Wiegel,+Michael+%E2%80%8EW.W.+Adams+(Hrsg.):+Thermophiles&pg=PA19&redir_esc=y#v=onepage&q=Otto%20Kandler%3A%20The%20early%20diversification%20of%20life%20and%20the%20origin%20of%20the%20three%20domains%3A%20A%20proposal.%20In%3A%20J%C3%BCrgen%20Wiegel%2C%20Michael%20%E2%80%8EW.W.%20Adams%20(Hrsg.)%3A%20Thermophiles&f=false Maya Kandler (talk) 11:58, 17 December 2022 (UTC)

@Maya Kandler: ✓ Done (Kandler 1998 Early diversification of life and pre-cell theory.svg). TilmannR (talk) 10:46, 19 December 2022 (UTC)
Hi TilmannR,
thank you so much for your quick and perfect work, that's really greatǃ Maya Kandler (talk) 21:08, 20 December 2022 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 21:09, 20 December 2022 (UTC)

Delve into SVG

On the File talk:Cognitive bias codex en.svg you mentioned:

"Ultimately this file is a little experiment of mine."

I would love to delve deeper in everything surrounding your awesome SVG, if you're available for a conversation, I'd be greatly appreciate it.

Best regards Tim TimBorgNetzWerk (talk) 20:11, 5 January 2023 (UTC)

@TimBorgNetzWerk: Sure. What would you like to know? TilmannR (talk) 01:00, 6 January 2023 (UTC)
Bascially I'm trying to build my PhD on improving the representation and access to information. I saw your SVG and wanted to build more like this, wanted to understand how it works and extend the usage of this representation to other fields, hopefully semi-automatic.
Here some resources:
- My initial response to seing this:
-> https://www.linkedin.com/feed/update/urn:li:activity:7000846313365864448
- The projects description:
-> https://borgnetzwerk.de/aims-and-values/
- Some visualization about current progress:
-> https://twitter.com/BorgNetzWerk/status/1610912078818066432
Thank you, have a good start into the year and thanks for the opportunity to get some insights :)
Best regards
Tim TimBorgNetzWerk (talk) 08:51, 10 January 2023 (UTC)
@TimBorgNetzWerk: Well, what makes this SVG special is that it contains a <script> node, which overwrites itself with static SVG content. It's a compromise between
  • wanting to use scripting for improved maintainability
  • without requiring the installation of any compilers, interpreters, or libraries
  • while the direct uploading of SVGs with scripts is disallowed for security reasons.
It's a solution to a very specific problem. Your information sharing network doesn't have the same constraints. You can just feed plain old data into an off-the-shelf data visualization framework. And based on your tweets it seems like you're already familiar with some data mining and visualization techniques. TilmannR (talk) 16:54, 10 January 2023 (UTC)
Thanks alot again for the reply, I'd like to continue that train of thought though:
If i have an overview over these visualizations, or have generated such a visualization myself - wouldn't it be nice to extract where what dot is, save it to an xy map, feed that back through your script and have low-weight map of anything you'd want on any type of wiki, with the advantages you decribed?
In any case, I'd love to learn what you did exactly and how I would replicate it. Maybe you can just give me some starting points, like "take a look at my scribt and read xy documentation" or whatever, I'd appreciate any input :)
Best regards TimBorgNetzWerk (talk) 15:36, 13 January 2023 (UTC)
@TimBorgNetzWerk
I'd love to learn what you did exactly and how I would replicate it. Maybe you can just give me some starting points
Your optimal starting point depends on how much you already know about SVG and JS and programming in general.
  • If you're looking for basic programming tutorials, I don't have any specific recommendations.
  • If you're looking for reliable documentation on SVG, CSS and JS, there's https://developer.mozilla.org/en-US/ .
  • If you are already familiar with JS, then you can just read the script. It's a bit old-school, but I don't think that diminishes its legibility too much.
It's mostly arithmetic and string processing anyways. As you already know tree_text contains all the text and the names of Wikipedia articles. The function generate takes the data, computes the positions for the text and the handles of the bezier curves, and converts it all into a string to be inserted into the SVG.
wouldn't it be nice to extract where what dot is, save it to an xy map, feed that back through your script
Well, this script was written specifically to create a maintainable vector graphics version of an existing PNG: The Cognitive Bias Codex - 180+ biases, designed by John Manoogian III (jm3).png.
It is not universal. It cannot generate visualizations that are substantially different from what it currently generates unless it's heavily modified. And while the circular arrangement is visually pleasing, I don't think it's a good idea to make people read vertical or diagonal text. So you're much better off using a more powerful data visualization library instead of trying to reuse this script. TilmannR (talk) 18:57, 15 January 2023 (UTC)
Thanks, I guess that's more than I could have ever asked for :)
I was and still am just so impressed about the potential of having a graphic that is searchable. With this explanation, I'll be able to work it out once recreating or utilizing this is on the agenda for my project. I'll pin this conversation and thank you again for your help ;) TimBorgNetzWerk (talk) 19:59, 15 January 2023 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 20:31, 15 January 2023 (UTC)

svg

hi, wie erstellst du diese svgs: Oli968.svg
mit welchem programm und mit welcher vorlage? oder hast du vektordaten im internet gefunden? --Mrmw (talk) 15:08, 20 February 2023 (UTC)

@Mrmw: Die Bilder sind in Inkscape per Hand getraced, dann mit SVGOMG optimiert. Die Vorlage steht jeweils als "source" in der {{Information}}. Das "M" logo und einige der Ziffern sind aus den "other versions" kopiert, damit alle Versionen einigermaßen konsistent sind. TilmannR (talk) 11:46, 21 February 2023 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 18:56, 3 March 2023 (UTC)

Rollback right given

I have granted rollback rights to your account; the reason for this is that after a review of some of your contributions, I believe I can trust you to use rollback correctly by using it for its intended usage of reverting vandalism, and that you will not abuse it to revert-war. For information on rollback, see Commons:Rollback. If you do not want rollback, just let me know, and I'll remove it. Good luck and thanks. —‍Mdaniels5757 (talk • contribs) 00:11, 4 March 2023 (UTC)

For the record: Rollback rights turn out to be less useful than I hoped they would be, because one can only rollback the most recent user's edits, even if it's just a minor edit by a bot account. Therefore all vandalism that gets categorized by a bot (e.g. here) is un-rollback-able. TilmannR (talk) 20:41, 4 March 2023 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 02:48, 4 March 2023 (UTC)
File:Kandler 1994 Early diversification of life and pre-cell theory.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Maya Kandler (talk) 21:23, 8 March 2023 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 13:57, 12 March 2023 (UTC)

RAI logos

Hi! Thank you for this and others. I've reached out to the IP user (109.166.138.32 (talk · contribs)) to ask them to stop doing this. I also just cleaned up their "contributions". Cheers! Cryptic-waveform (talk) 17:40, 23 March 2023 (UTC)

@Cryptic-waveform: Hi. I'm glad that we finally emptied Category:Pages using Information template with parsing errors. It's a little anticlimactic that I wasn't here for the last ones, but since most of them were just missing }}, it's probably better that you did it with bot support. Thank you! TilmannR (talk) 07:57, 26 March 2023 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 20:08, 21 May 2023 (UTC)

SVG version

Hi Tillmann, Could u make an SVG version of this map;  ? Suthernorthernwestby (talk) 16:50, 26 March 2023 (UTC)

@Suthernorthernwestby: No, sorry. I don't have much time right now.
I do not recommend posting such requests in multiple places at the same time. Imagine if Goran tek-en and I had immediately started working on this request. One of us would have wasted their time.
Assuming that the image is based on File:Somalia location map.svg, you need to adjust the source and license information of your file, because the original file is under a license, which requires that derivative works use an equivalent license and mention the original author. TilmannR (talk) 19:26, 26 March 2023 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 20:08, 21 May 2023 (UTC)

I am impressed with your clarity, reasoning, sources, and patience. Glrx (talk) 05:41, 6 April 2023 (UTC)

@Glrx: Humility requires me to declare that I didn't do anything impressive. But I do appreciate the compliment. It really brightened my day. TilmannR (talk) 18:53, 6 April 2023 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 20:08, 21 May 2023 (UTC)
File:Mario Fan-art (Pixel art graphic style).svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Nosferattus (talk) 04:50, 11 June 2023 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 01:48, 12 June 2023 (UTC)

Planetary Models

Hello, TilmannR!

I recently viewed your 3D .stl planetary models of the Moon, Earth and Mars,

https://commons.wikimedia.org/wiki/File:Mars_elevation_2.stl

...etc, and think that they are wonderful!

I was wondering, seeing as you’ve already started :), do you think that you would have the time to also create the same type of 3d-renderings of Venus and of Mercury? That way, you would be providing a full set for people to marvel at!

(If you don’t have the time to do both, I think Venus would be the more significant of the two, considering its many similarities to our own planetary home.)

Thanks in advance, and I look forward to hearing back from you!

Aryiadne (talk) 18:53, 28 November 2023 (UTC)

p.s.

I am aware that the necessary radar data for creating the models does exist, likely on the same nasa/wu pages that you have used in the Mars model, such as perhaps here :

Detailed topographic maps of the two planets also exist, such as :

and so on, so the data is certainly out there...

:)
@Aryiadne: Hi. Unfortunately I have to decline.
  • I'm not actively participating in the Wikipedia Commons at this time. I'm busy with various other things.
  • I've searched for the script I used to generate the Earth and Mars models, but apparently I no longer have it.
  • As far as I know the high-quality topographical data of Mercury and Venus is incomplete. Mixing it with low-quality estimates would lead to distracting visual artifacts unless a lot of effort is invested into generating fake data.
TilmannR (talk) 23:16, 3 December 2023 (UTC)
Hello again, TilmannR!
I am so sorry to hear that you won't be able to create these models :(
In any case, IF one day you decide that you can find the time, here are two interesting pages that I found :
They are prints of 3D relief maps of Venus and Mercury (Mercator projections), which seem to be extremely detailed. So even if the datasets that you would need are not to be found at the WU-StL links that I originally provided, they certainly seem to be available somewhere.
I wish you every success with whatever it is that you are working on currently! :)
Aryiadne (talk) 14:32, 5 December 2023 (UTC)
Thanks! :) TilmannR (talk) 16:56, 5 December 2023 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 16:56, 5 December 2023 (UTC)

Happy new year

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

Thanks! I wish you a happy new year, too. TilmannR (talk) 00:15, 1 January 2024 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 15:36, 3 January 2024 (UTC)

Self-generating SVG with JavaScript

Hi TilmannR,

I've just come across File:Cognitive_bias_codex_en.svg and am intrigued by your idea to generate a static SVG from one with JavaScript. I have been generating SVG with Python. As you wrote, the advantage of your method is that one doesn't need any software besides a web browser.

I'd like to experiment with your idea but somehow embed the JavaScript as a comment in the SVG itself, so that the source is never detached from the file. If one saves my SVG files generated from Python as a .py file and deletes the first line (I would've preferred not having to do this but couldn't find a way), one gets a valid Python script that generate the SVG.

Might you be interested to further your experiment in a similar manner? I suppose the editor has to replace

<!--

with

<script

or similar.

Thanks,
cmɢʟee ⋅τaʟκ 14:01, 26 December 2023 (UTC)

@Cmglee: Hi! The cognitive bias SVG has the following structure:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg xmlns="http://www.w3.org/2000/svg" width="600" height="600" viewBox="-100 -100 200 200">
  <g id="generated_content">
  <script type="text/javascript"><![CDATA[
    var result = ['<circle r="100"/>', '<circle r="50" fill="#fff"/>']; // Just an example
    document.getElementById("generated_content").innerHTML = result.join('');
  ]]></script>
  </g>
</svg>
so the line that makes the result visible simultaneously removes the script. With a slight modification...
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg xmlns="http://www.w3.org/2000/svg" width="600" height="600" viewBox="-100 -100 200 200">
<g id="generated_content"></g>
<g id="generator_script">
<script type="text/javascript"><![CDATA[
  var result = ['<circle r="100"/>', '<circle r="50" fill="#fff"/>']; // Just an example
  document.getElementById("generated_content").innerHTML = result.join('');
  
  var generator_script = document.getElementById("generator_script");
  var script_as_comment = generator_script.innerHTML.replace(/<scrip[^>]+>/, '<!-'+'-scrpt>').replace('</scr'+'ipt>', '</scrpt-'+'->');
  generator_script.innerHTML = script_as_comment;
... you can keep the script as a comment. Then the person using the script only has to replace <!--scrpt> with <script type="text/javascript"> and </scrpt--> with </script>, which is easily automated.
It's just a little annoying that "For compatibility, the string " -- " (double-hyphen) MUST NOT occur within comments.".
TilmannR (talk) 14:28, 27 December 2023 (UTC)
Hi TilmannR, many thanks for explaining how your method works and devising a way to embed itself. I'll experiment with it the next time I've to upload an SVG needing scripting. If it works well, would you mind if I write it up as a how-to, of course crediting you? Cheers, cmɢʟee ⋅τaʟκ 16:47, 27 December 2023 (UTC)
@Cmglee: I wouldn't mind at all. I'm just not sure whether it's wise to invite other people to distribute arbitrary source code via Commons. It's not what Commons is for, and we have no way to protect people, who just want to translate or fix typos, from executing malicious code other than JS being somewhat sandboxed by default. TilmannR (talk) 08:01, 28 December 2023 (UTC)
That's a very fair point. Guess any language we use to generate the SVG has risks of someone exploiting it. At least Javascript is sandboxed, though due to potential browser exploits, even an external tool like Toolforge has risks. Cheers, cmɢʟee ⋅τaʟκ 13:10, 28 December 2023 (UTC)
The analogue of Gabriel's horn in two dimensions has an area of 2 but infinite perimeter
I've made my first SVG using your script, modified and commented to help other editors as much as possible. Would you have some time to review my changes? Thanks in advance, cmɢʟee ⋅τaʟκ 07:07, 31 December 2023 (UTC)
@Cmglee:
  • Converted the loop into a function (easier to reuse & replace)
  • Using string interpolation instead of + (asymptotically faster, but doesn't matter for a small number of short strings. P.S. I wouldn't be surprised, if modern JS interpreters automagically optimize string concatenation.)
  • Replacing var with const (slightly nicer semantics)
function number_to_string(x, decimals=2) {
	return Number.parseFloat(x.toFixed(decimals)).toString();
}

function piecewise_linear_approximation(f, x0, x1, step_size=0.1, scale=100) {
	const num_lines = Math.round((x1-x0)/step_size);
	const xy_svg = [];
	for(let i=0; i <= num_lines; ++i){
		const x = (x0 * (num_lines - i) + x1 * i) / num_lines;
		const x_svg = number_to_string(  x * scale);
		const y_svg = number_to_string(f(x)* scale);
		xy_svg.push(`${x_svg},${y_svg}`);
	}
	return xy_svg.join('L');
};

const out = [];
/// ======================== SVG-specific JavaScript =========================

const out_dash  = piecewise_linear_approximation((x)=>1/(x*x), 0.5, 1.0);
const out_solid = piecewise_linear_approximation((x)=>1/(x*x), 1.0, 3.5);
out.push(`
<g id="half" stroke="#c00">
	<path class="dash" d="M${out_dash}"/>
	<path fill="#fc0" d="M350,0H100L${out_solid}"/>
</g>`);

 /// ============= JavaScript SVG generator by TilmannR and cmglee ============
 document.getElementById('GENERATED_CONTENT').innerHTML =
                        '\n\n' + out.join('') + '\n\n ';
 const generator     = document.getElementById('GENERATOR_SCRIPT');
 generator.innerHTML = generator.innerHTML.
                        replace(/[<]script[^>]*/, '<!-' + '-script').
                        replace(/<[/]script>/, '</script-' + '->');
piecewise_linear_approximation could be replaced with a cubic_bezier_approximation function, but I'm too lazy/tired to implement that right now. I wonder whether there's a better way to implement number_to_string i.e. Number.toFixed() but without superfluous trailing zeros.
TilmannR (talk) 00:26, 1 January 2024 (UTC)
Thank you very much for your feedback. You seem an expert in JS! I've implemented most of your recommendations.
Though you are right that a const array (out) can still be pushed to, I wonder if that might mislead editors (as it did me until I looked it up).
One nitpick I have is that non-ASCII characters specified thus: &#177; are replaced: ± so the file is no longer ASCII. When opened in ASCII-only text editors or fonts, the characters are garbled. Even if it works, it becomes difficult to distinguish different types of dashes. Is there a way to force the saved file to be ASCII?
Thanks, cmɢʟee ⋅τaʟκ 10:11, 1 January 2024 (UTC)
I don't consider myself to be a JS expert, but thanks for the compliment.
It's all a matter of perspective: Not the array is constant, but the reference to the array is constant. So in a way const makes the code less confusing, because you know that (within the current block) the given identifier always refers to the same object.
UTF-8 is a very popular standard, so I wouldn't worry about limiting the character set to ASCII. Imagine a file with Chinese or Arabic or Russian – any kind of non-latin text: If all those characters are converted to escape sequences, the text is no longer human-readable and becomes much more difficult to edit. TilmannR (talk) 11:43, 1 January 2024 (UTC)
😊 I see your points. I've updated the code and added a comment to avoid confusion (SVG may be pushed into the array even if out is a constant.)
It's true for text in different languages. It can lead to confusion for different types of dashes or spaces, though. Cheers, cmɢʟee ⋅τaʟκ 14:38, 2 January 2024 (UTC)

Hi TilmannR, in case it interests you, I've begun porting my US choropleth map to this model. I also adapted your number_to_string function to strip trailing zeros as follows:

function round_to_string(x, decimal_places=2, do_trim=false) {
 const str = parseFloat(x).toFixed(decimal_places).toString();
 if (do_trim) { return str.replace(/\.0*$/, '').replace(/(?<=\.\d+)0+$/, ''); }
 else         { return str; }
}

Have I missed anything? Cheers, cmɢʟee ⋅τaʟκ 04:33, 15 January 2024 (UTC)

P.S. Is it better to use
 if (do_trim) { return str.replace(/\.0*$/, '').replace(/(\.\d+)0+$/, '$1'); }
instead of lookbehind? cmɢʟee ⋅τaʟκ 04:42, 15 January 2024 (UTC)
toFixed returns a string, so calling toString should be superfluous.
<source> is deprecated. Please use <syntaxhighlight> instead. Otherwise my talk page gets put into Category:Pages_using_deprecated_source_tags.
Note that .replace(/\.0*$/, '').replace(/(\.\d+)0+$/, '$1') turns 0.1000 into 0.100, because the \d+ will greedily match all but the final 0. You can fix this by either explicitly asking for a nonzero digit (i.e. \d*[1-9]) or making the + lazy by appending a ?, which is shorter, but also less legible.
return !do_trim? str : str.replace(/\.0*$|(\.\d+?)0+$/, '$1');
... both replaces .0*$ with the empty string and replaces .\d*[1-9]0+$ with .\d*[1-9] in a single expression. TilmannR (talk) 11:41, 15 January 2024 (UTC)
Thank you very much, TilmannR, and also for telling me why I should use syntaxhighlight; I've updated the JavaScript.
Would you also be interested to have your invention (generating SVG with JavaScript) presented at Wikimania 2024? If you'd rather not present it, would you mind if I did, giving you full credit, of course? I think that it is a superb way to programmatically generate SVG and that the community would benefit from more widespread use of this technique.
Thanks,
cmɢʟee ⋅τaʟκ 15:40, 16 January 2024 (UTC)
Oh, that's a tricky question. On one hand giving a presentation might help me become more confident and better at giving presentations. On the other hand I have very little to say about this. The key insight is that browsers execute script tags in SVG files. Everything else is just implementation details, which are (in my opinion) not particularly interesting.
🤔
P.S. Instead of using the Levenshtein distance to fuzzy-select an abbreviation I'd output an error message, using the Levenshtein distance to suggest the "correct" way of spelling a given name. Otherwise you can get unexpected results, if someone for some reason names a territory that isn't in your list. TilmannR (talk) 12:19, 17 January 2024 (UTC)
Thanks for your support. If you think it's too short, we could split the session into your generation with JavaScript, and I could talk about my prior generation work with Python, Perl and Google Sheets.
The deadline for scholarships has passed and presentation submissions are due in June so we have plenty of time.
Cheers, cmɢʟee ⋅τaʟκ 10:42, 18 January 2024 (UTC)
I think I'll pass. TilmannR (talk) 15:55, 18 January 2024 (UTC)
No problem at all. Is it all right that I talk about your generation system if I decide to go ahead? Thanks, cmɢʟee ⋅τaʟκ 00:18, 19 January 2024 (UTC)
Of course. TilmannR (talk) 22:52, 19 January 2024 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. TilmannR (talk) 10:37, 3 April 2024 (UTC)