User talk:MichaelSchoenitzer

Archive 1, Archive 2

(Sorry to write in Engilsh)

Hi MichaelSchoenitzer. I see you've handled two permissions tickets about a bunch of photos of Stolpersteine: ticket:2017022610012902 and ticket:2017021210005544. There are, though, a lot of images of Stolpersteine which still have the "OTRS pending" template on them, see Category:OTRS pending as of 24 February 2017. Can you check if permission has been given to these as well? (Or send a reply to them asking for permission?) My German is not so good.... Thanks in advance. Trijnstel_talk 19:47, 14 March 2017 (UTC)[reply]

@Trijnstel: I added the OTRS-Info for all the files mentioned in the original ticket. After more files were uploaded the template Template:Francisco Peralta Torrejón was created for these Stolpersteine, it adds the OTRS-template automatically. This should be used for all of those files. I'm currently low in time. -- Michael F. Schönitzer 11:20, 7 April 2017 (UTC)[reply]

Thanks. I've added that template to all Stolpersteine images in that category. Trijnstel_talk 22:00, 7 April 2017 (UTC)[reply]

Awesome, thanks for the work. -- Michael F. Schönitzer 12:43, 8 April 2017 (UTC)[reply]

File:Necromanis_franconica.jpg - a different file has been uploaded on top of the old one. That causes a mismatch in mt.wikipedia, which uses the old file via a local copy under that name. The mt-copy could be deleted, if the old file would reappear in commons. Since 2016 several Wikipedias display an image that never was intended there. Could you re-upload the new file as File:Comparison - Sansanosmilus palmidens - Necromanis franconica.jpg and restore the old one? 85.182.86.148 15:09, 31 January 2018 (UTC)[reply]

Hi, that is a really weird case. Sadly I can't fix this, I think we'll need an admin for this. -- Michael F. Schönitzer 20:37, 16 February 2018 (UTC)[reply]

Hello. La Paz cable car map is not accurate, especially the station locations of Linea Morada and Celeste. Killman station does not even exist. — Preceding unsigned comment added by Siachoquero (talk • contribs) 10:47, 10 July 2018 (UTC)[reply]

@Siachoquero: Hi, thanks for your input. The latest version was not created by me but by @Chumwa: . I mostly used miteleferico.bo as source. Do you know any other sources? In the current version the Station "Cancha Zapata" seems to be indeed quite off, comparing to this map. Cumwa, can you correct this? (I tried but failed.) The situation about station 'Killman' does supprise me a bit, it isn't on the webpage now but I think it was in the past? Maybe it was cancled? It's hard to search for me since I don't speak Spanish. -- Michael F. Schönitzer 00:40, 11 July 2018 (UTC)[reply]

The corrections are made now. The vanished Killman station is really strange: in older maps it is always present. --Chumwa (talk) 05:57, 11 July 2018 (UTC)[reply]

Hello again.

Now Linea Celeste alignment is correct. Yes station "Killman" was canceled to make Linea Morada "express line". Linea Morada alignment is completely mistaken on your map. It must be completely straight Exact alignment. Alignment on your map Correct alignment. — Preceding unsigned comment was added by 95.104.73.110 (talk) 18:23, 15 July 2018 (UTC)[reply]

@Chumwa: Can you please update the map once more? Thanks. -- Michael F. Schönitzer 20:28, 15 July 2018 (UTC)[reply]

File:Galton-height-regress.jpg has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk. If you are the copyright holder and the creator of the file, please read Commons:But it's my own work! for tips on how to provide evidence of that. The file you added has been deleted. If you have written permission from the copyright holder, please have them send us a free license release via COM:VRT. If you believe that the deletion was not in accordance with policy, you may request undeletion. (It is not necessary to request undeletion if using VRT; the file will be automatically restored at the conclusion of the process.) This file is a copyright violation for the following reason: While the *data* this graph is based on is from Galton's 1889 book Natural Inheritance, this graph was created in 1994, it is not an "original (1889) graph" as claimed This file is a copyright violation because it comes from: https://books.google.co.uk/books?id=E5V-3kkiKikC&pg=PA19&#v=onepage Warning: Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing. Afrikaans ∙ العربية ∙ asturianu ∙ azərbaycanca ∙ беларуская ∙ беларуская (тарашкевіца) ∙ български ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Zazaki ∙ Ελληνικά ∙ English ∙ español ∙ euskara ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ italiano ∙ 日本語 ∙ 한국어 ∙ Lëtzebuergesch ∙ македонски ∙ മലയാളം ∙ मराठी ∙ Bahasa Melayu ∙ Malti ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ Plattdüütsch ∙ Nederlands ∙ norsk nynorsk ∙ norsk ∙ polski ∙ português ∙ português do Brasil ∙ română ∙ русский ∙ sicilianu ∙ slovenčina ∙ slovenščina ∙ српски / srpski ∙ svenska ∙ தமிழ் ∙ тоҷикӣ ∙ ไทย ∙ Türkçe ∙ українська ∙ oʻzbekcha / ўзбекча ∙ Tiếng Việt ∙ 中文（简体） ∙ 中文（繁體） ∙ +/−

 

D Wells (talk) 13:01, 31 July 2019 (UTC)[reply]

A community discussion has been closed where the consensus was to grant all file movers the suppressredirect user right. This will allow file movers to not leave behind a redirect when moving files and instead automatically have the original file name deleted. Policy never requires you to suppress the redirect, suppression of redirects is entirely optional.

Possible acceptable uses of this ability:

• To move recently uploaded files with an obvious error in the file name where that error would not be a reasonable redirect. For example: moving "Sheep in a tree.jpg" to "Squirrel in a tree.jpg" when the image does in fact depict a squirrel.
• To perform file name swaps.
• When the original file name contains vandalism. (File renaming criterion #5)

Please note, this ability should be used only in certain circumstances and only if you are absolutely sure that it is not going to break the display of the file on any project. Redirects should never be suppressed if the file is in use on any project. When in doubt, leave a redirect. If you forget to suppress the redirect in case of file name vandalism or you are not fully certain if the original file name is actually vandalism, leave a redirect and tag the redirect for speedy deletion per G2.

The malicious or reckless breaking of file links via the suppressredirect user right is considered an abuse of the file mover right and is grounds for immediate revocation of that right. This message serves as both a notice that you have this right and as an official warning. Questions regarding this right should be directed to administrators. --Majora (talk) 21:35, 7 November 2019 (UTC)[reply]

Guten Tag,

du hast vor etwa einem Jahr mein Bild München, Loretokapelle, 8.jpeg in St. Mina koptisch-orthodoxe Kirche, Loretokapelle, 8.jpg umbenannt, und zwar mit der Begründung „wrong name“. Ich glaube, das heißt „falscher Name“.

Ich bin zwar nicht begeistert, wenn ein Bild von mir einen grammatikalisch falschen Namen trägt (nach „St. Mina“ müsste ein Komma stehen), aber das ist natürlich immer noch besser als ein inhaltlich falscher Name. Könntest du mir, damit ich solche Fehler künftig vermeide, sagen, worin mein Fehler bestand? Die Kategorie heißt ja auch Loretokapelle (Munich). Gibt es vielleicht in München noch eine weitere Loretokapüelle?

Danke und Grüße -- Renardo la vulpo (talk) 19:00, 14 September 2020 (UTC)[reply]

Hi @Renardo la vulpo: , es tut mir leid, falls ich das fälschlich umbenannt habe – und ich kann es auch erneut umbenennen, falls der aktuelle Name unglücklich ist. Ich erinnere mich nur noch grob: da gab es damals ein Durcheinander – ich glaub, es waren zwei unterschiedliche Kirchen miteinander vermixt – da hab ich das aufgeräumt und wohl auch einige der Bilder umbenannt um Verwechslung zu vermeiden. -- Michael F. Schönitzer 19:24, 16 September 2020 (UTC)[reply]

Danke für die Antwort, Michael – wenn es da Zweifel gab, dann lassen wir 's mal so, wie es jetzt ist. -- Renardo la vulpo (talk) 12:15, 17 September 2020 (UTC)[reply]

Hallo,

ich wollte diese svg-Datei aktualisieren, in der steht, das der Code von Dir ist. Leider meckert gnuplot am Code herum. Ich hab das Problem hier beschrieben, vielleicht könntest Du ja antworten. Im übrigen, wenn ich die Anweisung "fsize 18" herausnehme, dann klappt der Output. Danke schonmal. --Michael w (talk) 17:39, 6 December 2020 (UTC)[reply]

Hi, wie Boehm schon schrieb muss es font ",18" statt fsize 18 heißen. Ich glaube fsize hieß es früher mal. Wenn du das updatest, würde ich die Farben ändern, damit man sie besser auseinander halten kann. Und du musst vielleicht xtics vergrößern (verdoppeln?), weil sonst die Beschriftung der x-Achse zu eng ist. Ping mich gerne an, wenn es Probleme gibt. -- Michael F. Schönitzer 22:37, 8 December 2020 (UTC)[reply]

Hab jetzt mit geändertem Code und aktuellen Daten eine neue Datei erzeugt und hochgeladen. Bin nicht wirklich fit in gnuplot. Wünschenswert wäre bzw. ich könnte mir vorstellen, die Umsatzlinie gestrichelt dazustellen, damit man den Unterschied besser sieht. --Michael w (talk) 14:26, 9 December 2020 (UTC)[reply]

@Michael w: Gestrichelt ginge mit dt 2 (oder eine andere Zahl >1), aber warum nicht gleich an übliche Konventionen zu Gewinn/Verlust-Diagrammen halten? → Bild -- Michael F. Schönitzer 00:22, 12 December 2020 (UTC)[reply]

Hallo, ja sieht gut aus. Wie gesagt, ich kenne mich null mit gnuplot aus. Danke fürs erstellen, ich binde das gleichmal in den Artikel ein. --Michael w (talk) 08:15, 12 December 2020 (UTC)[reply]

Hello Michael, we are leading a code review and fixing of LinguaLibre Suite. Could you check phabricator:T218373 and confirm this bug still occurs ? Yug (talk) 16:41, 15 February 2021 (UTC)[reply]

العربية ∙ беларуская ∙ беларуская (тарашкевіца) ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Ελληνικά ∙ English ∙ español ∙ euskara ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ italiano ∙ 日本語 ∙ ಕನ್ನಡ ∙ 한국어 ∙ lietuvių ∙ latviešu ∙ македонски ∙ മലയാളം ∙ मराठी ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ 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:Huston rir ipv4 exhaustion projection.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 ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case. Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). Warning: unless the permission information is given, the file may be deleted after seven days. Thank you.

 

Q28 (talk) 06:12, 15 February 2023 (UTC)[reply]

Hello,

This file has not been updated since 2020 and could use a little update, since it's used on many projects. Could you update it, please? All the best — WikiLucas (🖋️) 15:31, 30 April 2023 (UTC)[reply]

Read this message in your language

Dear Wikimedian,

You are receiving this message because we noticed that you voted in Round 1 of the 2022 Picture of the Year contest, but not yet in the second round. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2022) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

In this second and final round, you may vote for a maximum of three images. The image with the most votes will become the Picture of the Year 2022.

Round 2 will end at 18 May 2023, 23:59:59 UTC.

Click here to vote now!

Thanks,
the Wikimedia Commons Picture of the Year committee

Delivered by MediaWiki message delivery (talk) 07:46, 5 May 2023 (UTC)[reply]

File:LL-Q188 (deu)-Michael Schoenitzer (MichaelSchoenitzer)-Ebermannstadt.wav 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! Afrikaans ∙ العربية ∙ беларуская ∙ беларуская (тарашкевіца) ∙ български ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ bosanski ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Zazaki ∙ ދިވެހިބަސް ∙ Ελληνικά ∙ English ∙ Esperanto ∙ español ∙ eesti ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ íslenska ∙ italiano ∙ 日本語 ∙ 한국어 ∙ 조선말 ∙ македонски ∙ മലയാളം ∙ Bahasa Melayu ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ 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 ∙ 中文 ∙ 中文（简体） ∙ 中文（繁體） ∙ +/−

Bildungsbürger (talk) 16:20, 5 February 2024 (UTC)[reply]

Dear Wikimedian,

Wikimedia Commons is happy to announce that the 2023 Picture of the Year competition is now open. This year will be the eighteenth edition of the annual Wikimedia Commons photo competition, which recognizes exceptional contributions by users on Wikimedia Commons. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2023) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year are all entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

For your convenience, we have sorted the images into topical categories. Two rounds of voting will be held: In the first round, you may vote for as many images as you like. The top 30 overall and top 5% of most popular images in each category will continue to the final. In the final round, you may vote for just three images to become the Picture of the Year.

Round 1 will end on 14 October 2024, 23:59:59 UTC.

Click here to vote now!

Thanks,
the Wikimedia Commons Picture of the Year committee

You are receiving this message because you voted in the 2022 Picture of the Year contest.

MediaWiki message delivery (talk) 17:01, 1 October 2024 (UTC)[reply]

Read this message in your language

Dear Wikimedian,

You are receiving this message because we noticed that you previously voted in the Picture of the Year contest. Wikimedia users are invited to vote for their favorite images featured on Commons during the last year (2023) to produce a single Picture of the Year.

Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year were entered in this competition. These images include professional animal and plant shots, breathtaking panoramas and skylines, restorations of historical images, photographs portraying the world's best architecture, impressive human portraits, and so much more.

In this second and final round, you may vote for a maximum of three images. The image with the most votes will become the Picture of the Year 2023.

Round 2 will end at 28 October 2024, 23:59:59 UTC.

Click here to vote now!

If you have already voted for Round 2, please ignore this message.

Thanks,
the Wikimedia Commons Picture of the Year committee
MediaWiki message delivery (talk) 17:10, 16 October 2024 (UTC)[reply]