User talk:Menner

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


Welcome to Wikimedia Commons, Menner!

-- 15:15, 21 October 2011 (UTC)

Tip: Categorizing images[edit]

Afrikaans  العربية  беларуская (тарашкевіца)  বাংলা  català  čeština  dansk  Deutsch  Deutsch (Sie-Form)  Ελληνικά  English  Esperanto  español  فارسی  suomi  français  galego  עברית  magyar  íslenska  italiano  日本語  ქართული  한국어  македонски  മലയാളം  norsk bokmål  Plattdüütsch  Nederlands  norsk  polski  português  português do Brasil  română  русский  sicilianu  slovenčina  slovenščina  српски / srpski  svenska  Türkçe  українська  Tiếng Việt  中文(简体)‎  中文(繁體)‎  +/−


Hello, Menner!
Tip: Add categories to your files
Tip: Add categories to your files

Thanks a lot for contributing to the Wikimedia Commons! Here's a tip to make your uploads more useful: Why not add some categories to describe them? This will help more people to find and use them.

Here's how:

1) If you're using the UploadWizard, you can add categories to each file when you describe it. Just click "more options" for the file and add the categories which make sense:

2) You can also pick the file from your list of uploads, edit the file description page, and manually add the category code at the end of the page.

[[Category:Category name]]

For example, if you are uploading a diagram showing the orbits of comets, you add the following code:

[[Category:Astronomical diagrams]]
[[Category:Comets]]

This will make the diagram show up in the categories "Astronomical diagrams" and "Comets".

When picking categories, try to choose a specific category ("Astronomical diagrams") over a generic one ("Illustrations").

Thanks again for your uploads! More information about categorization can be found in Commons:Categories, and don't hesitate to leave a note on the help desk.

CategorizationBot (talk) 16:03, 22 October 2011 (UTC)[reply]

File:Carnot-Maschine.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

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

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

Kopiersperre (talk) 21:07, 30 July 2014 (UTC)[reply]


Hi Menner, 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:Menner/CommonsSvgChecker.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 or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 687 character 17: Bad or unnecessary escaping. - Evidence: "padmaa\-Bold.1.1",

Your CommonsMaintenanceBot (talk) at 16:13, 6 November 2015 (UTC).[reply]

Autopatrol given[edit]

Hello. I just wanted to let you know that I have granted autopatrol rights to your account; the reason for this is that I believe you are sufficiently trustworthy and experienced to have your contributions automatically marked as "reviewed". This has no effect on your editing, it is simply intended to make it easier for users that are monitoring Recent changes or Recent uploads to find unproductive edits amidst the productive ones like yours. In addition, the Flickr upload feature and an increased number of batch-uploads in UploadWizard, uploading of freely licensed MP3 files, overwriting files uploaded by others and an increased limit for page renames per minute are now available to you. Thank you. -- Rillke(q?) 16:30, 7 November 2015 (UTC)[reply]

OK hatte also keine Bezug zu meiner Frage. -- Menner (talk) 17:47, 7 November 2015 (UTC)[reply]

Hallo Menner, erstmal vielen Danke für dein Arrangement zum SVG! Wie sieht die Zukunft von deinem Tool konkret aus? Es gibt ja ähnliche oder aufbauende Tools dazu. Ich selbst habe ja auch ein geschrieben, dies würde meiner Meinung sich ebenfalls in deines voll integrieren lassen (User:Perhelion/simpleSVGcheck.js einfach Links zum W3C-Validator auf der Dateibeschreibungsseite, also man könnte einfach dein Tool mit ranhängen). In wie weit benutzt dein Tool einen W3C-Check (dann könnte ich in meinen den Link komplett ersetzen)? Sollte man nicht direkt bei Commons:SVG Check alle diese Tools verbindend erwähnen⁉ Viele GrüßeUser: Perhelion (Commons: = crap?)  10:05, 16 December 2015 (UTC)[reply]

@Perhelion: Die Zukunft meines Tools wird die Zukunft zeigen :). Der alte SVG Check ist ja erstmal nicht weg. Dadurch kann ich die aufkommenden Probleme und Wünsche bewerten ohne unter Zugzwang zu geraten. Das erste Ziel wäre somit die Bewährung in der Praxis, sprich die Kinderkrankheiten eliminieren und Grundschliff machen (z.B. Tippfehler). In etwa drei Monaten sollte das Abgeschlossen sein und grok.se sollte mir erste Metriken zur Nutzung geben sowie Feedback von Anwendern. Danach kommt die Planung und Bewertung, wie ich mit dem SVG Checker weitermache.
Parallel, jenachdem wieviel Zeit mir bleibt möchte ich noch vier aus den existierenden Bugfixes bei libRSVG reinbringen.
Da die Survey ja nun um ist kann ziehe ich auch daraus mein Urteil. Zwar wird Handlungsbedarf erkannt was SVGs angeht, jedoch nicht mit der Dringlichkeit wie ich es bewerte. Erklären lässt sich das nur dadurch das Wissenschaft und Technik kein Breitenthema sind. Noch spezieller macht es SVG, weil es hier ums Zeichnen von Grafiken geht. Das sieht man ja schon in der GWS. Und dazu wird man noch ala Featuritis von dem blöden Wunsch nach 3D-Grafiken ausgestochen. Wer soll den die Überhaupt machen? Für meinen Teil bin ich enttäuscht.
Insgesamt werde ich es daher in Zukunft gemütlicher angehen lassen. Ansonsten warten wir mal ab bis es mit SVG 2.0 knallt. Manchmal muss es eben weh tun bis etwas in die Gänge kommt.
--Menner (talk) 17:07, 16 December 2015 (UTC)[reply]
Aja danke der Ausführung. Ich benutze es nun mit Freude, dabei ist mir eine kleine Inkonsistenz aufgefallen. Wecleh eigtl. auch gleich eine Bitte in Form eines Feature-Request beinhaltet, den ich schon bei dem Vorgängermodel (von Jarry) hatte. Nämlich das Testen unter verschiedenen Auflösungen, ist zwar nicht schön aber hilfreich. ;) Hier ein Bspl. wo etwas schief ging und deine Vorschau eigtl. ok war, Version von 22:59, 20. Jan. 2016 (gequetscht, da height fehlte). OT: Leider habe ich etwas die Versions-History vollgebläht, da je komplexer, desto mehr kann man falsch machen (die Inkonistez von XML:space nervt auch ^^). LGUser: Perhelion (Commons: = crap?) 22:12, 20 January 2016 (UTC)[reply]

SVG help button[edit]

I like the idea but I am extremely unsatisfied with the positioning. Can you perhaps try to link the text SVG from the line below: Original file ‎(SVG file, nominally 959 × 593 pixels, file size: 87 KB)? If you like, I can also inject an identifying character into the MediaWiki message that your script could pick-up. Note that there are different translations for this interface text. -- Rillke(q?) 22:39, 23 December 2015 (UTC)[reply]

Hi Rillke. Currently I'm testing on the SVG Checker. Special:NewFiles offers lots examples for field testing. It has too many false positive on some details. Yet I can say that unsupported font type is the major issue. Even our experienced contributors don't get it. As thus meta:SVG fonts is the next thing I'll look at and the help button needs to wait. --Menner (talk) 07:29, 24 December 2015 (UTC)[reply]


Hi Menner, 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:Menner/commons-svg-checker.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 5 new jshint issues — the page's status is now having ERRORS. 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 or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 1 character 2: Expected a string and instead saw {. - Evidence: {{delete|reason=Own subpage. No longer needed. |subpage=User:Menner/commons-svg-checker.js|year=2015|month=December|day=28}}
  2. ISSUE: line 1 character 3: Expected ':' and instead saw 'delete'. - Evidence: {{delete|reason=Own subpage. No longer needed. |subpage=User:Menner/commons-svg-checker.js|year=2015|month=December|day=28}}
  3. ISSUE: line 1 character 9: Expected a JSON value. - Evidence: {{delete|reason=Own subpage. No longer needed. |subpage=User:Menner/commons-svg-checker.js|year=2015|month=December|day=28}}
  4. ISSUE: line 1 character 9: Expected '}' and instead saw '|'. - Evidence: {{delete|reason=Own subpage. No longer needed. |subpage=User:Menner/commons-svg-checker.js|year=2015|month=December|day=28}}
  5. ISSUE: line 1 character 10: Expected '(end)' and instead saw 'reason'. - Evidence: {{delete|reason=Own subpage. No longer needed. |subpage=User:Menner/commons-svg-checker.js|year=2015|month=December|day=28}}

Your CommonsMaintenanceBot (talk) at 08:13, 28 December 2015 (UTC).[reply]


Hi Menner, 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:Menner/commons-svg-checker.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 esprima issue — the page's status is now having ERRORS. 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 or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 1 column 9: Unexpected token |

Your CommonsMaintenanceBot (talk) at 08:13, 28 December 2015 (UTC).[reply]

graphic capable of being misunderstood: Kondensator_Zeigerdiagramm-1[edit]

Hi Menner!

At first the link to the file in question: https://commons.wikimedia.org/wiki/File:Kondensator_Zeigerdiagramm-1-.svg?uselang=de

It says "Z" at the long black vector and usually I'd assume that in this case the impediance of the whole RLC-circuit is meant. But as it is shown in the graphic it is only possible that "Z" contains the capacitance and the resistance as otherwise its imaginary part would have to be smaller. Please make clear that only the capacitance and the resistance is included in Z or change its vector to the complete impedance of the RLC circuit. Thank you :)

I think you've missed a detail. I've changed the color of the drawing. I hope its clearer now. Thanks for your comment. --Menner (talk) 07:03, 1 May 2016 (UTC)[reply]
I actually missed the detail that the XC is drawn from the top of the XL. Taking this into account, everything is fine. But it is not too easy to see.. Sorry for that.
No worries. It is not perfect yet. It is still to easy to be overseen. Yet, I don't have time to evaluate this. (I've seen your earlier drawing. You might try en:Inkscape to solve problems on your own.) -- Menner (talk) 16:26, 6 May 2016 (UTC)[reply]

Fixed SVG bugs[edit]

Hello Menner, danke für deine SVG-Bestrebungen. Mir ist jetzt nur eine Kleinigkeit aufgefallen (nach Update von librsvg). Normaler Weise werden die Duplikate von gefixten SVG nicht aufgehoben, hast du da einen besonderen Grund für? LG User: Perhelion 12:35, 10 July 2016 (UTC)[reply]

Nein, es gibt keinen Grund wofür ich das Bild aufheben möchte. -- Menner (talk) 14:47, 10 July 2016 (UTC)[reply]
Vielen Dank nochmal für deine Fixes! Die Belohnung hast du dir verdient. Es ist schon beachtlich dass dies so wenig Beachtung findet, da mit Wikimedia und Linux zusammen wirklich nicht wenig Leute betroffen sind. LG User: Perhelion 21:44, 10 July 2016 (UTC)[reply]
File:T117530 Chinatown map WV.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

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

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

User: Perhelion 18:13, 11 July 2016 (UTC)[reply]


Hi Menner, 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:Menner/CommonsSvgChecker-Development.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 or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 381 character 20: document.write can be a form of eval. - Evidence: p.appendChild( document.write( str ) );

Your CommonsMaintenanceBot (talk) at 09:14, 26 December 2016 (UTC).[reply]


Hi Menner, 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:Menner/CommonsSvgChecker-Development.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 or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 585 character 61: Missing semicolon. - Evidence: p2.appendChild( document.createTextNoed( "Loading: " ) )

Your CommonsMaintenanceBot (talk) at 12:46, 26 December 2016 (UTC).[reply]


Pressure[edit]

Hi Menner, in your figure https://de.wikipedia.org/wiki/Isentrope_Zustands%C3%A4nderung#/media/File:Isothermal_and_isentropic_process.svg the pressure unit is missing a square (meter). Regards, Holglglgl (talk) 21:56, 13 March 2017 (UTC)[reply]

Notification about possible deletion[edit]

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 see Commons:But it's my own work! for a guide on how to address these issues.

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

Affected:


Yours sincerely, DMacks (talk) 08:33, 14 October 2017 (UTC)[reply]