Open main menu
Archive This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Contents

File tagging File:Rstab verschiebungen.png

беларуская (тарашкевіца)‎ | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | español | euskara | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | italiano | 日本語 | 한국어 | lietuvių | македонски | മലയാളം | मराठी | Plattdüütsch | Nederlands | norsk | polski | português | română | русский | sicilianu | slovenčina | slovenščina | српски / srpski | svenska | Türkçe | українська | اردو | Tiếng Việt | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:Rstab verschiebungen.png. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or send an email with copy of a written permission to OTRS (permissions-commons@wikimedia.org). This also applies if you are the author yourself.

Please see this page for more information on how to confirm permission, and Commons:Permission if you would like to understand why we ask for permission when uploading work that is not your own.

Unless the permission information is given, the file may be deleted after seven days. Thank you.

And also:

Yours sincerely EugeneZelenko (talk) 14:52, 15 March 2016 (UTC)

@EugeneZelenko: I produced those screenshots. Me and a universitycollege of mine produced the opened file. I (=User:JoKalliauer) said User:JoKalliauer is the autor. So I don't really understand why I need a permisson of the autor, when I am the (main) autor? Isn't it common sense, when somebody who has the permission to upload something, and then he also upload it, that he has the permission of uploding? -- JoKalliauer (talk) 16:15, 15 March 2016 (UTC)
What is copyright status of software? See Commons:Screenshots. --EugeneZelenko (talk) 14:11, 16 March 2016 (UTC)
@EugeneZelenko: Thank you for the information.
Could you delete the old version of:
the current versions of those pictures should be allowed. JoKalliauer (talk) 17:56, 17 March 2016 (UTC)
  Done --EugeneZelenko (talk) 14:21, 18 March 2016 (UTC)
This section was archived on a request by: JoKalliauer (talk) 17:49, 28 March 2016 (UTC)

Copyright status: File:02-05-2015 Bildschirm002.png

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:02-05-2015 Bildschirm002.png. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.

If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.)

If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there.

Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

And also:

No required license templates were detected at this file page. Please correct it, or if you have any questions please check my FAQ or contact me on my talk page. Yours sincerely, Jarekt (talk) 11:52, 6 April 2016 (UTC)

@Jarekt: As you can see I deleted the license on purpose, also I created thos screenshots and I added {{subst:delete2|image=*.png|reason=}}, that means I would like to delete those pictures.
Why do you send me a information about possible deletion? I requested the deletion. JoKalliauer (talk) 12:05, 6 April 2016 (UTC)
I do not know about your intentions to delete those files, but you removed a license template and I am just informing you that that will cause eventual file deletion. If that is your intention than do not do anything and the file will be deleted in a week. --Jarekt (talk) 12:11, 6 April 2016 (UTC)
Wurden gelöscht   DoneJoKalliauer (talk) 12:47, 12 April 2016 (UTC)
This section was archived on a request by: JoKalliauer (talk) 12:47, 12 April 2016 (UTC)

Copyright status: File:2D-Lager.png

беларуская (тарашкевіца)‎ | български | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | English | فارسی | suomi | français | magyar | italiano | македонски | മലയാളം | Bahasa Melayu | 日本語 | norsk | polski | português | português do Brasil | română | slovenščina | svenska | українська | ಕನ್ನಡ | ತುಳು | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:2D-Lager.png. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.

If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.)

If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the OTRS system and follow the procedure described there.

Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

Yours sincerely, JuTa 22:24, 31 December 2016 (UTC)

@JuTa: Da wir beide Deutsch als Muttersprache haben, hoffe ist das ok, wenn ich in Deutsch schreibe.
Laut der Deuschen Wikipedia ist diese Datei unter der Schöpfungshöhe, siehe:
https://de.wikipedia.org/w/index.php?title=Wikipedia:Urheberrechtsfragen&diff=161075357&oldid=161073474
Ein Link auf die de:Wikipedia:Urheberrechtsfragen ist auch beim Bild
Damit sehe ich keinen Grund warum die Datei gelöscht werden sollte.
Edit: Ich habe gerade gesehen dass du das behoben hast.
Danke
This section was archived on a request by: JoKalliauer (talk) 06:47, 1 January 2017 (UTC)

SVG (Scalable Vector Graphics)

беларуская (тарашкевіца)‎ | Deutsch | English | español | français | hrvatski | italiano | 日本語 | português | português do Brasil | македонски | ಕನ್ನಡ | ತುಳು | +/−

 
Thank you for uploading some images! Did you know that Wikimedia Commons recommends the SVG (Scalable Vector Graphics) format for certain types of images? Scalable Vector Graphics are designed to look appropriate at any scale, and SVG images are easier to modify and translate, helping Wikimedia to distribute knowledge to all of the world. A lot of modern programs support SVG export. If you encountered problems or have questions, don't hesitate to ask me, a member of the Graphic Lab, or the Graphics village pump. Uploading images in SVG format isn't mandatory, but it would help. (To avoid any misunderstandings, please don't just put raster images into a svg container as embedded raster.) Thanks, and happy editing!
already as SVG:
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 11:33, 1 March 2017 (UTC)|2=done

Deletions nominations

Hi, please only nominate categories for deletion if empty. Jcb (talk) 20:05, 4 September 2016 (UTC)

@Jcb: Thanks, but I'm still working on it, isn't there a bot for changing categorienames? JoKalliauer (talk) 20:08, 4 September 2016 (UTC)
Yes, there is. You can use 'Perform batch task' from the left menu. Jcb (talk) 20:10, 4 September 2016 (UTC)
@Jcb:Thanks, but I can't find it in the left menu, do I have to check the Preferences? or is it only available vor admins? Or am I'm just to silly to find it? Here is a screenshot: http://i1127.photobucket.com/albums/l632/Jo-Kalliauer/Category%20Vienna%20University%20of%20Technology%20%20%20Wikimedia%20Commons_zpsrzsvffby.png JoKalliauer (talk) 20:22, 4 September 2016 (UTC)
Do you mean VisualFileChange.js? JoKalliauer (talk) 20:33, 4 September 2016 (UTC)
Yes, that's it. Jcb (talk) 21:00, 4 September 2016 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 11:33, 1 March 2017 (UTC)|2=happend before finishing edition

File:Badjpeg.svg

 
File:Badjpeg.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 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!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

nyuszika7h (talk) 21:16, 16 February 2017 (UTC)

Decision was:   Keep
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 11:33, 1 March 2017 (UTC)|2={{Vote keep}}

Your VFC installation method is deprecated

Hello JoKalliauer, we are aware that using the old installation method of VFC (via common.js, which you are using) may not work reliably anymore and can break other scripts as well. A detailed explanation can be found here. Important: To prevent problems please remove the old VFC installation code from your common.js and instead enable the VFC gadget in your preferences. Thanks! --VFC devs (q) 16:23, 22 May 2017 (UTC)

This section was archived on a request by: JoKalliauer (talk) 20:21, 23 May 2018 (UTC)

GPS Satellite.svg

Ich glaube weder Inkscape, noch path-text. Bist du da sicher ? Gruss -- sarang사랑 08:07, 30 October 2017 (UTC)

@Sarang:
Inkscape
Ich habe File:GPS_Refraction.svg (angeblich mit Inksacpe erstellt) genommen und mit Inkscape das Bild "herausgeschnitten" und anschließend das Skript auf de:Benutzer:JoKalliauer/Inkscape-SVG-Speichern#Automatisch ausgeführt und dann gemäß de:Benutzer:JoKalliauer/Inkscape-SVG-Speichern#Wie_komprimiere_ich_die_Dateigr.C3.B6.C3.9Fe das Bild komprimiert und dann abermals de:Benutzer:JoKalliauer/Inkscape-SVG-Speichern#Automatisch ausgeführt.
Skript
Ich das Skript vor auf den Wikimedia-Tool-Server laufen zu lassen, aber vorher will ich dessen Funktionalität testen.
path-text
Alle Texte sind doch als Pfad?   Ja, das ist ein copy&past Fehler von der Quelle, da ich keine path-Texte mitgenommen habe, habe es bereits ausgebessert. Danke für den Hinweis.
 — Johannes Kalliauer - Talk | Contributions 17:42, 30 October 2017 (UTC)
This section was archived on a request by: JoKalliauer (talk) 20:21, 23 May 2018 (UTC)

Code issues in User:JoKalliauer/common.js

Hi JoKalliauer, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:JoKalliauer/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 2 character 91: Script URL. - Evidence: mw.util.addPortletLink('p-tb', 'javascript:importScript("MediaWiki:VisualFileChange.js");', 'Perform batch task', 't-AjaxQuickDeleteOnDemand');

Your CommonsMaintenanceBot (talk) at 19:39, 30 October 2017 (UTC).

This section was archived on a request by: JoKalliauer (talk) 20:21, 23 May 2018 (UTC)

bitte aufpassen

So etwas [1] gehört auf die talk page des Benutzers und nicht auf die Benutzerseite. Gruß, --Achim (talk) 19:58, 2 November 2017 (UTC)

Danke, war unabsichtlich  — Johannes Kalliauer - Talk | Contributions 20:05, 2 November 2017 (UTC)
This section was archived on a request by: JoKalliauer (talk) 20:21, 23 May 2018 (UTC)

For your information

Hallo, ich habe nun mal File:Korea National Route 5.svg mit eingebettetem Text erzeugt - nur so mal zum Spass. 3mal kontrolliert, scheint alles zu stimmen. Mir fällt auf dass der verwendete Font wohl nicht so optimal ist, wirkt etwas unharmonisch - aber bei einer Kartenskizze ist das sicher von minderer Wichtigkeit?
Was mir noch auffällt: die DOCTYPE-Deklaration wird von unserem librsvg nicht benötigt, kann wegbleiben. Wenn du aber width/height weglässt orientiert sich die Grösse am 512-default, was nicht immer günstig ist. Ich habe DOCTYPE belassen, und die Originalgrösse wieder angegeben, was wiederum die viewBox redundant gemacht hat. Schönen Ostermontag! -- sarang사랑 11:21, 2 April 2018 (UTC)

Hallo Sarang!
  1. zu File:Korea National Route 5.svg: Ich finde eingebetten Text besser (leichter bearbeitbar und schärfer)
  2. zu DOCTYPE-Deklaration (kurz DTD)
    1. Ich bin ein Fan von validen Dateien ohne Warnungen beim W3C-Validator (deutsche/österreichische Korrekteit)
    2. Beim W3C-Validator werden gewisse Fehler nur mit DTD gefunden.
    3. Bzw. die Verwendung von DTD stellt sicher, dass die Datei nur Funktionen beinhaltet hat die "von allen" unterstützt wird, und somit unabhängig von der Betrachtersoftware funktionieren sollte.
    4. Lade dir File:Ways_of_St-2._James_in_Europe.svg herunter, öffne die Datei in einem Browser deines Vertrauenes und dann lösche DTD und du wirst sehen die Datei wird dann gar nicht mehr angezeigt. (PS Das hat nichts mit dem librsvg-bug zu tun, der nur aus Sicherheitsgründen keine xlink:href="data:;base64, zulässt.)
    5. Bin nicht der Einzige der DTD verwendet/bevorzugt: z.B::de:Benutzer:Marsupilami/Inkscape-FAQ oder die Ergänzung von DTD von Antonsusi bei meiner allerersten SVG
    • Ich verwende keine DTD wenn eine Datei Metadaten hat, weil dann ein Error beim W3C-Validator kommt, statt nur einer Warnung.
  3. viewBox
    1. Ich bevorzuge viewBox, weil im Browser dann das Bild genau hineingefittet wird (zu kleine Bilder sieht man groß genug um selbst Rundungsfehler durch CleanUp zu erkennen, zu große Bilder sieht man das ganze Bild ohne zu scrollen)
    • Bei dem Bild kam der Wunsch die Datei zu bereinigen, deshalb hab ich Scour im "aggressiven Modus" (inklusive --enable-viewboxing) durchlaufen lassen. Ob man viewBox bevorzugt oder nicht ist mMn Ansichtssache. Bei eigenen Bildern verwende ich viewBox (ohne height und ohne width) eigentlich immer.
    • PS: In der Englischen Wikipedia wird ein Bot damit beauftragt tausende non-free-content-svgs die Anzeigegröße zu reduzieren. Ich habe zwar die Vorgangsweise(en:User:Ronhjones/SVGreduce) erklärt die das in Zukunft Verlustfrei macht (im Gegensatz zu früheren Bearbeitungen, wo der Inhalt skaliert wurde und somit auch die Dateigröße unverhältnismäßig größer wurde), erkenne aber nicht wirklich den Sinn darin.
JoKalliauer (talk) 13:10, 2 April 2018 (UTC)
@Sarang: (zumindest bei mir gehen Diskseiten oft in der Beobachtungliste unter, würde mich über deine Meinung dazu freuen) JoKalliauer (talk) 18:33, 2 April 2018 (UTC)
hallo; bei DTD bin ich leidenschchaftslos - wenn sie einen Sinn hat dann deklarieren, mir ist sie bisher in der Wp redundant erschienen - auch wenn der SVG-Standard verfehlt wird,
Ich plädiere immer dafür eine "sinnvolle" Grösse zu wählen, das ist (bei Wappen, Fahnen etc.) eine Höhe so bei 400 bis 600 px, das gibt eine gute erste Anzeige, ohne Zooming und Scrolling; bei winzigen Icons kann das auch weniger sein, zB 24 × 24. Insofern ist der 512-Automatismus ein guter default.
Ich habe keine Beobachtungsliste aktiviert, somit merke ich Nachrichten und Danksagungen sofort. -- sarang사랑 21:53, 2 April 2018 (UTC)
This section was archived on a request by: JoKalliauer (talk) 20:21, 23 May 2018 (UTC)

 
suggestion2

Hi @JoKalliauer:,

please make a logo for Saraiki Wikipedia (Request).

Translations :i
Wikipedia = وکیپیڈیا
The Free Encyclopaedia = مُختی بھوم ڳوجھی

You can take help from Urdu logo

Thanks in advance. — — Bukhari (Talk!) 15:27, 25 June 2018 (UTC)
@BukhariSaeed: I now hardly do anything anymore that that is more than editing Text in SVG, since the Logo is a path-Text-version it is more "difficult" to edit, therefore I'm not sure if I take the request.
Generally the correct way to do it would be to ask on Commons:Graphic_Lab/Illustration_workshop and you might ping some persons related to this picture.
@PageWatcher: You are allowed to take this request. (I might do it, but not now.)
 — Johannes Kalliauer - Talk | Contributions 14:40, 28 June 2018 (UTC)
@BukhariSaeed: File:Wikipedia-logo-v2-Saraiki.svg   Done Or do you want a png-Version, or a path-Text-SVG-Version?  — Johannes Kalliauer - Talk | Contributions 16:41, 4 July 2018 (UTC)
Please use Nastliq fonts & the text is not correct, it should be in centre.— Bukhari (Talk!) 16:45, 4 July 2018 (UTC)
@BukhariSaeed: I dont know Nastaʿlīq script, it would be great if you could tell me any font listed in meta:SVG fonts#Arabic fonts comparison  — Johannes Kalliauer - Talk | Contributions 21:31, 4 July 2018 (UTC)
Use font-family: "Jameel Noori Nastaleeq"— Bukhari (Talk!) 02:04, 5 July 2018 (UTC)
@BukhariSaeed: I changed the font to font-family="Jameel Noori Nastaleeq", but as said before I would recommend any font listed in meta:SVG fonts#Arabic fonts comparison. And the text ist horizontally centered.   Done  — Johannes Kalliauer - Talk | Contributions 20:35, 5 July 2018 (UTC)
Thanks alot :), Please upload png version.— — Bukhari (Talk!) 03:56, 6 July 2018 (UTC)
Since I do not have the font installed, It would look identical to the wikirenderer: Here are the PNGs (created by Wikipedia):
 — Johannes Kalliauer - Talk | Contributions 16:28, 6 July 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 16:28, 6 July 2018 (UTC)
 
compare with وکیپیڈیا
There was a long discussion of Arabic fonts at Talk:Wikipedia/2.0 that also links to File_talk:Wikipedia_in_Arabic_script_languages_in_KACST_Office.svg (note last topic). I do not understand the script issues. It sounds like librsvg should have a Nastaleeq font, but I (1) don't know if it does or (2) how to find out whether it does (the claimed list of fonts appears to be inaccurate) or (3) how get such a font installed for librsvg on Commons. If you (BukhariSaeed) have an appropriate font, then I would suggest converting the SVG logo's text to curves with Inkscape and overwriting the existing Saraiki.svg logo. Glrx (talk) 17:06, 6 July 2018 (UTC)

Amnesia

Hallo Johannes, vielleicht kannst du mir helfen: Vor einiger Zeit hatte ich versprochen eine SVG-Grafik zu zeichnen; ich kam bisher nicht dazu, jetzt wollte ich mich damit befassen - und kann nirgends mehr finden um was es ging. Kann es sein dass du auch an der betr. Disku beteiligt warst, und weisst was es war? -- sarang사랑 05:43, 18 July 2018 (UTC)

@Sarang: Meinst du vl. #File:20T superconducting magnet.png? :-D  — Johannes Kalliauer - Talk | Contributions 06:25, 18 July 2018 (UTC)
Ja, genau, vielen Dank! Bisschen peinlich dass mein Kurzzeitgedächtnis mich so im Stich lässt, zum grossen Glück gibt es andere wie dich die mir helfen können. :This section was archived on a request by: -- sarang사랑 06:30, 18 July 2018 (UTC)

File:USA Counties with FIPS and names.svg

You need to think about what you are doing. Glrx (talk) 23:41, 30 August 2018 (UTC)

There are several things you could mean:
  1. I should edit more carefully and try to avoid uploading pictures twice
  2. The precision is too low
  3. Removing invalid id-names-errors does not make sense
  4. You think the old code was better readable
Explanation:
  1. Sorry, I'm a bit scatterbrained.
  2. Even if zooming in I cannot see any visual changes
  3. A file containing more than 500Errors are problematic, because if there are relevant errors you cannot find them, and for nu often stops counting by roughly 1000Errors. Files in Category:SVG_files_with_multiple_W3C-errors often tends to buggy behaviour, when viewing/editing.
    • I do not understand the numbers, they are not the zip-code/postal code, therefore they might be misleading.
  4. I would not edit such large files in a text-editor, and if so I generally prefer tiny code. The file was created by Inkscape.
 — Johannes Kalliauer - Talk | Contributions 07:16, 31 August 2018 (UTC)
FIPS are like postal codes. (BTW, the ZIP code database includes FIPS codes.) The whole point of the graphic was to provide a graphic with the FIPS codes. By deleting the codes, the utility of the graphic disappears. The data should remain; it just needs formatting to comply with the spec. `Glrx (talk) 07:43, 31 August 2018 (UTC)
Thanks for taking care of my edits! :-D Now it should be ok again.
 — Johannes Kalliauer - Talk | Contributions 09:33, 31 August 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 09:33, 31 August 2018 (UTC)

Weclome

Welcome to Wikimedia Commons, JoKalliauer!
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 11:33, 1 March 2017 (UTC)
This section was archived on a request by: JoKalliauer (talk) 20:21, 23 May 2018 (UTC)

Thank you for your participation in Wiki Loves Love 2019

Wiki Loves Love 2019 has ended and team Wiki Loves Love sends you greetings and appreciation for joining us in spreading love around the globe and documents how love is expressed in different cultures. We hope to see you again in 2020. Till then stay tuned to know the results of WLL19 that will be out in this April. Please make sure that your email is enabled so we can communicate with you if you are one of our prize winners.(learn more how to do)

Best regards.

Wiki Loves Love International Team

--MediaWiki message delivery (talk) 07:31, 18 March 2019 (UTC)

I think I did not participape on purpose.  — Johannes Kalliauer - Talk | Contributions 17:00, 18 March 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 17:00, 18 March 2019 (UTC)

File:Medellin Kartell.svg

Hallo JoKalliauer,

vielen Dank für die Vektorisierung. Ich war lange offline in der Wikipedia und habe es erst jetzt gesehen.

Grüße, Kopiersperre (talk) 09:55, 1 March 2017 (UTC)

Kein Problem  — Johannes Kalliauer - Talk | Contributions 11:33, 1 March 2017 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

Re:Group rename

Ok, but it is necessary to delete the redirects. You should use the template {{Rename}} in each file to know what the new name you want. Example: in File:MDKQ anim3.svg add {{rename|1=|<new name>|2=2|3=<reason>|user=}} and fill in the parameters. I think an admin could do it faster, because there are many files and redirects must be deleted. Jarould [talk] 06:20, 29 July 2017 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

KPÖ

Die KPÖ würd' ich im Wahldiagramm auch für 2017 eintragen, KPÖplus ist schon ziemlich eindeutig eine Nachfolgepartei. Grüße, --BuschBohne (talk) 19:14, 15 October 2017 (UTC)

@BuschBohne: Ich hab leider noch keine Daten für die KPÖplus, kannst du sie mir bitte verlinken?  — Johannes Kalliauer - Talk | Contributions 19:25, 15 October 2017 (UTC)

Endergebnis ohne Briefwahl hat sie bei 0,7. --BuschBohne (talk) 19:28, 15 October 2017 (UTC)
Vermutlich wäre es auch sinnvoll, bei 2013 einen Punkt für's Team Stronach anzuzeigen. Und statt "Grune" soll's wohl "Grüne" heißen. Eventuell auch NEOS/LiF auf zwei Farben aufspalten. --BuschBohne (talk) 20:55, 17 October 2017 (UTC)
Grüne werde ich ausbessern. Daten werde ich aktualisieren sobald die Endergebnisse da sind. Weitere Parteien hinzufügen muss ich schauen wie das geht, es ist mein erstes Gnuplot-Diagramm. NEOS/LIF mag ich der Übersichtlichkeit nicht aufspalten. Ob ich Stronach bzw BZÖ hinzufüge werde ich noch schauen, ansonsten kannst du einfach ein neues Diagramm machen. Quellcode ist ohnehin vorhanden.  — Johannes Kalliauer - Talk | Contributions 21:18, 17 October 2017 (UTC)
Es reicht wenn du den Quellcode auf File:Wahlergebnisse_aut2017.svg änderst ich erstell dann die Grafik mit den geänderten Quellcode neu.  — Johannes Kalliauer - Talk | Contributions 21:19, 17 October 2017 (UTC)
@BuschBohne: https://upload.wikimedia.org/wikipedia/commons/6/66/Wahlergebnisse_aut2017Full.svg  — Johannes Kalliauer - Talk | Contributions 11:02, 21 October 2017 (UTC)
Achtung: Die 4%-Hürde wurde erstmals 1994 angewandt, zuvor war nur der Gewinn eines Grundmandates maßgeblich. --BuschBohne (talk) 14:10, 21 October 2017 (UTC)

Könntest du vielleicht noch zwei Diagramme erstellen, nur mit den Werten von jeweils SPÖ und FPÖ um diese zwei Diagramme zu ersetzen? --BuschBohne (talk) 16:22, 20 October 2017 (UTC)

Vielleicht wäre es für diese Diagramme besser, die Y-Achse bei 0 starten zu lassen. --BuschBohne (talk) 21:47, 21 October 2017 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

File:SVG 3 paths BugSolved.svg

Hey JoKalliauer, ich glaube hier irgendwas zusätzlich mit einem schwarzen Viereck zu erklären macht überhaupt keinen Sinn... weniger ist mehr (wenn es denn sein muss reicht hier ein simpler erklärender Satz, es wurde hier nur äußerst einfach der Bug mit gleichen Quadraten aufgezeigt). Des Weiteren ist dein Präfix Bezeichnung "BugSolved" sehr unglücklich (ansonsten hätte ich eine andere Datei von dir schon als Ersetzung genommen jedoch war mir der Name zu doof), denn jede Datei ist ohne Bugs zu erwarten und der Renderer wird auch ab und zu gefixt (was die Bez. zusätzlich irritierend macht). Nichtsdestotrotz danke für dein Effort in der Sache. Einen schönen Advent -- User: Perhelion 23:31, 9 December 2017 (UTC)

Danke für dein Feedback.
Hätte ich ein Viereck gemacht wäre es tatsächlich sinnlos, jedoch habe ich drei Vierecke, dies kann man vollautomatisch mit https://jakearchibald.github.io/svgomg/ machen, also ich habe keinen neuen Code geschrieben:
<path d="M0 0h300v300H0zM300 0h300v300H300zM600 0h300v300H600z"/>
Generell finde ich den Bug Librsvg_bugs#Hairline_cracks nicht wirklich relevant, mir wäre er zumindest noch nicht in realen Dateien untergekommen.
 — Johannes Kalliauer - Talk | Contributions 00:00, 10 December 2017 (UTC)
Ja der Bug ist in der Tat trivial und hatte jetzt auf der Bug-Seite überproportionale Aufmerksamkeit. Dass der Bug bei vereintem Pfad nicht auftritt ist gerade so erwähnenswert (ein kleines Charakteristikum das eigtl. erwartungsgemäß ist). -- User: Perhelion 00:17, 10 December 2017 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

File:Image-Tmi-2 schematic-fr Path.svg

Hello.
First, read carefully please the description of by= in {{Derived from}}. Second, why did you create this new File: item at all? There is a problem with Adobe Inc. shit somewhere in revisions of File:Image-Tmi-2 schematic-fr.svg, but this site has a large crowd of sysops – it’s their job, these janitorial functions. Don’t please distract your valuable resources to it. Incnis Mrsi (talk) 21:23, 18 January 2018 (UTC)

There are many templates, I sometimes mess up between them, thanks for telling me. :-)
So File:Image-Tmi-2 schematic-fr Path.svg has to get deleted due to font-copyright-Problem of Adobe Inc. and File:Image-Tmi-2_schematic-fr.svg should be overwritten with File:Image-Tmi-2_schematic-fr_Text.svg?
 — Johannes Kalliauer - Talk | Contributions 21:38, 18 January 2018 (UTC)
Himmel OMG… didn’t you envisage that total deletion of Image-Tmi-2_schematic-fr.svg will destroy the last vestige of visible authorship claim for Kimdime? In case of revision deletion, SVGs with Adobe font will be inaccessible, but https://commons.wikimedia.org/w/index.php?title=File:Image-Tmi-2_schematic-fr.svg&action=history will persist… verunderstand? Incnis Mrsi (talk) 21:46, 18 January 2018 (UTC)


PS I am just a stupid user, who wrote a script, that starts 1)Inkscape 2)scour 4)svgcleaner 5)svgo. When you edit some files, you know what they change. It is just comparing input with output.
Because of your request on Commons:Deletion_requests/File:Test.svg. If you want to delete an old version you have to start a DeletionRequest (DR) or ask any admin to delete it. (see: User_talk:Jcb/archive/18#Delete_of_Fileversions)
Himmel...are you German speaking? If so we could talk German.
I ment I would upload a new version to File:Image-Tmi-2_schematic-fr.svg and then delete File:Image-Tmi-2_schematic-fr_Text.svg as a duplicate.
 — Johannes Kalliauer - Talk | Contributions 21:52, 18 January 2018 (UTC)
Unfortunately, don’t know much German, but can remember that in a Jaroslav Hašek’s story an Imperial Austrian officer exclaimed “Himmeldonnerwetter”. As for SVG pollution with copyrighted fonts, I expect that you’ll find many live examples with Arial and similar stuff. I didn’t hunt for it systematically any only excised copyrighted items when observed them in the code. Incnis Mrsi (talk) 10:41, 20 January 2018 (UTC)
In my opinion real text with font-family="ArialMT" is ok, because 'ArialMT will substituded in the Rendering by DejaVu Sans (also Liberation Sans might be a better choice).
But if ArialMT is converted to Path as in File:Image-Tmi-2_schematic-fr_Path.svg it is a copyright-problem and should be deleted.
 — Johannes Kalliauer - Talk | Contributions 10:58, 20 January 2018 (UTC)
Hi, I received a notification. Sorry didn't read the whole discussion. I think my contribution to this file is basically a translation. I won't take offence if my attribution disappears. RegardsKimdime (talk) 14:10, 21 January 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

Graphics village pump

Hello.
Could you watch Commons: Graphics village pump #File:Envelope cast.svg, please? I currently can’t talk anymore, it’s past midnight in Russia. Incnis Mrsi (talk) 21:24, 27 January 2018 (UTC)

User:Perhelion fixed the file and I repaired the Gnuplot-Source-Code, now the Gnuplot makes one plot with 100 red Lines instead of 100 Plots over each other with one red line each. Now Gnuplot would create a valid file (without postprocessing).  — Johannes Kalliauer - Talk | Contributions 00:24, 28 January 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

Neues Problem

fällt mir seit gestern auf: die diversen von Igen erzeugten Blöcke ragen nun über den Rand der "Information" hinaus, es gibt neue Zeilen wo bisher keine gewesen sind, zT geraten Texte übereinander. Ich konnte noch nicht herausfinden woran das liegt, ist aber ein unhaltbarer Zustand. Kannst du etwas finden? -- sarang사랑 10:09, 24 April 2018 (UTC)

@Sarang:<span style="float:left;height:1.2em;vertical-align:middle">{{{p|}}}<!-- soll geändert werden auf <span style="vertical-align:middle">{{{p|}}}<!-- JoKalliauer (talk) 16:49, 24 April 2018 (UTC)
Der Code sollte von
<span style="float:left;height:1.2em"><!-- 
-->{{Created with Inkscape|v}}<!--
--></span><!--

--><noinclude><br style="clear:both"/>
----
--some text--
----
</noinclude>

auf

<span><!-- 
-->{{Created with Inkscape|v}}<!--
--></span><!--

--><noinclude><br style="clear:both"/>
----
--some text--
----
</noinclude>

geändert werden.

JoKalliauer (talk) 16:53, 24 April 2018 (UTC)

Weiterdiskussion auf Template_talk:Image_generation#currently_not_working JoKalliauer (talk) 17:03, 24 April 2018 (UTC)
Danke Johannes; ich weiss immer noch nicht warum es plötzlich nicht mehr funktioniert hat. Wenn es mit dieser <span> Änderung besser geht - o.k.; aber das kann nichts damit zu tun haben dass die diversen boxes ausserhalb der Information-box erscheinen, und zT den Text der licence überschreiben. Wer oder was auch immer es gewesen ist, es ist inzwischen wieder repariert worden und alles sieht wieder gut aus (ev. nach purge).
Ich nehme deinen Änderungsvorschlag in die sandbox, für das baldige nächste update. Gruss -- sarang사랑 05:12, 25 April 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

File:History of the Universe-zh-hant Workaround.svg

 
File:History of the Universe-zh-hant Workaround.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 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!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Glrx (talk) 21:30, 28 April 2018 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

viewBox, width, and height

On 2 April, you said

Ich bevorzuge viewBox, weil im Browser dann das Bild genau hineingefittet wird (zu kleine Bilder sieht man groß genug um selbst Rundungsfehler durch CleanUp zu erkennen, zu große Bilder sieht man das ganze Bild ohne zu scrollen)
Bei dem Bild kam der Wunsch die Datei zu bereinigen, deshalb hab ich Scour im "aggressiven Modus" (inklusive --enable-viewboxing) durchlaufen lassen. Ob man viewBox bevorzugt oder nicht ist mMn Ansichtssache. Bei eigenen Bildern verwende ich viewBox (ohne height und ohne width) eigentlich immer.

but you just edited File:History of the Universe lang.svg and inserted a fixed width and height despite the file having a viewBox attribute. It doesn't make any difference to MW software today, but setting width and height to something other than 100% means the file will not do the right thing when inserted with the HTML object element. Glrx (talk) 15:03, 29 April 2018 (UTC)

@Glrx: Yes you can remove that, I forget to remove it. I used it because resolution with 5500 is a bit high, and https://commons.wikimedia.org/w/index.php?title=Commons:Commons_SVG_Checker&withJS=MediaWiki:CommonsSvgChecker.js as well as http://tools.wmflabs.org/svgcheck/ does show in this resolution of the viewbox, which is too large for my notebook (I know you can scoll out but 5500 is in my opinion very huge). I height and width for debugging reasons, so please remove it in the next edit. JoKalliauer (talk) 16:37, 29 April 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

File:Image-Tmi-2 schematic-fr Path.svg

 
File:Image-Tmi-2 schematic-fr Path.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 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!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Glrx (talk) 16:18, 29 April 2018 (UTC)

@Glrx: File:Image-Tmi-2_schematic-fr.svg used font-family="'Myriad-Roman'", which is not available on commons therefore only File:Image-Tmi-2 schematic-fr Path.svg is identical to the original (the Original has already the converted the text to path). For the text-version I replaced the font with font-family="UnGraphic" which look's similar, but 'TOUR DE RÉFRIGÉRATION' was much too large therefore I used the smallest sans-font in File:MediaWiki_SVG_font_list_sans.svg (ordered in length of the characters), therefore it has a mixture of fonts which I would not recommend. I though I discus it first with you and then we both might come together to a conclusion and we summarise the conclusion in the official discussion for the administrators. JoKalliauer (talk) 16:48, 29 April 2018 (UTC)

I do not see a benefit in keeping the path text version. It may be an exact rendering, but an exact rendering is not needed. We don't need many copies of the essentially the same thing.
The fonts need not closely match. They are used as labels rather than calligraphic art.
Consider that images on Commons are intended to rendered everywhere (not just on Commons with RSVG). Yes, using a font such as "UnGraphic" may make the image work on Commons, but my machine doesn't have that font, so when I look at the Tmi-2 SVG in my browser, "TOUR DE RÉFRIGÉRATION" doesn't fit. The goal should be to make the SVG render reasonably with most user agents. That means one cannot rely on any one font being available. Images should render reasonably with the fallback fonts. I am guilty: I spent a long time using &thinsp; and Commons skinny fonts (font-family="Bitstream Charter") trying to keep the text in File:Proton proton cycle.svg within the boxes; then the font disappeared from Commons (look at hep now).
If the problem is to fit the line, then we could use a smaller font, we could avoid using all uppercase characters (e.g., the buildings could be in a bold font rather than uppercase), or we could use two lines. There's also textLength and lengthAdjust, but that's just asking for trouble.
File:Image-Tmi-2 schematic-fr Path.svg should be deleted. You should copy the SVG from File:Image-Tmi-2 schematic-fr Text.svg to File:Image-Tmi-2 schematic-fr.svg, and then File:Image-Tmi-2 schematic-fr Text.svg should be deleted as redundant. (Sometime File:Image-Tmi-2 schematic-fr.svg should be renamed to File:Tmi-2 schematic-fr.svg.)
Glrx (talk) 17:54, 29 April 2018 (UTC)
As written in my text above I changed "TOUR DE RÉFRIGÉRATION" to the smallest font font-family="Ubuntu Condensed" font-stretch="condensed", therefore I used two different fonts in the same file, which doesn't look nice. And if you do not have the font, font-stretch="condensed" should still work. If you do not have a Ubuntu Condensed installed you can download it from https://design.ubuntu.com/font/ . JoKalliauer (talk) 06:25, 30 April 2018 (UTC)
Do you know why https://commons.wikimedia.org/wiki/Commons:Commons_SVG_Checker?withJS=MediaWiki:CommonsSvgChecker.js&checkSVG=File:Proton_proton_cycle.svg says WARNING in <g>: Font type Bitstream Charter is not available in Wikimedia software. It will be rendered with minor differences by Wikimedia's SVG renderer. See https://meta.wikimedia.org/wiki/SVG_fonts for details. JoKalliauer (talk) 06:25, 30 April 2018 (UTC)
There is a hep label in the proton–proton illustration; that's the line that RSVG now renders outside the box.
Labels should have plenty of room so they can be translated.
Using special fonts is not a general fix. Most operating systems will not have "Ubuntu Condensed", and most users would not bother to download an uncommon font (even if free) just to make an illustration work. Commons should have SVG files that work out of the box most of the time. Tmi-2 Text did not work out of the box when I loaded into Chrome, Edge, or Firefox; the label touched the cooling tower walls. Making an illustration work out of the box means using ordinary fonts. I love Palatino, Berkeley, and Tekton, but when it comes to SVG illustrations, it can be better to use others.
Yes, I know why the Commons SVG Checker issues the warning message, I know the Checker tests some font names multiple times (e.g., "DejaVu Sans Mono"), and I know that the Checker uses a linear search instead of a faster JavaScript object.
No, I do not know why Commons dropped Bitstream Charter. It used to be on Commons,[2] and that is why I used it. You noticed Bitstream went away. Why Bitstream fonts are gone doesn't matter to me; they are just gone.
The French Wikipedia redirects fr:Tour de réfrigération to fr:Tour aéroréfrigérante which also uses tour de refroissement (which en.Wikt says is the translation). cooling tower (Q193886) gives all three translations.
Glrx (talk) 17:38, 30 April 2018 (UTC)
@Glrx: I'm not shure if Commons really "dropped Bitstream Charter" see c:File_talk:Meta_SVG_fonts.svg. (There might be some issues with Commons-Checker.) JoKalliauer (talk) 22:10, 2 May 2018 (UTC)
I'm guessing it was dropped by its absence on the list and the overflowing line in the illustration, but I don't know for sure. In many ways, it does not matter. Even if Commons has a font and librsvg knows to use it, that does not mean the typical Windows, Mac, or Unix user has the font installed on his system. Glrx (talk) 16:14, 3 May 2018 (UTC)
I am not believing the Commons-Checker according to available fonts, check File:MediaWiki_SVG_font_list_sans.svg the Fonts from "Kedage" to "Waree" are rendered with the default fallback-font (DejaVu Sans), but without any warning of Commons Checker. JoKalliauer (talk) 22:04, 3 May 2018 (UTC)
Commons SVG Checker's list of fonts is a snapshot of https://noc.wikimedia.org/conf/fc-list ; the JavaScript source gives the regex it used to process fc-list. The current version of fc-list does not have "Kedage", "Mallige", and "TAMu*" anymore, so those should fail. The curent file has "Kacst*" with styles Medium, Regular, KacstScreen, but only "KacstQurn" and "KacstTitleL" use style Regular (as second option). "Guseul", "Lohit Oriya", "Lohit Telugu", "mry_KacstQurn", "TAMu" has style Regular. "Waree" has styles Bold, BoldOblique, Book, Oblique. Fonts that have style Regular should work, but maybe the Latin characters of some fonts use the same Latin characters as RSVG fallback (or use SVG's character fallback). Maybe RSVG is running off a different list. In any event, the conclusion is Commons SVG Checker does not have an accurate font list. Glrx (talk) 01:41, 4 May 2018 (UTC)
Looks like fc-list is generated by Unix command fc-list (man 1). See example output here. Going to https://noc.wikimedia.org/conf/ says the fc-list file is "dynamically generated" and "perfectly up-to-date". Glrx (talk) 18:36, 4 May 2018 (UTC)
@Glrx: But https://gerrit.wikimedia.org/g/operations/mediawiki-config/+blame/master/fc-list?blame=1 looks like it was edited by some users? If more problems occour we might should update https://commons.wikimedia.org/wiki/MediaWiki:CommonsSvgChecker.js JoKalliauer (talk) 10:44, 5 May 2018 (UTC)
I think fc-list is just a status list rather than the database of installed fonts; editing fc-list doesn't seem to make sense; there's a library for font selection that should use the fonts that are actually installed. I'm slightly curious about an accurate font list for Commons. Updating Commons SVG Checker's list would not hurt, but we don't have an accurate list. Glrx (talk) 13:55, 5 May 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

File:LibrsvgBug T193929.svg

 
File:LibrsvgBug T193929.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 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!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Glrx (talk) 00:14, 6 May 2018 (UTC)

Deleted because it was not a librsvgbug, see phab:T193929 for details.  — Johannes Kalliauer - Talk | Contributions 19:07, 6 June 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

File:Antu application-pdf.svg

Hallo JoKalliauer, ich versuche zu verstehen, warum Du meine Änderungen an File:Antu application-pdf.svg rückgängig gemacht hast und die Datei wieder in Category:Uncheckable SVG created with Other tools:Antu icons einsortiert hast. Die Datei ist nicht mehr uncheckable, Kannst Du das bitte erklären? --Sebastian Wallroth (talk) 10:02, 6 May 2018 (UTC)

@Sebastian Wallroth: Sorry, mein Fehler, dachte das Skript hat die Kategorie unabsichtlich entfernt, hatte zu wenig aufgepasst. JoKalliauer (talk) 10:07, 6 May 2018 (UTC)
Ach, dass ist mir auch schon passiert. Grüße aus Berlin! --Sebastian Wallroth (talk) 11:41, 6 May 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:41, 22 March 2019 (UTC)

CDATA

Hallo Johannes, in den letzten Tagen hast du aus einer Menge Dateien das PGF CDATA entfernt. Meine Meinung dazu: wenn es sich um eine Datei handelt die oft (oder sonstwie wichtig) eingebunden ist, wird das downloading durch die drastische Verkleinerung gringfügig beschleunigt; wenn das nicht der Fall ist, die Datei also nur gelegentlich mal angesehen wird, bringt eine solche Qualitätsverbesserung keinen Nutzen. Ich empfehle also, jedesmal abzuwägen ob die Erzeugung so einer weiteren Datei, eines besseren Duplikats, gerechtfertigt ist. Aber auf jeden Fall sollte das PGF-tag aus der Beschreibung entfernt werden! Fallls du meinst, mache ich eventuell noch ein tag "...enthielt PGF" – was meinst du?. -- sarang사랑 12:51, 9 June 2018 (UTC)

I doubt removing PGF CDATA has much of an impact on download speed. The SVG files are converted to PNG files at the server farm, and then the PNG files are cached for subsequent requests. A smaller SVG file will take less time for the server to read, but once converted, the SVG files need not be read again.
That said, I have no objection to removing the PGF CDATA; to most users it is dead weight.
I do object to other "optimizations" that affect the organization of the SVG file. The goal should not be an optimized SVG file but rather a clean SVG file.
Glrx (talk) 13:52, 9 June 2018 (UTC)
@Sarang: Yes I know "~" should be deleted, but in this case, I choose to parallel process files, therefore I first add Igen to several files, then I download the file, then I check again if all errors are removed, and remove the "~" again. I think it is not a problem to keep ~ for a few days. (I will clean the file-description-pages up upon myself.) "contained PGF" does not make sense to me, as long as those data are really useless, as I assume?  — Johannes Kalliauer - Talk | Contributions 14:26, 9 June 2018 (UTC)
@Glrx: Everytime the SVG is requested in a new size it has to be read again, or if someone "?action=purge" it, both does not occur that often, but files are often copied several times within Wikipedia (f.e translation to different language).
@Sarang, Glrx: However: In my opinion Category:SVG files with errors should be (with view exeptions) empty, because files might be invalid, but they should not contain errors (I mean real errors, which won't render correct, might not correlate with W3C-errors. Errors like links to not embedded pictures, or syntax-mistakes, or foreignObject only few Software knows, wrong MIME-type, missing xmlns...). As long as Adobe files with CDATA blocks is a subcategory of SVG files with errors, I think the files should be reuploaded to reduce the files in SVG files with errors, if we change categories, I would think differently.
 — Johannes Kalliauer - Talk | Contributions 14:26, 9 June 2018 (UTC)
@Sarang: Should Adobe files with CDATA blocks be a subcategory of SVG media for cleanup?  — Johannes Kalliauer - Talk | Contributions 12:20, 10 June 2018 (UTC)
I would suggest: no. Neither I think it the best idea to subcategorize them to SVG files with errors. It is of some interest how many huge files are around with these useless blocks, but it is not a real error, it's just ... filling the data bases. IMHO it is enough when the CDATA category is a subcat of the Adobe files. -- sarang사랑 12:45, 10 June 2018 (UTC)
Totally agree: Now Adobe files with CDATA blocks is a subcategory of SVG files with errors and therefore a subsubcategory of SVG media for cleanup, which does not make much sence as you said. Removing SVG files with errors on Adobe files with CDATA blocks makes sense to me.  — Johannes Kalliauer - Talk | Contributions 12:54, 10 June 2018 (UTC)
Yes, PGF CDATA blocks are not errors just like RDF, sodipodi, and chem elements are not errors; PGF data just has little value.
Please do not switch to English on my account. Glrx (talk) 18:11, 10 June 2018 (UTC)
Ich habe jetzt die Kategorie SVG files with errors(und somit auch SVG media for cleanup) entfernt: siehe history  — Johannes Kalliauer - Talk | Contributions 18:22, 10 June 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:45, 22 March 2019 (UTC)

RSVG

ich habe ein neues Igen hochgeladen, und konnte den workaround in RSVG Bug wieder entfernen. Falls dir auffällt dass was nicht stimmt, bitte um Info. Danke -- sarang사랑 13:09, 9 June 2018 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:45, 22 March 2019 (UTC)

Archived page

I see you recently started a new section on an archived page. Figured you might want to know. - Jmabel ! talk 21:40, 11 June 2018 (UTC)

@Jmabel: I think User_talk:Rillke is the recent page. (It redirects to User_talk:Rillke/Discuss/2016). — Johannes Kalliauer - Talk | Contributions 21:49, 11 June 2018 (UTC)
I think what may be more germane is that Rillke hasn't edited Commons in over 2 years. - Jmabel ! talk 22:29, 11 June 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:45, 22 March 2019 (UTC)

File:Human 100 100000.svg

Why did you add SVG compatibility issues to File:Human 100 100000.svg]? Is it a former bug?  — Johannes Kalliauer - Talk | Contributions 20:09, 20 June 2018 (UTC)

  • Yes it wat tagged at 2012. I removed tag since it is no longer valid. --Nevit Dilmen (talk) 14:09, 21 June 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:45, 22 March 2019 (UTC)

Hi! It's me!

When using the cleanup.js tool, which one should I click? cleanup JS, fast cleanup TS (new), or cleanup TS?--Jeromi Mikhael (talk) 06:29, 23 June 2018 (UTC)

@Jeromi Mikhael: I think there is no "right" one, I am using User:Perhelion/simpleSVGcheck.js (see User:JoKalliauer/common.js), (as far as I know) this is developed by User:Perhelion (with some input from User:Sarang). Since you are using a tool of User:Magog the Ogre: I would ask User talk:Magog the Ogre.  — Johannes Kalliauer - Talk | Contributions 08:37, 23 June 2018 (UTC)
@Jeromi Mikhael: TS is better. I kept JS around only by popular demand. It's more aggressive in the changes it makes, but it's buggy and fixes fewer problems. Magog the Ogre (talk) (contribs) 17:14, 23 June 2018 (UTC)
@Magog the Ogre: Umm, the fast one or the normal one?--Jeromi Mikhael (talk) 06:31, 24 June 2018 (UTC)
@Jeromi Mikhael: The normal one of course. I personally using a fork of Magogs version for improvements and testing, so only the JS version. The TS version is not necessary better. The more features should be ported to the JS version too (I personally don't see a real advantage of a TS version, maybe it is the better knowledge of PHP by Magog). -- User: Perhelion 23:00, 27 June 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:45, 22 March 2019 (UTC)

File:Bronze-service-star-3d-vector.svg

Hey, thanks! That looks so much better at reduced sizes now! — fourthords | =Λ= | 15:42, 2 September 2018 (UTC)

@Fourthords: I did a "shitty" repair, I deleted some blurs and I think I reduced one blur, but the whole picture should be redrawn in my opionin, since it ist badly traced (try zoom in or look at 1.038 × 1.024 Pixel-PNG, and take a closer look at the edges of the star. Reducing file size is just done, by using three fully-automatic optimizers scour, svgcleaner, svgoptimizer. Just reducing file-size is generally [not really a valid reason for]/[not worth] reuploading.  — Johannes Kalliauer - Talk | Contributions 16:25, 4 September 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

lang=fa in infobox image

Change |image=xyz.svg to |image=[[File:xyz.svg|lang=fa|200px]] Glrx (talk) 15:50, 19 September 2018 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Text rendering

Hallo Johannes, du bist doch ein Experte fur bugs. Der Benutzer Istkart hat Abertausende suboptimaler Karten hochgeladen, alle mit kyrillischen Texten. Von 09-2012 bis 02-2015 hat er Esri-ArcMap verwendet, und alle Texte in diesen unzahligen Karten werden nicht gerendert. Kannst du ermitteln, woran das liegt (wenn es kein zu grosser Aufwand ist!), eventuell bedarf es einer Subkategorie fur diesen Fehler. Gruss -- sarang사랑 07:05, 20 September 2018 (UTC)

(@Sarang:)
Die Texte werden gerendert, nur sehr in­ak­ku­rat (phab:T36947, hab noch nie ein so "schönes" Bug-Beispiel gesehen.). Er verwendet font-size="1" für alle Texte für alle seine SVG-Karten, die Genauigkeit ist bei Schriften unter 25px schlecht, siehe File:Fonttest-Kerning.svg. Der Bug wurde schon von librsvg (angeblich/vermutlich) behoben phab:T36947#4078851, @AKlapper (WMF): nur gehört librsvg auf Wikimedia upgedated phab:T193352.
Also ist der Text kein Fehler von Istkart (sonderm vom Renderer), aber die Bilder sind nicht richtig ArcMap eingebunden xlink:href="data:;base64, iVBORw0KGgoAAAANSUhEUgAA..., korrekt ist aber xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAA... phab:T5537, wobei derzeit kann man solche Bilder auf Wikimedia gar nicht mehr hochladen (glaub Sicherheitsgründe).
 — Johannes Kalliauer - Talk | Contributions 15:39, 20 September 2018 (UTC)
@JoKalliauer: Wie bereits von Dir zitiert: https://phabricator.wikimedia.org/T193352#4166886 . Gibt es eine Frage, oder was war die Intention des Pings? --AKlapper (WMF) (talk) 15:48, 20 September 2018 (UTC)
@AKlapper (WMF): Sorry, hab zu wenig Ahnung von Abhänigkeiten/Debian-Paketen, dass ich das Problem nicht verstehe, und es mir folgedessen nicht gemerkt hatte(und auch nicht nochmal gelesen hatte). Danke für die Antwort  — Johannes Kalliauer - Talk | Contributions 15:54, 20 September 2018 (UTC)
@JoKalliauer: Ah. Heh. :) Okay. Und ich bin oft sehr schlecht im Fragen rauslesen wenn sie nicht total explizit sind, daher hatte ich nachgefragt... der letzte Kommentar in dem Ticket macht etwas Hoffnung dass das Problem in den naechsten Monat vielleicht in Debian geloest wird. --AKlapper (WMF) (talk) 16:00, 20 September 2018 (UTC)
Yes, the font size is an issue on almost all the labels, but there are also logical errors in the maps. Consider File:Historical map of Greece 1200 BC.svg. The svg element has width="841.49291pt" height="595.50236pt" viewBox="0 0 841.49291 595.50236", but text is intended to the left (negative x) and above (negative y) of the viewBox. In addition, clip paths exclude the text. For example,
<clipPath id="SVG_CP_7">
	<path d="M0,595.50236L0,0L841.49291,0L841.49291,595.50236L0,595.50236z"/>
</clipPath>
<g font-family="'Arial'" font-size="1" kerning="0" font-weight="400" fill="#0000C8" clip-path="url(#SVG_CP_7)" >
	<text text-anchor="start" transform="matrix(6.83814 0 0 6.84064 678.41548 -6.4901)" >
		<tspan direction="ltr" unicode-bidi="embed" x="0 ">2</tspan>
		<tspan direction="ltr" unicode-bidi="embed" x="0.52651 ">9</tspan>
		<tspan direction="ltr" unicode-bidi="embed" x="1.10567 ">°</tspan>
		<tspan direction="ltr" unicode-bidi="embed" x="1.52687 ">0</tspan>
		<tspan direction="ltr" unicode-bidi="embed" x="2.10603 ">&apos;</tspan>
		<tspan direction="ltr" unicode-bidi="embed" x="2.26398 ">0</tspan>
		<tspan direction="ltr" unicode-bidi="embed" x="2.84314 ">&quot;</tspan>
		<tspan direction="ltr" unicode-bidi="embed" x="3.2117 ">E</tspan>
	</text>
</g>
The 29°0'0" is intended to be 6.83814 pixels tall with text anchor at (678.41548, -6.4901), so all the text is outside the viewBox. In addition, SVG_CP_7 clips everything whose y is less than 0. The clip paths are overkill.
As a side note, font-size should be used instead of scaling with a transform. The direction is not needed, and the unicode-bidi="embed" is pointless when the characters are individually placed in their own text chunks. It is also pointless because all the characters are either left-to-right or neutral; there will not be any direction changes. It appears to be an effort to defeat any Unicode reordering. Also, text-anchor="middle" is a more appropriate way to deal with differing font metrics than explicit placement of each character.
<text x="680" y="-6.5" font-size="7" fill="#0000C8" text-anchor="middle">29°0'0"</text>
Glrx (talk) 16:53, 20 September 2018 (UTC)
@Glrx: Thanks. I didn't look that close into the file (I just do some halfautomatic scriptprozessing). Now I see there are several more things to improve.  — Johannes Kalliauer - Talk | Contributions 21:01, 20 September 2018 (UTC)
@Sarang: In der SVG maps showing history in Russian gibt es über 200 *.jpg, kann man die mit einem Batchprozess nach Maps showing history in Russian verschieben?  — Johannes Kalliauer - Talk | Contributions 16:33, 21 September 2018 (UTC) 0   Done (0 maps) -- sarang사랑

Da bist du viel fleissiger gewesen als ich dir zumuten wollte! Danke.
Unser Kyrillo-Fan war ja auch immens fleissig. Von 07-2012 bis 08-2012 hat er Karten mit ArcMap 10.0.0.2414 erstellt, die den Text rendern; ab 09-2012 bis 02-2015 mit buggy ArcMap 10.1.0.3035 (der librsvg zeigt Text nicht an, der Browser (mit "edit SVG") kann das!); das scheint er irgendwann gemerkt zu haben, jedenfalls erzeugt er von 03-2015 bis 10-2016 JPG-Karten. Erst ab 11-2016 verwendet er ein SVG-tool "Qt" (? - mir unbekannt) das auch den Text anzeigt. (Ob text oder nicht ist mir ziemlich egal, mein Kyrillisch ist nicht so gut dass ich das fliessend lesen könnte.) IMHO sind seine alle Karten nicht so gut oder brauchbar, dass eine Verbesserung lohnt; ganz abgesehen von der Kyrillität! Wenigstens sind die Dateinamen in Englisch... -- sarang사랑 04:16, 22 September 2018 (UTC)

@Sarang: Tausende Dateien von Istkart habe ich als JoKalliauer2 bot-mässig korrigiert (Einige bereits gelöscht: Commons:Deletion_requests/All_uploads_by_Istkart).
Wie auch immer. Derzeit gibt es eine Lösdiskussion. @Amada44: (Auch Deutschmuttersprachler) fragt warum die Qualität schlecht ist. Magst du dort sagen warum sie nicht so gut/nichr brauchbar sind?
 — Johannes Kalliauer - Talk | Contributions 19:21, 5 March 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

File:Na+H2O.svg

Hallo JoKalliauer. Deine Version mag technisch besser sein, aber optisch überzeugt sie nicht (insbesondere bezüglich des Pluszeichens). Magst du nacharbeiten oder soll ich die Version zurücksetzen? --Leyo 12:31, 1 October 2018 (UTC)

@Leyo:
Danke für's anschreiben, wollte dich vorher auch schon fast anschreiben, dachte dann aber es war nur weil ich das Plus nicht hochgestellt hatte.
Mich überzeugt der (für mich motivationslos) gedrehte Text in der Pfad-Text-version nicht, daher habe ich das Bild in meinem zweiten Edit (30. Sep. 2018) überarbeitet. (Mein erster Edit (27. Sep. 2018) war fälschlicherweise weil ich phab:T36947 (Text-kerning) nicht gesehen habe, das habe ich jetzt in meinem dritten Edit (1. Okt. 2018) auch behoben.)
Ich hab jetzt in meinem dritten Edit (1. Okt. 2018) ein normals Plus "+" hochgestellt vorher hatte ich ein hochgestelltes Plus "⁺".
Ich hab in meinem dritten Edit (1. Okt. 2018) das Pluszeichen bei File:Na+H2O.svg sehr an deine Version angepasst siehe File:Test.svg (18:54, 1. Okt. 2018) (Dein Pfad-text ist zum Vergleich grün hinterlegt.)
Gibt es noch etwas zum nacharbeiten?
 — Johannes Kalliauer - Talk | Contributions 19:41, 1 October 2018 (UTC)
Johannes, herunter ist nicht richtig.
  <text x=" 990" y="2570">δ+</text>
SVG 1.1 <number> hat kein " ". Mit Google Chrome, " 990" → "0".
Glrx (talk) 20:15, 1 October 2018 (UTC)
Danke euch beiden! Jetzt sieht's gut aus. --Leyo 23:27, 1 October 2018 (UTC)
Thanks User:Glrx. I fixed it now. (But I find it strange since x="1,2,3" is allowed.) Do you know why the radialGradient of the upper and lower H2O one looks different to the side H2O? (seems to be a librsvgbug)  — Johannes Kalliauer - Talk | Contributions 06:41, 2 October 2018 (UTC)
I think the simple rule is no leading spaces. The list "1,2,3" may separate the elements (but not begin the elements) with whitespace or a comma surrounded by optional whitespace. See <list-of-Ts>. That's where MW ran into trouble with viewBox="0,0 , 640 320".
The difference in the radialGradient bothered me yesterday, but I haven't investigated. The effect appears in Chrome, Edge, and Firefox. My guess is a bounding box issue; the bounding box computation uses an inexact shortcut. The user agent may see the use instance, calculate the bounding box of the use prototype (say 100×100px for a 100px diameter circle), and then modify that bounding box by the transform to compute the bounding box of the instance (getting say 123×123px -- that is, it computes the bounding box of a rotated square rather than a rotated circle). The larger bounding box means the focus is closer to the perimeter and the gradient is spread out more. The bounding boxes for the two vertical instances are not expanded at all because the rotation is 0 or 180°, but the four side images are expanded. If my theory is correct, the expansion can be countered with gradientUnits=userSpaceOnUse instead of the default objectBoundingBox.
Glrx (talk) 15:19, 2 October 2018 (UTC)
It may also be the rotation of the hydrogen expanding the box. A simpler test would temporarily delete the hydrogen and see if all the oxygen then look the same. Glrx (talk) 15:36, 2 October 2018 (UTC)
I noticed that the transform is not 180° it is transform="rotate(178)", therefore I was wondering. (Or do you think rotation(0.98888...*π (rad)) is rounded to rotation(1*π (rad))?)  — Johannes Kalliauer - Talk | Contributions 15:42, 2 October 2018 (UTC)
A rotation off by 2° would make little visual difference on the bounding box. I would have made the rotations multiples of 60°, but I kept the angle distribution of the original. I was going to keep the radial distribution, but the molecules on the left were all closer than the right, so I just made them the same.
I should look at this some time; I think the hydrogens will not make a difference because I only do gradient fills on circles/atoms rather than molecules. I don't know if the SVG standard specifies how bounding boxes are computed. At the same time, I want a better understanding of symbol and marker. Glrx (talk) 16:35, 2 October 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Your edit on File:Indonesia (orthographic projection).svg

Hi. After you added colour-shading on the map, you did not include Riau Island Province (Natuna Islands). Do you mind to fix that? Thank you Badpuccini (talk) 14:09, 7 October 2018 (UTC)

@Badpuccini: Thanks   Done  — Johannes Kalliauer - Talk | Contributions 14:29, 7 October 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

LibrSVG workaround

I have just fulfilled your old request. Please check if everything is fine. --jdx Re: 11:40, 10 October 2018 (UTC)

Thanks! :-D  — Johannes Kalliauer - Talk | Contributions 20:01, 10 October 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

File:Emblema Buenos Aires 2018 youth olympic games.svg

Hi. You added PD-font to Emblema Buenos Aires 2018 youth olympic games.svg, but I don't believe that's correct:

  • It's weird for the image to be simultaneously CC-BY and PD licensed.
  • PD-font only applies to raster renderings (e.g. PNGs). Maybe you meant PD-textlogo?

TilmannR (talk) 18:55, 18 October 2018 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Creator:Johannes Kalliauer

 
Creator:Johannes Kalliauer 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 creator, 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.

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!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

~Moheen (keep talking) 05:30, 5 November 2018 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Format

Hallo Johannes, bist du ein Fan von Understrokes? Mir fällt auf dass du immer so schreibst:
File:Featured_picture_nominations_per_month_in_Wikimedia_Commons.svg. Ich finde ja, dass es mit blanks leichter lesbar sei:
File:Featured picture nominations per month in Wikimedia Commons.svg
oder Featured picture nominations per month in Wikimedia Commons.svg; auch um eine Kleinigkeit kürzer; aber vielleicht ist dir das Kopieren (aus dem Titel?) einfacher. -- sarang사랑 00:24, 24 November 2018 (UTC)

Danke, aber mich stören die Unterstriche nicht so und die unterschiede zwischen de.wikipedia und commons komm' ich auch manchmal durcheinander.  — Johannes Kalliauer - Talk | Contributions 00:07, 25 November 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

phab:T36947 SVG Text Issues

Thank you for your text fix on file:Parksosaurids-Scale-Comparison-SVG-001.svg I'm about to upload a new version of the file, is there anything I should be doing to fix the text issue in the original Inkscape file? I don't want other users to have to waste their time fixing issues like these. I also noticed that the file you edited is about 100kb smaller, is there something I can do in the original Inkscape file to achieve this? Cheers!Steveoc 86 (talk) 21:18, 26 November 2018 (UTC)

@Steveoc 86: font-sizes below 20px are buggy, thats not your fault thats a fault of inprecise rendering of librsvg
Since this Problem occured quite often there are two help pages: en:Wikipedia:SVG_help#bad_letter-alignment_on_small_font-size (english) or de:Wikipedia:Probleme_mit_SVGs#Die_Abstände_von_Buchstaben_stimmen_nicht (german).
You should not care about the file-size that much.
I would recommend to save as optimized SVG: en:Help:Inkscape#From_invalid_to_valid_SVG:_Inkscape_files (englisch) or de:Benutzer:JoKalliauer/Inkscape-SVG-Speichern (german).
Reducing file size could lead to removement of relevant data or a reduction of precission, and in some cases it breaks the file.
There is also a easy-too-use SVG-Cleaner: https://jakearchibald.github.io/svgomg/
I know more about reducing file-size, which might be more advanced.
Reducing file-size is more important for files above ~5MB.
 — Johannes Kalliauer - Talk | Contributions 00:00, 27 November 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Re: if you scrubb a svg please make the file valid on your own

Oh I would if I knew how. And it's not like the file was valid before my action either, actually it went from 2 Errors, 4 warning(s) to 2 Errors, 3 warning(s), so one less warning. Thanks for uploading the valid and smaller file size version. --Palosirkka (talk) 10:34, 30 November 2018 (UTC)

@Palosirkka:
scour -i input.svg -o output.svg  --shorten-ids --remove-metadata
  • Scour
    1. Warning: This validator does not validate Inkscape extensions properly. Inkscape-specific errors may go unnoticed.
      • will be repaired by default, but be aware that deletes some important editing-information, such as grids or guidelines.
    2. Warning: This validator does not validate RDF. RDF subtrees go unchecked.
svgcleaner input.svg output.svg --allow-bigger-file --remove-nonsvg-attributes yes --remove-nonsvg-elements yes --remove-version yes --remove-text-attributes yes --remove-needless-attributes yes
  • SVGCleaner makes a better job:
    1. Warning: This validator does not validate Inkscape extensions properly. Inkscape-specific errors may go unnoticed.
      • will be repaired by default ( --remove-nonsvg-attributes yes --remove-nonsvg-elements yes)
    2. Warning: Unsupported SVG version specified. This validator only supports SVG 1.1. The recommended way to suppress this warning is to remove the version attribute altogether.
      • will be repaired by default ( --remove-version yes)
    3. Warning: This validator does not validate RDF. RDF subtrees go unchecked.
      • will be repaired by default ( --remove-metadata yes)
    4. 2*Error: Attribute enable-background not allowed on SVG element path at this point.
      • will be repaired by default ( --remove-needless-attributes yes)
 — Johannes Kalliauer - Talk | Contributions 20:53, 1 December 2018 (UTC)
Thanks for the info! I wonder whether removing the RDF subtrees is a good idea whether that validator understands them or not. However I have no idea how widely (or narrowly) such info gets used. --Palosirkka (talk) 08:28, 2 December 2018 (UTC)
I would recommend to remove RDF-subtrees by hand, then you know if you can remove them or not. I would say on Commons about 1 out of 7 files conatain Metadata. There are different opinions about metadata on commons, since the description-page contains lizense-Information. If the autor included usefull metadata you should keep it, but in most cases it was created by the editor-software.  — Johannes Kalliauer - Talk | Contributions 08:40, 2 December 2018 (UTC)
Validator warnings are no big deal. They are not SVG errors.
I would keep all metadata. If it is the trival info stating the picture is a StillImage, then it doesn't take much space so there is little savings. If the metadata has license information, then removing that information from a CC-BY file probably violates the terms of the CC-BY license. Even if the Commons File page has license information, Commons is meant for sharing files. If somebody copies the SVG file and uses it elsewhere, the link to Commons and its license information is lost. I would prefer to see a 'bot inserting RDF statements that specify the license, the creator, the publisher, and other details. If an SVG file borrows material from other sources (e.g., a JPEG or an SVG symbol), then that borrowing should be acknowledged in the RDF.
Instead of deleting version="1.0" and inserting the SVG 1.0 DTD, I would change it to version="1.1". For all practical purposes, version 1.0 should be a subset of 1.1.
Removing sodipodi and inkscape namespaces and unused attributes can save a lot of space, but it will also remove hints about the origins of an object. Text converted to curves may have "unused" font attributes on the path element that can be used to identify the path as a text string, a copied g element may have its copy history embedded in the "unused" (and unshortened) id attribute, and the target of a use element may have attributes that state it is a standard library object such as an arrowhead. The attribute enable-background has unclear semantics and is seldom needed, so I'm OK with removing it, but it may not be wise to remove all unused attributes. The definition of unused may also be suspect. Are aria-* and data-* attributes "unused"?
Removing title elements is plain error. They are not rendered by librsvg, but they are tooltips in the browser.
An empty defs takes little space and is not an SVG error. Some of the cleaners above remove the defs element when the contents are not painted (e.g., gradient fills and clip paths). I consider that bad practice. All elements that are referenced should be in the defs element. Elements should not be painted in one part of the tree and used as a symbol in another part.
The cleaners should not flatten the hierarchy.
Yes, I want to see much smaller SVG files on Commons, and Inkscape is notoriously verbose. That does not mean the cleaners should be trying to eliminate every last byte from a file.
Glrx (talk) 19:02, 2 December 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

About your request of deletion

I was warned that you have requested the deletion of some of the images that I've translated into Basque and put in WikimediaCommons. Please, don't delete them. I tried to make them following the rules: putting the origin of the file, its author, used license and date of the original file. I used Eazydraw program to export the original PNG file to SVG format. I'm not an expert user of wikimedia commons and I might have made some mistake, but my work was serious and trying to respect the rules as far as I know. Please, if something is wrong, tell me exactly what can I do for my work not to be deleted: it is important, because these images are translated into Basque language for a educational version for children of Wikipedia called Txikipedia, the first wiki encyclopedia for children within the Wikipedia, of which I am the promotor with the help of the Basque Wikimedian Association. Best regards, --Koldo Biguri (talk) 10:01, 30 December 2018 (UTC)

@Koldo Biguri:
1)please delare which files
2)They are superseded (replaced) by better Pictures, therefore there is no need for your files any more.
 — Johannes Kalliauer - Talk | Contributions 10:45, 30 December 2018 (UTC)
@JoKalliauer: Thank you very much, Johannes. I've loaded a lot of images lately:
Thank you for your help. Maybe you can advisme me on another program to make the files properly.--Koldo Biguri (talk) 11:05, 30 December 2018 (UTC)
@Koldo Biguri: {{FakeSVG}}s are unwanted, FakeSVGs are PNG or JPEGs that are saved as SVGs.
Do not Download files ending with .svg.png, otherwise your edits might get deleted.
Generally you should distinglish between Vectorgraphics and Rastergrafics
Both are free to use.
 — Johannes Kalliauer - Talk | Contributions 15:49, 30 December 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

The bug in Decoy Receptor Figure.svg

Hi. I believe "<use xlink:href="#b"/> not supported" is a very misleading description of the bug, because <use> tags work perfectly fine in most cases. I believe that the problem is that width and height of <symbol> default to "auto" and librsvg just doesn't seem to interpret that value correctly. I haven't looked at the source code though. I'm just speculating based on what worked and didn't work as a workaround. TilmannR (talk) 14:52, 30 December 2018 (UTC)

@TilmannR: Please change the description, as you think is the best. Since you created the workaround you might know it the best.
I looked a the changes (I just replaced in your file the tabstops with spaces, to see the differences between the files better): https://www.dropbox.com/s/g8e15m923qblog3/Screenshot%202018-12-30%2017.13.42.png?dl=0
 — Johannes Kalliauer - Talk | Contributions 16:17, 30 December 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Flower icon.svg: Bugged or not?

Hi. Why is Flower icon.svg both in Pictures formerly showing a librsvg bug and Pictures showing a librsvg bug (unsolved)? Is there a second bug? Of course librsvg's blurring is awful, but if that's an unsolved bug, all images with blurs would belong in that category. TilmannR (talk) 15:09, 30 December 2018 (UTC)

I think it is a unsolved Pictures formerly showing a librsvg bug. Maybe I forgot to ?action=purge, and it was rendered with the former librsvg-version. I removed unsolved  — Johannes Kalliauer - Talk | Contributions 16:22, 30 December 2018 (UTC)
Ah, thanks now I know again why I created Pictures showing a librsvg bug (feGaussianBlur). It's because of awful rendering of blurring.  — Johannes Kalliauer - Talk | Contributions 16:40, 30 December 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Changes in Flower soft.svg

Hi. My workaround for Flower soft.svg contains a bug that I've never seen before: In the thumbnails none of the thin paths are drawn except for two of the petals (the first and third paths in the first group of paths). The paths don't have any transforms, filters, patterns or anything, so I'm really surprised that they aren't getting rendered. TilmannR (talk) 16:03, 30 December 2018 (UTC)

Apparently strokes don't get rendered, if their width is below something like 0.05px. TilmannR (talk) 16:09, 30 December 2018 (UTC)

@TilmannR: Maybe related to phab:T199618, see File:Oxygen480-mimetypes-hidef-application-x-dgn.svg, File:Oxygen480-mimetypes-image-vnd.dgn.svg, File:Oxygen480-mimetypes-image-vnd.dwg.svg for similar pictures, depending on the resolution strokes can be to thin. I don't think it is a specific stroke-with, I think it also dependes on the size of the file and the size of the rendering.  — Johannes Kalliauer - Talk | Contributions 16:26, 30 December 2018 (UTC)
I hypothesize that the limit is always a stroke width of 0.05px relative to the pixel size of the output PNG. So it's indeed not a specific stroke-with and it depends on the size of the rendering, but it's a combination of both. Perhaps librsvg rounds the stroke width to the nearest 0.1px, so it simply gets rounded down to 0 at that point. TilmannR (talk) 16:35, 30 December 2018 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Bug

Special:Diff/332822626 Wenn wir PNG und SVG vergleichen sollte auffallen, dass bei der SVG-Renderung der Schatten fehlt. Habitator terrae 🌍 15:52, 31 December 2018 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

File:Henryk Rafalski.jpg

I cannot handle this: I am no longer an OTRS team member. Ankry (talk) 13:17, 1 January 2019 (UTC)

@Ankry: Thanks, but copying it from File:Henryk_Rafalski.pdf schould be ok, since the jpg is only extracted it from the pdf. Since the pdf will get a Deletion Request, therefore there is no sence of quoting the pdf as source.  — Johannes Kalliauer - Talk | Contributions 13:20, 1 January 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

Notification about possible deletion

 
Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.

If you created these pages, please note that the fact that they have 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 them, such as a copyright issue.

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!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Affected:

And also:

Yours sincerely, — Racconish💬 17:39, 1 January 2019 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 23:58, 22 March 2019 (UTC)

File source is not properly indicated: File:Gustaf Hedström Sörböle.jpg

العربية | asturianu | беларуская (тарашкевіца)‎ | বাংলা | català | čeština | dansk | Deutsch | Ελληνικά | English | español | euskara | فارسی | suomi | français | galego | עברית | magyar | italiano | 日本語 | 한국어 | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | polski | português | português do Brasil | русский | sicilianu | slovenčina | slovenščina | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
A file that you have uploaded to Wikimedia Commons, File:Gustaf Hedström Sörböle.jpg, is missing information about where it comes from or who created it, which is needed to verify its copyright status. Please edit the file description and add the missing information, or the file may be deleted.

If you created the content yourself, enter {{Own}} as the source. If you did not add a licensing template, you must add one. You may use, for example, {{self|GFDL|cc-by-sa-all}} or {{Cc-zero}} to release certain rights to your work.

If someone else created the content, or if it is based on someone else's work, the source should be the address to the web page where you found it, the name and ISBN of the book you scanned it from, or similar. You should also name the author, provide verifiable information to show that the content is in the public domain or has been published under a free license by its author, and add an appropriate template identifying the public domain or licensing status, if you have not already done so.

Please add the required information for this and other files you have uploaded before adding more files. If you need assistance, please ask at the help desk. Thank you!

Hedwig in Washington (mail?) 08:07, 9 January 2019 (UTC)

@Hedwig in Washington: It's description says: "Swedish politician from late nineteenth century", therfore it will be more than 120Years old -> {{Pd-old}} ?  — Johannes Kalliauer - Talk | Contributions 16:50, 9 January 2019 (UTC)
Some go with 1890, some with 1892, 1896, etc. The problem is that (IN THEORY!) the copyright could still be intact in the US. Without better date or death date of the subject I have no idea how to justify keeping the file. Maybe the guys on SV-Wiki could help? --Hedwig in Washington (mail?) 17:06, 9 January 2019 (UTC)
@Hedwig in Washington: I think {{PD-old-assumed}} should fit.  — Johannes Kalliauer - Talk | Contributions 17:26, 11 January 2019 (UTC)
@: Your edit is wrong. w:sv:Gustaf_Hedström_i_Sörböle died more than 120 years ago, but the Author/Photographer maybe not, see some lines above.  — Johannes Kalliauer - Talk | Contributions 17:33, 11 January 2019 (UTC)
I did some digging and couldn't find a photographer name. Since Sörböle died in 1866, in theory, the photographer could easily have lived into the 1930 or even longer. 1866 + 60 for a 20 year old photographer would be 1940 as death date. That would be a problem with the URAA date. Bloody Nora, sometimes I really get fed up with copyright. Anyway, the probability is pretty low. I would agree with PD-old-assumed. --Hedwig in Washington (mail?) 17:54, 11 January 2019 (UTC)

No, my edit is correct under EU law with no published author And this is at least 152 years old. If you need the assumed template, this should go to a DR. -- (talk) 19:07, 11 January 2019 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

File:Antu preferences-desktop-screensaver.png

 
File:Antu preferences-desktop-screensaver.png 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 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!

Afrikaans | العربية | беларуская (тарашкевіца)‎ | български | বাংলা | català | čeština | dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | español | eesti | فارسی | suomi | français | galego | עברית | hrvatski | magyar | Հայերեն | Bahasa Indonesia | íslenska | italiano | 日本語 | 한국어 | 한국어 (조선) | македонски | മലയാളം | Plattdüütsch | Nederlands | norsk nynorsk | norsk | occitan | polski | پښتو | português | português do Brasil | română | русский | sicilianu | slovenčina | slovenščina | shqip | српски / srpski | svenska | ไทย | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Huntster (t @ c) 18:14, 14 January 2019 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

Commons:Graphic Lab/Illustration workshop

Hi, just wanted to make you aware that in this edit, you accidentally replaced the whole workshop page. Please be careful in the future and utilize the "show preview" and "show changes" buttons. Opencooper (talk) 23:01, 30 January 2019 (UTC)

@Opencooper: Thanks for telling me.
The preview would not help since I thought I edtited the section, therfore the preview would be correct. I think the problem was that I edited the section. Restarted my computer, and the text was still available and I saved it, and then I was in a hurry.  — Johannes Kalliauer - Talk | Contributions 20:29, 31 January 2019 (UTC)
Ahh yes the software loses the session information, and I've noticed if you refresh the page, the specific section seems to get lost. No worries. Happy editing! Opencooper (talk) 01:52, 1 February 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

SVG-Datei oder PNG-Datei?

Servus JoKalliauer,
zuerst eine Frage: Wäre für einen neuen WP-Artikel, ähnlich dem Artikel Parabelzirkel des Frans van Schooten, eine SVG-Datei besser als eine PNG-Datei geeignet? Falls wesentlich besser, könntest du mir dann vom Hyperbelzirkel eine SVG-Datei mit dem Dateinamen 01-Hyperbelzirkel-Frans van Schooten.svg erstellen? Mit meinem Programmen klappt das leider nicht. Mit Gruß aus München, Petrus3743 (talk) 21:05, 13 February 2019 (UTC)

Jenachdem in welchen Format du die Quelldatei hast, in dem Format solltest du es hochladen. Also tiff, PNG oder JPEG.
Des Weiteren fehlt die Genehmigung es hochzuladen. (Zustimmung der Urhebers)
 — Johannes Kalliauer - Talk | Contributions 21:15, 13 February 2019 (UTC)
@Johannes Kalliauer, ich sehe gerade, du hast mir auch schon bei meiner Datei File:01-Parabelzirkel-Frans van Schooten.png geholfen. Sie war mir ein gutes Beispiel für die Datei File:01-Hyperbelzirkel-Frans van Schooten.jpg. Ein herzliches Dankeschön für deine konstruktive Unterstützung! Mit Gruß --Petrus3743 (talk) 22:34, 14 February 2019 (UTC)
@Petrus3743: Danke für deine nette Wortwahl. Generell möchte ich dich aber darauf hinweisen, das Bücher auf Google-Books zwar kostenlos zur verfügung gestellt werden, aber nicht auf Commons hochgeladen werden dürfen, da die Autoren/der Verlag noch die Urheberrechte besitzt (auch wenn er/sie es kostenlos (temporär) auf die von ihm/ihr gewünschten Weise zur Verfügung gestellt wird) .  — Johannes Kalliauer - Talk | Contributions 17:45, 15 February 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

Removed margins

Hello JoKalliauer, "vlag" means "flag" or in German "flagge", so there is no need to "remove margins" if a flag exists out of a white field with an coat of arms on it. --D'Arch (talk) 05:44, 17 February 2019 (UTC)

This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

Translations within one SVG file with Inkscape

Hello!. Finally I add an instructions within Commons: look at this. I have suggested a set of changes to the explanations you gave me. Thanks!. --Jmarchn (talk) 18:24, 17 February 2019 (UTC)

@Jmarchn: Thanks for the info! I did not fully understand it and have to try it gain, but I'm happy there seems to be some workaround in Inkscape.
There will be also a Wikitool that can make tranlations more easy: https://tools.wmflabs.org/svgtranslate/ But it is still under heavy deleopment and just this week this prototype came out.
@Glrx: I was wrong: There seems to be a workaround to edit multilanugal files in Inkscape: Commons:Translation_possible/Learn_more#Multiple_translations_within_one_SVG_file_with_Inkscape
 — Johannes Kalliauer - Talk | Contributions 18:43, 17 February 2019 (UTC)
@Jmarchn, NKohli (WMF): I'm happy to see edits to that instructional page, but I strongly disagree with the recommendations. Language translations should not be put on separate layers (a planar translation). The given advice essentially embeds several separate images into one file. Layers bunch all the words together without separating them into translation units. Translation units are the foundation of most translation tools. See, for example, how MediaWiki translates templates. Using separate layers requires translations be done by specialists who understand XML/SVG or are skilled at a graphics editor. That makes translation inaccessible to most editors. It is better to allow the translations be done by people who know the natural languages but may have a limited understanding of SVG or limited graphics skills. Consequently, each image label/translation unit should be in a separate switch. Then each switch is a separate translation task. That has been the design philosophy of SVG Translate 1.0 (l10n; with separate files and without switch), SVG Translate 2.0 (i18n with switch), and the emerging SVG Translate 3.0 (i18n with switch).
There is a difference between "localization" (l10n) and "internationaliion" (i18n); the given advice confuses the two ideas. A localized file has only one language, and a different file would be needed for each language wiki. An internationalized file embeds many languages; the same file is used for several wikis.
To make both l10n and i18n easy, images should be designed or modified to have space for labels whose dimensions vary widely. Chinese labels can be very compact, but Malayam and Tamil labels may take lots of space. Even English can be compact compared to Spanish. Yes, multiple lines may be used by some languages, but that facility is coming in SVG 2.0; it was present in the SVG 1.2 draft. SVG 2.0 offers an SVG 1.1 compatible CSS method that can work even if browsers decline to implement the CSS portion. The graphic artist, instead of shoehorning each language and customizing leader lines, should make it easy for many languages to fit using the same leaders. That is not a skill that many artists are exercising right now. I absolutely love the images that LadyofHats produces, but those beautiful images are often sensitive to minor font changes (she often converts text to paths) and need minor graphic edits for simple translations.
I am not aware of any detailed investigation into graphics editor interaction with switch. That investigation is something that should have been a part of the SVG Translate 3.0 effort. Adding a switch translation should not lockout using Inkscape, Adobe Illustrator, or CorelDraw to touch up or correct the image. My impression is that switch will survive a trip through Inkscape, but I do not know about the other editors. Consequently, I'm leery of adding switch translations to an image somebody generated with AI; the original author may not be able to edit it. There's a way around the switch problem using XSLT, but somebody must do the work to find out what is needed and implement it. I also fear that Inkscape may flatten all style information; I think AI will keep it; I do not know about CorelDraw. These issues need investigation.
Glrx (talk) 19:50, 17 February 2019 (UTC)
@Glrx: Thank you very much for your extensive explanation!
I do not have Adobe Illustrator (€36/month) nor Corel (€664), so I do not know the possibility of creating or editing multilingual SVG files with these programs. I only use Inkscape. I explained over creating an internationalized (using your best name) SVG file. I still think that creating one layer by language (as I explained) is the best option (for most cases) with the current use of Inkscape. We hope that in the near future everything will change and my explanations will no longer be necessary. Anyway this is not my "war". Most users (including myself) opt for (or just know the possibility of) one drawing - one language (localized) thus achieving the best adjustment of tags and arrows.
PD: I'll send a message to LadyofHats for severals errors in draw File:Endocrine Alimentary system en.svg.
Jmarchn (talk) 20:49, 17 February 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

SVG-Validierung

Hallo JoKalliauer, zunächst einmal wollte ich mich bei dir für diesen Edit bedanken. Ich habe diesbezüglich eine Frage: Wie kann ich meine SVG-Dateien prüfen, ob diese valide sind, um dann diese Vorlage einzufügen? Wäre beispielsweise diese Grafik ebenfalls valide? PS: Meine Strukturformel habe ich mit dem Programm ChemDraw erstellt! Würde mich über eine Antwort sehr freuen! Viele Grüße, Chem Sim 2001 (talk) 14:29, 20 February 2019 (UTC)

@Chem Sim 2001:
Du kannst Bilder mit {{Valid SVG}} markieren.
Ob eine Datei valide ist oder nicht ist nicht wirklich relevant. Viele Dateien sind absichtlich nicht valide.
Jeder der mehr von SVGs versteht, wird dir sagen, dass das reine validieren von SVGs im Allgemeinen unerwünscht ist. (Sofern es kein Problem damit gibt.)
 — Johannes Kalliauer - Talk | Contributions 20:26, 20 February 2019 (UTC)
@JoKalliauer: Vielen Dank für deine hilfreiche Antwort. Gibt es auch eine Möglichkeit bei der SVG-Erstellung nur den Button "Diese Strukturformel wurde mit ChemDraw erstellt" einzufügen? Also ohne die SVG-Validierung davor? Chem Sim 2001 (talk) 21:02, 20 February 2019 (UTC)
@Chem Sim 2001: Verwende einfach {{Created with ChemDraw}}  — Johannes Kalliauer - Talk | Contributions 12:56, 21 February 2019 (UTC)
@JoKalliauer: Vielen Dank! Einen schönen Tag noch! Chem Sim 2001 (talk) 13:28, 21 February 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

File:Cuenca-030-031-032-033-B.svg + File:Cuenca-116-117-118-119-B.svg

Hallo JoKalliauer,

Erstmal vielen Dank für dein Review.

Ich vermute eine ganze Menge der gefundenen Fehler sind eine Folge der Lösch- und Sammelarbeiten vom svgo. Die Bitmap sind die Kontur der Städte, sie werden so vom QGIS eingebaut. Ansonst ist die Raster leer. In diesem Fall sind es 134 kB. svgo (svgoptimizer) reduziert die Größe der Datei auf weniger als die Hälfte, deswegen ist es unverzichtbar wenn man auf langsamen Internet Verbindungen warten muss, wie an vielen Orten der Welt existieren. In einer perfekten Welt würde ich die Fehler sofort beheben, aber jetzt werde ich noch auf die schnelleren Verbindungen warten.

Der große Manko von svgo, für mich, ist die Herstellung von Verbindungen zwischen Pfade (Flüsse-Tracks) die logisch miteinander nichts zu tun haben: ein Stück vom Fluß A wird vom svgo mit ein Stück von Fluß R und noch andre vom X und Z. Wenn man Fluß B etwas dunkler färben will, muss man zuerst alle seine Tracks "befreien" (ctrl+shift+K) von den anderen Flüssen und dann die "B"-Tracks vereinen (C+K) und dann färben.

Bisher habe ich keine Rendern-Fehler gesehen. Beste Grüße, --Juan Villalobos (talk) 11:41, 24 February 2019 (UTC)

@Juan Villalobos: Ich hab die Bilder so weit vereinfacht, dass sie valide sind und richtig gerendert werden. Damit sind vermutlich Funktionen verlohren gegangen, aber sie werden richtig dargestellt.
Ich hab https://github.com/JoKalliauer/cleanupSVG, welches auf svgo bassiert. Ich würde
svgo -i Input.svg -o Output.svg --disable=mergePaths
verwenden, damit werden keine Pfade verbunden.
mergePath hat auch mehrere Fehler:
also ich würde davon abraten.
Ich persönlich bevorzuge auch
 — Johannes Kalliauer - Talk | Contributions 19:53, 25 February 2019 (UTC)
Ich habe noch die Dateien aus Inkscape an denen ich es ausprobieren werde. Danke. --Juan Villalobos (talk) 10:54, 26 February 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 00:04, 23 March 2019 (UTC)

Hairline crack

Bei der Erin sehe ich den crack nicht; es erscheint mir auch als Beispiel weniger geeignet, da konnten mogliche Fehler aus der JGP-Konvertierung stammen. Viel eindeutiger sind die beiden anderen Beispiele, die nur aus primitiven rect's bestehen - mit deutlich sichtbarer Hairline. Und: was wolltest du mich fragen - ich habs nicht recht verstanden. -- sarang사랑 08:02, 10 June 2019 (UTC)

 
304
 
305
 
306
@Sarang: Bitte vergleiche die drei Versionen rechts, da sind so viele Hairline-chracks dass das Bild scheinbar eine andere Farbe bekommt.
Das Bild besteht aus 305 × 409 Pixel=124745 Quadraten. Quadrate sind besondere Rechtecke. ;-)  — Johannes Kalliauer - Talk | Contributions 08:16, 10 June 2019 (UTC)
Ich kann kaum etwas derartiges sehen; bei starkem Zoom sehe ich eine Art Artefakte, aber keine richtigen Hairlines im Sinne des bug. Bei den anderen Bildern sind sehr deutlich zu sehen, hier nur wenn man weiss worauf man achten muss.
Vielen Dank, ich weiss dass Quadrate Rechtecke sind (genauer: deren Menge angehoren).
@Sarang: Bitte um Entschuldigung, Das mit den Quadraten war nicht ernst gemeint (Wahr wohl ein blöder Scherz, sorry.). Also wenn ich das Bild in Firefox aber auch in Chrome mit viewBox="0 0 305 409" betrachte sieht man dass es hairline-chracks sind, gleiches bei Hineinzommen in Inkscape. siehe Firefox: https://www.dropbox.com/s/3blwxuc716lfphe/Screenshot%202019-06-10%2012.31.12.png?dl=0 oder Chrome https://www.dropbox.com/s/gpwbwl2jb2lk5r6/Screenshot%202019-06-10%2012.31.19.png?dl=0 oder am besten in Inkscape: https://www.dropbox.com/s/2u7bxrao5flsxc0/Screenshot%202019-06-10%2012.58.28.png?dl=0
Siehe auch die File:Test.svg#filehistory (beachte ich habe hier einen grauen Hintergrund gewählt um die Sichtbarkeit der Hairline-cracks zu reduzieren, was zu den grauen hair-linecracks beim weißen Hintergund erzeugt)
  Question Sieht bei dir
  1. https://upload.wikimedia.org/wikipedia/commons/thumb/5/52/Silversmith_BMP2SVG_accelerated-i-o.svg/305px-Silversmith_BMP2SVG_accelerated-i-o.svg.png
gleich aus? 304px und 306px haben hair-line-cracks (das schwarz scheint etwas grau), aber 305px nicht.
 — Johannes Kalliauer - Talk | Contributions 10:48, 10 June 2019 (UTC)
Auch ohne jedes Zooming erscheinen mir 304 und 306 gefadet, mit kleinen schwarzen Streuseln, also nicht nur heller sondern auch irgendwie verwaschener; 305 hingegen ist ein klares Bild. Mir ist schon klar, dass das auch einer dieser Rundungsfehler-bugs ist - aber sonst wird das wohl nur fur Experten einsichtig sein! Ich habe die Erin nicht runtergeladen sondern nur in Wikimedia betrachtet, kann sein dass sie in FF oder Chrome anders gerendert wird.
PS: Ich hab durchaus gesehen dass die Quadrate ein ;-) sind. -- sarang사랑 13:24, 10 June 2019 (UTC)
Ich dachte das die Hair-line-chracks nur bei exakt 0.5 auftreten, aber dieses Bild zeigt, dass sie auch bei vielen "zufälligen" Numern in der Nähe von 0.5 auftreten können. Ich hatte lang nicht verstanden, warum das Bild so grau gezeigt wird.  — Johannes Kalliauer - Talk | Contributions 13:38, 10 June 2019 (UTC)
@Sarang: meine Frage war warum {{F|Silversmith BMP2SVG accelerated-i-o.svg|G}} welches bei |other versions= steht, bei |description= aufscheint ? Ich weiß wie man den Fehler umgehen kann, aber für mich scheint das ein Bug zu sein? Oder ist das ein Feature?  — Johannes Kalliauer - Talk | Contributions 08:16, 10 June 2019 (UTC)
Jezt verstehe ich. Da ist dir ein lustiger Fehler passiert, du hast dem Erin-Bild den Parameter "description" folgen lassen - der gilt nun fur das Information-template des Bildes; und als spaterer Parameter ersetzt der Text Hairline crack, [[bugzilla:18936]] samt Bild den ursprunglichen Text {{Rsvg bug|description=Hairline crack, [[bugzilla:18936]]}}. Du hast auch die Warnung ubersehen "Warning: File:Hairline crack.svg is calling Template:Information with more than one value for the "description" parameter. Only the last value provided will be used.". So einfach sind manche Dinge erklarbar! Danke, keine Ursache, gern geschehen. -- sarang사랑 10:00, 10 June 2019 (UTC)
  Thank you. Danke, hatte das zweite |description= übersehen und verstand es nicht, warum es sich ändert, wenn ich die Reihenfolger der zwei Zeilen ändere.  — Johannes Kalliauer - Talk | Contributions 10:48, 10 June 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 13:38, 5 June 2019 (UTC)|clear=left

SVG Text example

You pointed me to File:Svg-text rendering test.svg. That file is confused about many issues, but I'm not sure it is worth cleaning up. Glrx (talk) 05:54, 7 July 2019 (UTC)

@Glrx: I did not even take a look into the code before, I thought it is about something else, and it reminded me on File:SVG_Test_TextAlign.svg (which (yours) is a really good example which I often use to look something up). And true, it's (the mentionded file by Jkwchui) not a good test-case.  — Johannes Kalliauer - Talk | Contributions 18:42, 7 July 2019 (UTC)
This section was archived on a request by:  — Johannes Kalliauer - Talk | Contributions 18:42, 7 July 2019 (UTC)
Return to the user page of "JoKalliauer/Archiv".