User talk:Lupo

Running 1.44.0-wmf.2 (8fd6c9c)

Older talk is in the archive.

Commons maintenance announcements [+/−]

More translations are needed for:

• Commons:Project scope (Sept 2008)
• Commons:Fan art (April 2009)
• Help:Gadget-ImageAnnotator#User interface texts (August 2009)
• Commons:File renaming (October 2009)
• Commons:Nudity

---

Backlogs:

as of 18 February 2010

• Old deletion requests are still opened.
• Many files moved to Commons requiring review.
• Too many unprocessed files without source.
• Many files are OTRS pending for too long.
• There are 124 requested merges.
• The Vandalismpatrol has over 1190238 unpatrolled anonymous edits.

Special uploadform

Hello Lupo, I noticed you have experience with the upload form/code/etc. My request is if it is possible to create a shorter version of the current uploadform for a photo contest in what some things already are pre-filled/hidden/restricted, and with one extra field? Can you help me with that or do you know who can help me wit this request? Greetings - Romaine (talk) 13:48, 22 August 2011 (UTC)

What contest do you have in mind? Please note that AFAIK Jeroen De Dauw is currently making the upload wizard customizable to be able to provide support for this year's WLM projects. For last year's dutch WLM, I had indeed programmed a simplified upload form, which still exists. If your requirements are not too different, I think I might be able to slip in some coding in between my normal daytime work. But I don't have the time to do any complicated things; too much to do off-wiki. Lupo 14:00, 22 August 2011 (UTC)

Great! It is WLM BE/LUX. I am not happy with the situation that experienced users are forced to use the uploadwizard. If they want to use it, they may do so, and I guess it will help new users with uploading, but I tried it the past days and I found it very uncomfortable for uploading (so much that I would not take part in the contest if the uploadwizard is the onliest way to participate). I had indeed in mind the Dutch WLM of 2010 what was an ideal format to use, and worked great! (I must say my compliments for that form last year.) What I had in mind was simple hiding some fields (source = always own, author = always username, other versions = hidden, Permission = hidden, Additional info = hidden, specialchars = hidden, license = CC-BY-SA 3.0, perhaps the date the current date auto), a field to select the region (in the Netherlands there are only rijksmonumenten, in Belgium there are three regions with each their own id-system, templates are already created on Commons: Vl, Wal and Bru) and a fill-in field for the id, and the category prefilled. It would be nice to have the UploadForm_description_languages set in 'fr', 'en', 'de', 'nl' as this are the languages used in the area of the Belgium contest. Besides the chose of the region it is roughly the same as the uploadform used in 2010. If there are questions, I am also available on IRC. Thanks in advance! Greetings - Romaine (talk) 14:29, 22 August 2011 (UTC)

I don't do IRC, sorry. I'm too old for that :-) But take a look again at the 2010 nl-WLM upload form. That form already does the "source = always own, author = always username, other versions = hidden, Permission = hidden, Additional info = hidden, specialchars = hidden, license = CC-BY-SA 3.0, perhaps the date the current date auto" already. The Rijksmonumenten field was added by a hack; it had a hard-coded label text, and its help text mis-used another help field for a hidden field (the additional info).

For Belgium, we'd need the label text translateable, and we'd need some selector where the user could specify one of "Onroerend erfgoed", "Monument Wallonie", or "Monument Brussels". I don't think we could make these selector texts translateable without excessive work, but I guess we could live with that.

The problem is the user language. Since the method we used for the Dutch WLM 2010 abused the "uselang" hack, it could be done essentially in only one language (Dutch). If we use the same mechanism (and I don't see any other way; at least none that would be relatively simple to do) we're also bound to one user interface language. Would it be acceptable to have the form in one language only (English)? Alternatively, I think I could do some script magic to have the form in different languages, but without help texts. Anything else would be rather complicated. (Sorry, but all this is rather hacky.)

Having four description fields (fr, nl, en, de) should be no problem, as long as it'd be OK to have all four always.

I would also have to know how to label the ID field in all three languages, and which categories to prefill in which conditions.

When does WLM start? If it's September 1 (like it was last year), we're already rather late...

Lupo 21:47, 22 August 2011 (UTC)

Hello Lupo, Everything about the WLM BE/LUX contest en much other things in other countries are indeed late. It starts 1 September.

Yes, all four the description fields all the time.

The form you link doesn't show fully it seems, the summary field shows a template here.

If it is not possible to have the selector field in four languages, one description would be fine I think. Then we can use "Onroerend erfgoed (Flanders)", "Monument Wallonie" and "Monument Brussels". Perhaps a fourth field must be added too for Luxembourg: "Monument Luxembourg". I think it would be better to have the form in four languages, the help texts can be left away.

I think we better leave the category-field not prefilled, but they must be able to use it, the category structure is too complicated to select the right category. The 2010 ELM-form looks good, so I hope we can get such one. Greetings - Romaine (talk) 12:21, 23 August 2011 (UTC)

← All right. I have programmed a first version (without localization yet!). You can have a sneak preview here. Is this form more or less what you had in mind? If not, what would like to have changed? (I'm talking only about the form itself, not about the huge introductory text. Play around by filling in stuff and then clicking the preview button instead of the upload button.)

Next step is to think about localization. I would need better introductory texts, specific for the WLM event, in all four languages. Something like MediaWiki:Uploadtext/nlwikilovesmonuments. If you want to take that exact text, I can translate that myself into the three other languages easily. With localization, I'll also set the license correctly to CC-BY-SA-3.0 (unported).

Are you sure that WLM BE/LUX will really start? The "How to participate" page is empty in all languages! For an event that should take off in a week, that doesn't bode well.

Lupo 21:28, 25 August 2011 (UTC)

Fantastic! Something like this I had in mind. Indeed the huge introductory text, if that could be shorter/skipped I think it would better, however not a big issue. I think the four description fields are a bit confusing because of the headers. "Description in ..." with ... the specific language would made it better I think, even if it is all in English. Please also add {{Wiki Loves Monuments 2011|be}} automatically when someone uploads a file with this form. You can use the same intro text, but then with this logo: File:LUSITANA_WLM_2011_d.svg, the "Naamsvermelding-Gelijk delen 3.0 Nederland:" without the "Nederland", and the first link linked to www.wikilovesmonuments.be . In the past weeks all the attention has gone into translating / creating the monument lists and the other pages of the website. Past weekend I tried to create the page how to participate but I got stuck with the uploadwizard. The page should be about how to upload, and that was the difficulty as described above. The website texts are written on nl-wiki itself. This weekend the website should be finished mostly. Very much things about the organisation of Wiki Loves Monuments both in Belgium/Luxembourg as in Europe is last minute work (or some work not done at all). September 1 the contest starts, that will be sure. And yes, in my planning everything should have been arranged already a month ago, but due problems with other people organizing went very very very slowly. But, we now got a great uploadform! :-) Romaine (talk) 01:38, 26 August 2011 (UTC)

OK. Note that {{Monument Luxemburg}} doesn't exist yet. I'll see that I can resolve the remaining issues (intro text and such) in the next few days. When it's done, I'll give you the precise links to the forms (the final version probably will not have the "&withJS=..." in the URL). Lupo 06:30, 26 August 2011 (UTC)

New intro texts and license selector is done. I've slightly changed the labelling of the four description fields, as suggested. Localization for Dutch and French is done; but will become active only the next time the Wikimedia servers refresh their message cache (I think that is every 24h). I'll check it again tomorrow; if it works by then, I'll do the two remaining localizations for English and German, and will then set up the script such that it executes automatically (without the "withJS=..." in the URL). Lupo 12:18, 26 August 2011 (UTC)

←  Done The four forms are:

• Dutch upload form for WLM BE/LUX
• French upload form for WLM BE/LUX
• German upload form for WLM BE/LUX
• English upload form for WLM BE/LUX

If you revisit them, you may need to reload your browser's cache the first time, because you had visited the earlier form and your browser thus cached the old implementation. Other people who have not visited these forms before should not have this problem, I think.

Try them out, and also really upload a few images. If there are any problems, tell me. Lupo 16:01, 27 August 2011 (UTC)

I got two times the description field with the template showing and the other showing time a lot of fields which disappeared after purging. I guess this has to do with the cache. I tried the form and worked great! Fantastic! :-) Thanks! Greetings - Romaine (talk) 01:01, 31 August 2011 (UTC)

Closing contest Wiki Loves Monuments

Hello Lupo, To conclude, your uploadform works great, many users have used it! :-) But, the end of the context is soon, only during the month of September people are allowed to upload for the contest. As perhaps a lot of users liked the uploadform you created, we think we can keep the form at least for a while, because people can easily put the identifiers in the template just by filling in. Also we would like to organize it next year again. The question is, can you remove the template {{Wiki Loves Monuments 2011|be}} out of the uploadform (for the next 11 months)? This must be done on the 1st of October (not earlier). This template marks if someone is participating with a file into the contest. All the other parts of the uploadform can remain the same. Thanks for your great help! :-) Romaine (talk) 16:37, 29 September 2011 (UTC)

Sorry for not responding; I was away. I see you already did that yourself. Lupo 09:42, 18 October 2011 (UTC)

No problem! :-) In September I got admin on Commons, and hadn't realized that I can change it as well. Fot next year we can use them again. :-) Thanks for creating them! Romaine (talk) 01:20, 19 October 2011 (UTC)

Doubt on this DR

Dear Admin Lupo, Please give your views in this DR here. I passed this May 2008 uploaded image based on your advice that pre-2009 images could be kept on Commons as long as there was some kind of clear permission. The objection is that the permission applies only to 'wikipedia.' I think you said that COM:OTRS was not very strict for images uploaded before January 1, 2009...but I'll let you decide if I was right or wrong in passing this image. If I was wrong, then so be it. But the permission on the panoramio link is still there--only it says 'for wikipedia.' Best Regards, --Leoboudv (talk) 08:23, 27 August 2011 (UTC)

I've replied there. Lupo 16:08, 27 August 2011 (UTC)

• Thank you for your comments. I'll revert my pass and tell the nominator of my decision. Thank You for your time, --Leoboudv (talk) 19:11, 27 August 2011 (UTC)

Please delete 20 panoramio images

Dear Admin Lupo,

Is it possible if you could immediatedly delete these 20 panoramio images here all at my own request? I passed them because Dr. Fo on panoramio got permission from the copyright owner to use his images from his account here in 2008...but of course the permission only mentioned wikipedia. (if you see their talkpages when I gave my reason in typing in the panoramio pass) Dr. Fo is giving me a headache sadly. His old images always mentioned wikipedia. BUT now I reverted my panoramio pass and I see that ZooFari and Electron marked them 1-2 full months ago on an ARR license...but they were never deleted before I passed them.

As an Admin, you can delete them all with your Admin tools. Most of the 20 images are barely used except this and this. Can you correct my error and delete the 20 photos ASAP?. Please accept my apology for misinterpreting your statement on what permission was acceptible for pre-2009 uploaded pictures. Now I am trying to clean up the mess and I recall M. El Garci's images very well indeed. Dr.Fo uploaded so many of them but since they were all in 2008, I thought they were OK. It turns out I was wrong. I hope you can do this as they were all failed as 'ARR' by ZooFari and Electron previously as I said. Thank You, --Leoboudv (talk) 02:13, 29 August 2011 (UTC)

Dear Leo, it's no problem, really. All these images are tagged "missing permission", they'll be gone in a few days. There's really no need to apologize. We all make mistakes, and in this case, no harm was done. I've made much more severe blunders in my time here. I once mistakenly deleted a bunch of images, which then were removed by a bot from the pages they had been used. I realized my error a few minutes later, but too late. I could restore them here, but I could only restore a few uses at the wikipedias. Such is life... Lupo 19:49, 29 August 2011 (UTC)

•  Comment: OK. Thank you for your reply. My blunder was not intentional. Best Regards, --Leoboudv (talk) 04:57, 30 August 2011 (UTC)

Danke

Hey Lupo! Vielen Dank für die cats bei den uShaka Seaworld Bildern!! Wie kommts dass du dich da so gut auskennst? LG, Amada44  ^{talk to me} 10:04, 30 August 2011 (UTC)

Tu ich gar nicht :-) Bitte, gern geschehen!

Hier gibt's eine kleine Karte, die mit etwas Fantasie gerade noch so knapp lesbar ist und die einige der Spezies auflistet. Das war mein Einstiegspunkt. Danach dann ein wenig Googlen nach Bildern und Beschreibungen der so vermuteten Spezies, dann Verifikation, dass das Viech auch tatsächlich in der Nähe von Südafrika vorkommt.

Einige Spezies konnte ich auch einfach direkt via Google bestimmen, so kam ich z.B. via Google image search nach "+starfish +white +red" ziemlich rasch auf den "Red-knobbed starfish" für File:UShaka Sea World 1063.jpg.

Nächstes Mal könntest Du ja auch einfach noch die üblicherweise am Rand der Aquariumsfenster angebrachten Erläuterungstafeln abfotografieren. In allen solchen Aquarien, die ich besucht habe, gab's sowas. Ungefähre Grössenangaben wären auch noch hilfreich. ;-) Lupo 10:31, 30 August 2011 (UTC)

Alle Achtung! Vor allem die Karte vom uShaka ist super! Das du die gefunden hast .... ;) Ich habe immer die Schilder fotografiert wenn es welche gab. Leider waren die etwas spärlich. Grössenangaben ist eine gute Idee (eigentlich müsste die man vor Ort notieren damit sie möglichst unverfälscht bleiben). Ich probiere mal auch ein paar nach deiner Methode zu finden ;). LG, Amada44  ^{talk to me} 18:44, 31 August 2011 (UTC)

Bei einigen habe ich meine Vermutungen auf der Diskussionsseite dokumentiert:

• File talk:UShaka Sea World 0929a.jpg
• File talk:UShaka Sea World 1064.jpg
• File talk:UShaka Sea World 1038.jpg
• File talk:UShaka Sea World 0869.jpg
• File talk:UShaka Sea World 1086.jpg

Und danke für die Korrektur des Weissspitzenhais! Lupo 19:52, 31 August 2011 (UTC)

Woher weisst Du, dass File:UShaka Sea World 0917a.jpg und File:UShaka Sea World 0920.jpg Pterois volitans sind und nicht Pterois miles? Die geografische Verbreitung von P. volitans und P. miles würde eher für letztere Spezies sprechen... Lupo 20:02, 31 August 2011 (UTC)

Ich habe noch mal eine Seite auf der uShaka homepage gefunden: http://www.seaworld.org.za/aquarium/animals/fish/aquarium/animals/fish/our-fish/ und http://www.seaworld.org.za/aquarium/animals/sharks_rays/aquarium/animals/sharks_rays/our-sharks-and-rays/ . Der eine Hai (auf dem Foto ist nur die Nase) ist glaube ich ein Dusky Shark, aber das muss ich morgen noch mal anschauen. LG, Amada44  ^{talk to me} 20:06, 31 August 2011 (UTC)

Ah, super! Aber gerade der Pterois ist unklar: sie schreiben "Devil Firefish (Pterois volitans)". w:en:Devil firefish ist aber P. miles, und w:en:Pterois volitans weist explizit auf die Ähnlichkeit der beiden Spezies hin. Na ja, eins von beiden ist's auf jeden Fall. Lupo 06:36, 1 September 2011 (UTC)

Lupo!

It's so good to see that you're still around on Commons! I haven't seen you in ages. You were always the guy I turned to when I had questions about international copyright issues that I couldn't answer myself. I took a long wikibreak, but I'm now very active again in copyright issues on the English Wikipedia, and I still sometimes run into situations I don't have a good answer for. Is it okay to bother you from time to time about such things? If so, is it better for me to contact you here, or on the German Wikipedia, or where? (Please reply here, if you would.) All the best, Quadell (talk) 12:46, 30 August 2011 (UTC)

Hi there, Quadell! Great to see you're back! Sure you may quiz me on copyright stuff here. Though there are several other people around here who know quite a bit about copyright, too, and sometimes (or often?) more than me, so if you need more balanced or more reliable answers than I can give, asking in a public forum might give better results.

I'm mostly active here at the Commons; I rarely edit en-WP nowadays. And while I do have an accout at de-WP, I'm all but inactive there. Even here, it seems my activity has declined lately; I just got too much to do in real life.

Just take it easy on the copyright stuff at en-WP lest it wears you down. Lupo 13:07, 30 August 2011 (UTC)

That's good advice. I'm glad you're taking it easy. Okay, here are a few of the questions that have stumped me lately.

1. w:en:Wikipedia:Media_copyright_questions#Image_of_a_film_prop:_3D_art.3F: Is a film prop of a grave memorial creative enough to be eligible for copyright in the U.S., making a photograph a derivative work?
2. w:en:Wikipedia:Media_copyright_questions#General_Questions: Is it true that if I take a photograph with your camera and your film in Canada, that you own the copyright and not me?
3. w:en:Wikipedia:Media_copyright_questions#Jumbotron_images: If a Jumbotron shows people at a ballgame in the U.S., but the image is not "fixed", is there a copyright held? If I take a photo of a Jumbotron screen, is it a derivative work?

Thanks for any help. Quadell (talk) 15:23, 30 August 2011 (UTC)

Well, then I would like to use this opportunity for a "me too"; like Quadell, I always valued your assessments and advice highly, Lupo (e.g. cases Mittelholzer, Paul Klee), and would like to reiterate: "It's so good to see that you're still around on Commons!" - indeed :-) Gestumblindi (talk) 18:36, 30 August 2011 (UTC)

Quadell, meet Gestumblindi, who knows quite a bit about copyright laws himself. Lupo 09:15, 31 August 2011 (UTC)

Quadell, I should have known you'd ask edge case questions that I cannot fully answer either. I've taken the liberty of numbering your three questions. Here's my take:

1. Yes, film props are copyrightable in the U.S. if they do meet the threshold of originality. Lucasfilm for instance has a valid copyright on the Stormtrooper helmet in the U.S., and has enforced that in the U.S. See Lucasfilm Ltd. v. Shepperton Design Studios Ltd,, with this final verdict in favor of Lucasfilm. If copyrighted, a photo of such a film prop might be considered a derivative work.

   But of course things are more complicated in the precise case of the tombstone prop. For Your Eyes Only is a British film, and the prop in all likelihood is a British work. Lucasfilm failed to enforce its U.S. copyright in the UK: UK Court of Appeal decision, upheld by the UK Supreme Court. (See also BBC's coverage of the case.) The British courts held that (a) 2-D film props (scene paintings) were clearly copyrightable, but (b) that 3-D props are copyrightable only if they are "sculptures". In the case of the Stormtrooper helmets, the UK courts found them to be a utilitarian objects, not sculptures, and thus not copyrightable in the UK. I believe, though, that the tombstone prop would qualify as a "sculpture", and furthermore (as en:User:Hammersoft pointed out at en-WP) the thing is painted, which, even if the 3-D model were not a sculpture, might qualify as "scene painting" and thus be copyrightable per se.

   So, yes, I think that tombstone prop is copyrightable (even in the UK) if it meets the threshold of originality. The question thus is whether the tombstone or its painting is original enough. Discussions about the originality embodied in an artefact always are, absent a court decision on this precise or on a sufficiently similar artefact, matters of opinion. I am not aware of any such court decision in this case (the Stormtrooper helmet is too different from the tombstone to allow conclusions by analogy). I tend to follow our precautionary principle "when in doubt, consider it copyrighted".

2. Yes, that would appear to be true. I knew that Italy once had the same rule (copyright owner of a photograph = owner of negative or original copy, if there is/was no negative) but dropped it, I think in the 1990s (probably when they implemented EU directive 93/98/EEC). I was unaware that Canada has that rule, too. I think it's an eminently sensible rule that avoids the classic problem when tourists ask a stranger to take a picture of them (the stranger owns the copyright in most countries!).

   Note that in Canada, that's only the default rule. If you wanted to take a photo with my camera (and my chip card) and own the copyright all the same, we could agree that the photographer (you) as opposed to the camera and chip owner (me) would be the copyright owner. Or in this digital age, you could just bring your own chip card and insert it into my camera: you'd own the original copy on the chip card, and would thus be the copyright owner.

3. The jumbotron displays an audiovisual stream embodying original authorship in its camera-work and its selection of which camera images to display. (See Gorman, R. A.: Copyright Law, 2nd ed., U.S. Federal Judicial Center, p. 20.) If this stream is fixed, then it is a work in the sense of the copyright law. 17 USC 101 defines simultaneous recording of a live transmission (by the producer of the live transmission) as a fixation. I don't know enough about how such jumbotron "broadcasts" are managed to say whether it's common for these streams to be recorded while being sent to the device, but I would not be surprised if it was so. After all, the jumbotron operators too know U.S. Copyright Law... If the stream is simultaneously recorded, then we have indeed an audiovisual work that is being displayed, and thus taking a picture of a jumbotron displaying a frame of that audiovisual work would make the picture a derivative work. (Unless the jumbotron was de minimis in the photo, for instance if the photo is an overview shot of the whole stadium that just also happens to include the jumbotron display.)

   Note that the whole thing about the stream being "fixed" is a U.S.-specific thing; I think if the jumbotron were in a stadium in the EU, the stream would be copyrighted even without being "fixed" in the U.S. sense. Live broadcasts are covered either by a copyright on the broadcast itself, or by a neighboring right. See e.g. the this overview. I think the fixation right of broadcasters defined in article 6(2) of EU directive 92/100/EEC would be applicable, too.

Lupo 09:15, 31 August 2011 (UTC)

Thank you so much. I'm impressed by your thoroughness, as always, Lupo. I've made some updates based on this information. You're a blessing. Be well, Quadell (talk) 20:15, 31 August 2011 (UTC)

• I just wanted to take the opportunity to voice agreement here with Quadell. Lupo, I'm very, very impressed. Wow! --Hammersoft (talk) 18:18, 1 September 2011 (UTC)

Commons:User Scripts

Recently, I created this page to have a centralized place to talk about current JS issues. Currently it is empty but I hope you will participate and use it. Thank you. -- RE rillke questions? 17:15, 1 September 2011 (UTC)

Invitto

Ich möchte gerne wissen woher Du wissen willst welche Photos von mir stammen und nicht. Betrifft zB. Datsun C20 Vanette Modellfamilie aus dem Prospekt oder zB. Nissan NV 400 von der Handwerkermesse. Bist Du mein 2.Ich das Du Dir das Recht nimmst zu beurteilen?????????????????––Invitto 20:06, 4 September 2011 (UTC)

Photos copied from numerous random websites. Just don't do that again. File:Niisan NV 400.jpg also appears to be a copyright violation. If you disagree, there's Commons:Undeletion requests, but if you keep uploading copyright violations, you will be blocked. Lupo 06:16, 5 September 2011 (UTC)

ach jetzt können wir plötzlich kein deutsch mehr, lustig ist das.... −− Invitto 10:07, 5 September 2011 (UTC)

Weeste wat? Geh woanders spielen. I replied in English because I wanted others who may not understand German to be able to follow at least part of this discussion. Im Übrigen hast Du nicht bloss Pressematerial hochgeladen, sondern einfach Bildchen links und rechts geklaut. Davon abgesehen ist auch Pressematerial üblicherweise weder Urheberrechtsfrei noch frei lizenziert. (Translation: You didn't just upload press material but simply stole images left and right. Anyway press material is usually neither copyright-free nor freely licensed.) Lupo 10:35, 5 September 2011 (UTC)

See also here. --Túrelio (talk) 10:48, 5 September 2011 (UTC)

Da haben sich unsere Edits gerade gekreuzt. :-) Lupo 10:50, 5 September 2011 (UTC)

Another panoramio DR

Dear Admin Lupo,

I'm sorry to disturb you. By now, I suppose you know what to expect here. Its yet another 2008 panoramio image uploaded by Dr. Fo which mentions use for "wikipedia." But if you look at the copyright owner's reply, he didn't put any restrictions on the use of his photo...whether it be on wikipedia or elsewhere. Secondly, I ask you here because Admin MGA73 is trying to save it but sadly it appears the copyright owner is away from his account. And finally, many Commons users here didn't know that a simple permission was acceptible for pre-2009 uploaded images. All I ask is to please look at my comments in the DR and Dr. Fo's comments in the 2008 panoramio link where he does mention the word copyright to nolan and gives a link to the picture to nolan. The copyright owner, nolan, replies, you can use the image with 'pleasure.'

Is that a vague permission or a clear permission? The copyright owner was given attribution to the picture--and its an important photo. But can we make an exception to Dr. Fo's question for use on wikipedia and place more weight on the copyright owner's reply...which mentions no restrictions on the use of his picture--either monetary or its use on the internet other than wikipedia? Its been here 3 yrs now. I hope you can make a reply in this specific DR. Pls. just say what is on your mind after you see the DR. Thank You, --Leoboudv (talk) 23:57, 7 September 2011 (UTC)

MediaWiki:Gadget-HotCat.js

Hi Lupo, zu der aktuell laufenden https-Umstellung. Bei schon länger bestehenden Zugang über https://secure.wikimedia.org/wikipedia/de/wiki/Hauptseite nach Anmeldung (monobook-skin, alles auf de-wp) aktivierten Helferlein/HotCat von commons bleibt der Browser (Opera 9.64, Build 2480, Plattform Linux.) nach der Anwahl einer Seiten dubios hängen: Links können keine mehr angeklickt werden, in das Suchfeld keine Texte mehr eingetippt werden. Ursache dürfte ein dubioser Javascript-Bug in dem HotCat-Teil sein, denn nach Deaktivierung von dem commons/HotCat funkt der Browser reproduzierbar.

Nun werkt es aber auch bei neuen Zugang über https://de.wikipedia.org/wiki/Wikipedia:Hauptseite (detto http), egal ob dieses schon als fehlerhaft vermutete Helferlein/HotCat aktiviert ist oder nicht. Ich nehme an, das hängt irgendwie mit dieser Deiner Änderung [1] zusammen, wenn Zugang über secure.wikimedia.org und irgendeiner URL-String-Herumbastelei im HotCat erfolgt, kann es aber nicht näher eingrenzen.--Wdwd (talk) 09:46, 1 October 2011 (UTC)

Bin zur Zeit auf Reisen. Kann mich erst in ca. zwei bis drei Wochen darum kümmern. Dann schau' ich dann aber mal; ich denke, ich habe noch eine Opera 9.64 auf Windows irgendwo verfügbar. Auf Linux sicher nicht. Lupo 21:31, 5 October 2011 (UTC)

Hatte leider doch kein Opera 9.64 mehr; musste diese erst nochmals installieren. Ich kann Dein Problem nicht reproduzieren, bei mir funktionieren alle Arten, auf de-WP zuzugreifen, ob nun via secure.wikimedia.org, https://de.wikipedia.org oder http://de.wikipedia.org. HotCat funktioniert in allen drei Fällen, und gar nichts blockiert nirgends. Lupo 20:18, 18 October 2011 (UTC)

International organizations

Hello again, Lupo. Someone asked a question at en:Wikipedia:Media copyright questions#Logos of NATO, SEATO und CENTO that has me stumped. How would we determine the copyright status of the logos and documents of international organizations? Any ideas? Thanks! – Quadell (talk) 13:43, 3 October 2011 (UTC)

I'm travelling right now; I cannot currently answer such questions, sorry. Lupo 21:34, 5 October 2011 (UTC)

Need your help on Lose Cover Photo

Lupo, please help. In 2008 we had a discussion on the rights of the book cover of my book Lose. I got an email from the publisher Edition Nove that the rights would be in my hands, and I believe you stored this in the OTRS database. Since only OTRS admins can verify this in the DB, I would like to ask you to verify the storage of this email (together with my email if I remember correctly) and to send it to me so that I in turn can verify if the correct mails have been stored. (You can send it to literari@klausebner.eu) I need this because a user allegates that the rights for the photo on the cover would not have been released by the photographer, and the photographer, from Germany, seems to support this allegation. I need to clarify all this, so I need the emails which have been stored on the OTRS databse. Sorry for the inconveniences and thank you very much in advance.--Klaus Ebner (talk) 07:48, 5 October 2011 (UTC)

Please contact our OTRS team; I am not a member of the OTRS team. Try asking for help at Commons talk:OTRS. (Sorry for being so brief, I'm travelling right now and have only sporadic Internet access.) Lupo 21:37, 5 October 2011 (UTC)

Problem substituting $ in MediaWiki:Upload-permitted with allowed file-types

Can you help here? If you have no clue we could still use a JavaScript method to replace $ with mw.config.get('wgFileExtensions'). Thank you. -- RE rillke questions? 10:26, 8 October 2011 (UTC)

Transclusions with $-substitutions don't work. Fixed by substituting the transcluded message. Lupo 19:57, 8 October 2011 (UTC)

Thank you. -- RE rillke questions? 20:57, 8 October 2011 (UTC)

Gallery details + DelReqHandler - Admin-Links

Dear Lupo, I know you are very busy with HotCat and other scripts under your maintenance. I just wondered whether you know why the delete-links do not work. I get an error like "DelReqHandler.get_cookie is undefined" when attempting to use the links provided in gallery-details. I just ask because the question about an easy tool raised on Administator's noticeboard. And I think adding a "kept"-link would not be that difficult to implement. Maybe you find the time to create something and investigate.

Thank you.

Kind regards -- RE rillke questions? 13:37, 11 December 2011 (UTC)

When DelReqHandler was rewritten by User:DieBuche, nobody adapted the link code in GalleryDetails. I don't know if the rewritten DelReqHandler offers any way to be reused from other gadgets like my old implementation. Lupo 21:12, 11 December 2011 (UTC)

Well, delete is only sending one post-request to the server. This shouldn't be difficult. $.post(url, params, successCB)

Thanks for your reply. -- RE rillke questions? 21:29, 11 December 2011 (UTC)

One would have to rewrite MediaWiki:ImageLinks.js. It still uses old stuff. For deletions, you'll need to get a deletion token first. But also the "notify..." and "flickrreview" links should trigger API edits. Lupo 07:41, 12 December 2011 (UTC)

I fear, I am too lazy, but not only. Some of MediaWiki:Utilities.js's functionality is now in mw.util. userIsInGroup is nearly superfluous since you can $.inArray(term, array), … You documented your software very well but is was not build into MediaWiki. Now we have LAPI and lots of other functions from "your framework" and the MediaWiki + jQuery -stuff. That's confusing and slows down everything. And the problem is that I came too late to this project (for learning, how other new users may feel ...).

LAPI: position : (function () can be removed now?

The concrete problem is how to show progress and how to find out where the user clicked (adminlinks) since it is using JavaScript-Links and not event-handlers (you could refer with $(this) to the clicked element-node). I do not have the strength and the competence (am not a professional) to completely rewrite this script and you and DieBuche seem to be busy and it is almost impossible to find new users willing to invest time into "our" scripts.

Finally, I wish you a happy new year and thanks for all you have done here. I think you are the one of those responsible for conveying people on Commons that JavaScipt is a natural part of this site. This has both advantages (acceptance) but also disadvantages (people come and say: "I want this, instantly please!"). -- RE rillke questions? 11:42, 2 January 2012 (UTC)

Frage zum Vorgang URAA

Hallo, du hattest vor längerer Zeit dieses Bild markiert, nun steht es zusammen mit einer Reihe anderer in Löschdiskussion. Da hier entweder ein mir völlig unbekannter Aspekt des Urheberrechts zur Geltung kommt oder schlichtweg ein Missverständnis vorliegt, ersuche ich um Aufklärung deinerseits. Eigentlich ist es ja so, dass Hammerschmidt vor mehr als 70 Jahren verstorben ist und Deutschland sowieso FoP hat. Danke - A.Savin 20:27, 18 January 2012 (UTC)

Tatsächlich, das sollte unter FOP fallen. Not-PD-US-URAA ist wohl schon korrekt, was die USA betrifft; in Deutschland ist das klar PD-old-70. Und da wir bei FOP uns nur auf das Ursprungsland abstützen und die US-Regelungen ignorieren, dürfte es also in Ordnung sein, das Not-PD-US-URAA einfach durch {{FOP}} zu ersetzen. Keine Ahnung, wieso mir damals FOP entgangen war. Tut mir leid. Hab's 'mal angepasst. Lupo 20:51, 18 January 2012 (UTC)

Hello, you have tagged This file with "Not PD US URAA". However, C Lindberg says here , that as France was late to implement the 1993 European directive, only a 50 years pma term would apply for France on 1 January 1996. What do you think ? Teofilo (talk) 21:16, 19 January 2012 (UTC)

Looks like Carl is right. Unless that EU directive had had some overriding effect even before the individual countries had written it into their own laws -- which I strongly doubt; that would be highly unusual, and directly contradict the French law implementing the directive -- France indeed would have had 50y p.m.a. (+ wartime extensions) on the URAA date 1996-01-01. Since 1997-04-01, the term is 70y p.m.a. in general for anything still copyrighted in at least one EU country on 1995-07-01. Lupo 23:11, 19 January 2012 (UTC)

Thanks for your reply. I further commented there. Teofilo (talk) 15:58, 20 January 2012 (UTC)

Hi Lupo, maybe you could have a look at this question? If the restoration would have meant just a restoration to 70 years p.m.a. for most works by individual authors, the issue would be much smaller, of course... Gestumblindi (talk) 21:07, 20 January 2012 (UTC)

Carl is right. The URAA restores copyright in the U.S. as if the work had been published in the U.S. on the date of its original publication abroad and all U.S. copyright formalities had been followed. 70y p.m.a. applies only to works not published before 1978, and might be of interest for us only for works of authors who died after 1925 but more than 70 years ago, and only if the works were posthumously published for the first time after 1977. Anything published 1923 - 1977, i.e., most works that are affected here by the URAA, got a copyright term of 95y since their original publication. Lupo 21:37, 20 January 2012 (UTC)

Thanks! Still, I think we should keep works posthumously published for the first time after 1977 in mind, there are certainly applications (e.g. photos from archives published recently for the first time...) Gestumblindi (talk) 21:40, 20 January 2012 (UTC)

Unless they were first published 2003 or later, there is a nasty gotcha with those... it's the later of 70pma and December 31, 2047. That is a special term for works created before 1978 but published from 1978 through 2002. But yes, old stuff just being published now would be 70pma, no strings attached. Carl Lindberg (talk) 03:56, 22 January 2012 (UTC)

HotCat

Hello, Lupo. You have new messages at MediaWiki_talk:Gadget-HotCat.js#Form_ID. You may remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

--Strainu (talk) 09:38, 20 January 2012 (UTC)

The Klee case

Hi Lupo; in light of the current URAA debate, I thought it could be a good idea trying to clarify the somewhat complicated copyright state of affairs regarding Paul Klee in the description of Category:Paul Klee, and changed it accordingly - I hope I got it right. Gestumblindi (talk) 01:13, 26 January 2012 (UTC)

Good idea. I think you got it right. In CH and EU, all his works are PD. In the U.S., published before 1923 is obviously PD, and those first published in CH, too. We assume that's all those published after 1933. Those first published in DE, which we assume to be his 1923-1933 works, would be copyrighted in the U.S. due to the URAA. Lupo 07:35, 26 January 2012 (UTC)

Vybz Kartel Bleacher.jpg

English:

Hello Lupo,

I noticed you have suppressed File:Vybz Kartel Bleacher.jpg. Perhaps I have forgotten something during the export process from en:wp, but I can confirm that this file has got a free licence (Creative Commons CC0 1.0) as you can see here : File:Vybz_Kartel_Bleacher.jpg.
It would be nice if you could reverse this action, or give me some explanations about it. Topfive (talk) 19:00, 30 January 2012 (UTC)

Français :

Bonjour Lupo, j'ai peut-être oublié quelque chose pendant l'importation du fichier, mais il est clair que l'image originale possède une licence libre.
Peux-tu reconsidérer cette suppression, ou me donner plus d'explications ? Je t'en remercie, Topfive (talk) 19:00, 30 January 2012 (UTC)

The image is all over the Internet, long before the upload at the English Wikipedia. I don't care what license it had or has at the English Wikipedia; it's just been grabbed from a random place, and there's no evidence the CC license was valid. Lupo 07:03, 31 January 2012 (UTC)

Ok, you are probably right. Topfive (talk) 12:39, 31 January 2012 (UTC)

I'd appreciate talkback at User talk:Rillke/checkCat.js

and thanks for the good description of HotCat/ the event-hooks one can use. -- RE rillke questions? 18:55, 5 February 2012 (UTC)

Now, I drafted User:Rillke/checkCat2.js. It should address the concerns raised on Village Pump. Basically it does the same but has a few more options. All used modules are loaded anyway by one of our default gadgets; therefore it should not be a performance-killer. Would you oppose adding it to the Gadget-Definition of HotCat? Thanks in advance. -- RE rillke questions? 14:24, 10 March 2012 (UTC)

That's fine by me. But note that if {{Check categories}} did add one category (instead of trying to be super-smart and adding a changing subcategory), then you could just configure HotCat to remove the template. It would present a "-" link on the category, and remove the template to remove the category. That'd be somewhat simpler. Maybe we could just make the template always add a (non-hidden) category named "Category check" or some such and configure HotCat to know that this category corresponded to the template. Lupo 15:31, 10 March 2012 (UTC)

I know at least 1 administrator here who would oppose adding a non-topic/maintenance-category that is visible to everyone (not hidden). But it's a special case, maybe, since the template is not smaller than a category... I am not sure. I assume you won't be the one adding this category to the template... and I don't need a long controversial discussion as well. -- RE rillke questions? 22:37, 13 March 2012 (UTC)

MediaWiki:Gadget-ImageAnnotator.js in der Esperantowikipedia

Hallo, Lupo. Nach der Hauptdiskussionsseite der Esperantowikipedia funktioniert dort eo:MediaWiki:Gadget-ImageAnnotator.js nicht mehr. Könnte es an der Umstellung der Software auf die Version 1.19 liegen? Wenn nicht, woran denn? Außerdem habe ich gerade gesehen, daß MediaWiki:Gadget-ImageAnnotator.js schon die Version 2.3a enthält. Was ist daran neu? Gruß --Tlustulimu (talk) 20:44, 16 February 2012 (UTC)

(+) Ich habe gerade gelesen, daß das Gadget wohl wieder funktionieren soll. Gruß --Tlustulimu (talk) 20:47, 16 February 2012 (UTC)

Gut, wenn's wieder geht... ein Update auf Version 2.3a ist aber schon empfehlenswert. Siehe Help:Gadget-ImageAnnotator/Installation#Upgrading_to_version_2.3a für die Prozedur, und gleich darunter eine Kurzbeschreibung, was sich geändert hat. Lupo 22:37, 16 February 2012 (UTC)

Documentation for gadget authors

I saw you had done some work on heavily-used gadgets. We're trying to start a library for gadget authors to use. Please check it out and post any questions or comments there. -- ☠MarkAHershberger☢(talk)☣ 02:00, 9 March 2012 (UTC)

image switching

Hello Lupo,

I saw that you built the Gadget-ImageAnnotator. I wander whether you can help with another gadget.

Image switcher:

• Switching between two pictures of same size, triggered by "mouse over".
• Example: Photo or Photo + information if photo touched by mouse, see eg [2]
• Technical CSS based solution suggested by Janka, see: de:Wikipedia:Fragen_zur_Wikipedia#Bilder_.C3.BCberlagern.3F
• Potential syntax: ((hover | bild1 | bild2 | thumb | right | Beschreibungstext))
• Missing: how to implement?

It would be nice if you could advise how to proceed.
Akroti (talk) 20:29, 14 March 2012 (UTC)

Something like this has accessibility problems. What about people who navigate only using the keyboard of voice commands? Granted, ImageAnnotator isn't a prime example in that respect either...

If you still want this, take a look at the French Wikipedia; if I recall correctly, they have slideshows there. Perhaps that can serve as an inspiration. And then there is the jQuery.ucompare plugin, which does something similar.[3]

A JavaScript-based solution is probably not very difficult to implement, but since it would probably be enabled for anyone by default, it would need to be very thoroughly tested, and work or at the very least gracefully degrade on older browsers. I'd say it must work on anything from IE6 on, and not crash or cause other disturbances on older browsers. So you're looking at a significant cross-browser development and testing effort. (Yes, even if you're using jQuery. Don't underestimate testing.) And you should have some sensible way to present the information if JavaScript is inactivated; maybe showing both images side by side, or as a static CSS overlay.

In any case, I have absolutely no time to implement something like this. Lupo 21:34, 14 March 2012 (UTC)

There is also jquery.cycle.all in core but this is, I think, too much as well if you just want to switch 2 images on hover. -- RE rillke questions? 22:48, 14 March 2012 (UTC)

Upload forms

Commons:Village pump#What's gone wrong with the upload form? - made some changes (created a default gadget from). Hopefully they did not break anything. With IE, I had to Ctrl+F5 to make it loading.

The whole code seems not to be for MW 1.19... Perhaps you find the time to update parts of them.

BTW, you can add modules to RL using a dirty hidden-gadget-trick like MediaWiki:Gadgets-definition#AuthorizedUsers-jQueryMousewheel. That could be something for LAPI and your other stuff.

And I now noted that a duplicate category-input in the upload form in IE 8 if HotCat is enabled. Don't know whether it was there before making this change.

If you find more issues, just revert, please. Thank you. -- RE rillke questions? 21:59, 24 March 2012 (UTC)

I knew about that gadget hack, but frankly said, we shouldn't need to use it. RL should recognize not just the built-in (jquery/mediawiki) modules and the gadget modules (ext), but also user modules and mediaWiki-namespace modules.

The double category bar might be caused by importScript having been rewritten in terms of mw.loader.load(), but without the load cache that the old importScriptURI had (it would never load the same URI twice, but mw.loader does).

Do default gadgets work? It doesn't seem to load for me. We made the upload form script originally opt-out because we wanted to have it enabled for newbies, who probably wouldn't know how to enable a gadget. The script was mainly intended to help new uploaders supply enough file information. Since now the upload wizard is the default, I guess that isn't that important anymore. We'll see what the people who used that form and didn't opt-out think about having to enable the gadget.

One ugly side-effect is that the preview button is gone also from the normal form.

Lupo 22:24, 24 March 2012 (UTC)

Yes, default gadgets should work. If it doesn't for you, just revert, please. I don't think they will add support for "MediaWiki" modules, soon. -- RE rillke questions? 23:53, 24 March 2012 (UTC)

Perhaps it does not load because hookEvent('load', ... is called too late. -- RE rillke questions? 23:57, 24 March 2012 (UTC)

With "&debug=true" it works. Might be yet another "var Foo = ..." that would need to become a "window.Foo = ... ". Lupo 07:49, 25 March 2012 (UTC)

Yup, that was it. "var JSconfig = {...};" in MediaWiki:Common.js. When loaded explicitly through the "site" dependency in MediaWiki:Gadget-ImprovedUploadForm.js, it runs inside a closure, and therefore doesn't publish JSconfig. Subsequently, there's a "JSconfig is not defined" error in ImprovedUploadForm, which mw.loader.using catches from the callback and quietly logs in window.console, if that exists. That bit is fixed by changing this to "window.JSconfig = {...}".

A more serious problem is that having an explicit dependency on the "site" module causes this module to be loaded twice. The problem here is that while it is loaded by default, the gadget is loaded and executed first. Hence when ImprovedUploadForm runs, mw.loader.using sees that "site" isn't loaded yet, and queues up a request to load it since it doesn't know that it will be loaded anyway. The same thing appears to happen with the user module, but for that, the server returns an empty script the second time because the "&user=" parameter isn't set in the request. Methinks mw.loader.using should special-case the handling of modules that will be loaded anyway: site, user.groups, and user. See bugzilla:32537. Lupo 21:49, 25 March 2012 (UTC)

A user reported a problem on VillagePump (COM:VP#Possible bug with file uploader.). Since you have the most experience with these scripts, I would be glad, if you could find the problem. Thank you! -- RE rillke questions? 19:20, 19 April 2012 (UTC)

User:Lupo/Simple Photographs

Are you OK with moving User:Lupo/Simple Photographs to Commons:Simple photographs? Please see Commons:Village_pump/Copyright#Commons:Simple_photographs. Thanks. Rd232 (talk) 14:58, 2 April 2012 (UTC)

Sure. It's just my semi-private notes on the subject; it would need polishing. But I guess if you move it, it'll be edited mercilessly in a snap :-) Leave a redirect, though, please. Lupo 21:41, 2 April 2012 (UTC)

OK, thanks, will do. Rd232 (talk) 21:53, 3 April 2012 (UTC)

Swiss Government Portraits - free or not free?

Hi Lupo; I would appreciate it a lot if you could have a look at Commons:Deletion requests/Template:Swiss Government Portrait and state your opinion, which I always found helpful :-). Gestumblindi (talk) 00:34, 20 April 2012 (UTC)

Commons:Bots/Requests/DrTrigonBot: automatic categorization (by bot)

Hello Lupo

I am working on a bot that does image categorization by image content using computer vision (OpenCV) and others. One part of this is a face and eye detection which returns information about the face and eyes positions. Now the "problem"; I would like to use ImageAnnotator to store and display those data, as e.g. on File:2011 Helene Xuan Chaire Forum transitions demographiques economiques Fondation du risque.jpg but as mentioned in Commons:ANN#Examples of inappropriate and not-informative notes: (e.g. 5.) this is no approriate use of ImageAnnotator. I (think to) understand the motivation for this - to add notes as "face" or "eye" is trivial information for a human but not for an algorithm and thus a bot! The data about face and eye position are added to the image description page anyway (semantic wiki, ...) and in my opinion I is a lot more preferrable to have them added by ImageAnnotator in order for a human to check if they match, instead of simple coordinate text. So what do you think about that? What is your oppinion? Do you see a way to satisfy your and my wishes? ;) Thanks and Greetings --DrTrigon (talk) 09:47, 5 May 2012 (UTC)

ImageAnnotator is done completely in client-side JavaScript. Your bot might have a hard time "adding notes through ImageAnnotator"; there's no remote-callable API for doing this. The bot could perhaps just add notes directly by just adding the appropriate note templates to the page itself.

As to whether that's appropriate: I'm not sure. It'll most likely be perceived as clutter by the majority of viewers. ImageAnnotator has no support for "note groups" or "layers"; if it had, one solution might be to make the bot add notes in a special layer that would not be displayed by default. But as I said, there's no support for this.

Perhaps the bot could add a section on a file's talk page (or a subpage of the talk page, don't know off-hand if subpages are enabled in "file talk" namespace). Include the file thumb there, and make the bot add the necessary templates there. See User:Lupo/File:Vista panorámica de Peñíscola desde el castillo.jpg for an example. The notes there are not visible on the file itself, they're just on that particular subpage (and on transclusions of that subpage, as on User:Lupo/FPCtest). Then make the bot just add a template to the file description page with some text like "A bot has identified some faces on this image. Please validate the bot's findings by visiting bot's subpage with the notes." or some such.

This support for local image notes is stable and is used also on COM:FPC and on the "image annotator sandbox" pages that one can create through Help:Gadget-ImageAnnotator#Trying it out. Lupo 10:35, 5 May 2012 (UTC)

To be clear, te adding is not a problem - my bot has already done a few such examples. An API would be great, but I have another working solution - so no hurry. ;)

Yeah I think the "clutter" argument might be "the problem"... ;)

The idea with the talk page could definately be a way to go... clever idea! It is may be not the best thing since image info/data are split between description and talk page, but that seems to me as a minor issue... I'll talk about this idea further in the bot request - may be I will come back to you at some point.

Thanks a lot for your fast and brilliant answer! Greetings --DrTrigon (talk) 13:06, 5 May 2012 (UTC)

ImageAnnotator in der Esperantowikipedia

Hallo, Lupo. Ich wurde darauf hingewiesen, daß der "ImageAnnotator" in der Esperantowikipedia nicht richtig funktioniert. Wie muß ich die Seite eo:MediaWiki:ImageAnnotatorConfig.js ändern, damit die Notizen im Artikelnamensraum funktionieren? Außerdem sollen alle sie sehen können. Leider weiß ich nicht, ob IP-s auch ändern können sollten. Wahrscheinlich doch eher nicht, oder? Gruß --Tlustulimu (talk) 09:58, 28 May 2012 (UTC)

Mit scheint, das Folgende ist nicht mehr aktuell:

Aus eo:MediaWiki:ImageAnnotatorConfig.js:

sharedRepositoryAPI : function ()
{
  return (wgServer.indexOf ('https://') == 0
          ? 'https://secure.wikimedia.org/wikipedia/commons/w/api.php'
          : '//commons.wikimedia.org/w/api.php'
         );
},

das sollte durch Folgendes ersetzt werden:

Aus v:de:MediaWiki:ImageAnnotatorConfig.js:

sharedRepositoryAPI : function ()
{
  return '//commons.wikimedia.org/w/api.php';
},

Dann sollte es wieder funktionieren. Falls immer noch nicht (auch nach einem Neuladen des Browser-Caches nicht!), bitte nochmals melden. Lupo 12:26, 28 May 2012 (UTC)

Hallo, Lupo. Ich habe den Code aktualisiert. Ich hatte das Gadget in meinen Einstellungen aus- und dann wieder angeschaltet, was ja auch den Cache austrickst.

Es funktionieren auf eo:Vikipedio:Bildoj kun notoj nur bei einigen Bildern, aber eben nicht bei allen. Woran könnte das liegen? Komisch ist außerdem, daß auf eo:Uzanto:ArnoLagrange/provejo das linke Bild mit Notizen erscheint. Seltsam ist auch, daß die Notizen in eo:Diskuto:Tibor_Sekelj funktionieren, während es im Artikel eo:Tibor_Sekelj selbst nicht klappt. --Tlustulimu (talk) 13:13, 28 May 2012 (UTC)

Habe mir das 'mal angeschaut. Das Problem ist bugzilla:36839: die MediaWiki-Software kann seit neuestem nicht mehr mit langen (> 511 Zeichen) URLs umgehen, die nicht-ASCII-Zeichen beinhalten. Dagegen kann ich in ImageAnnotateor nichts unternehmen, das muss serverseitig repariert werden. Lupo 14:00, 28 May 2012 (UTC)

Auf welche URL hat der Bug Einfluß? Auf die vom Bild, vom Artikel oder sogar von beiden? --Tlustulimu (talk) 15:10, 28 May 2012 (UTC)

In der normalen Benutzung von Wikipedia oder Schwesterprojekten hat der Bug kaum einen Effekt. Hingegen sind URLs mit mehr als 511 Zeichen bei programmatischen Server-Abfragen über das API, wie ImageAnnotator sie auch macht, keine Seltenheit. Je nachdem, wie vielse Bildchen sich auf einer Seite befinden, und ob deren Namen Nicht-ASCII-Zeichen enthalten, kann es vorkommen, dass die Server eine Anfrage nicht korrekt bearbeiten können. Deshalb funktioniert's ja auch auf eo:Diskuto:Tibor_Sekelj (wenige eingebundene Bildchen: die Anfrage von ImageAnnotator an die Server hat eine kurze URL, und die Server liefern das korrekte Resultat), nicht aber auf eo:Tibor_Sekelj (etwas mehr Bilchen, somit auch eine etwas längere URL in der Server-Anfrage von ImageAnnotator, und schon schlägt der Bug zu und die Server liefern falsche Resultate, nämlich keine mehr für betroffene Bilder deren Namen Nicht-ASCII-Zeichen beinhalten). Lupo 16:46, 28 May 2012 (UTC)

Vielen Danken für die Erklärungen! Höffentlich wird es bald ripariert werden ! --Arno Lagrange ✉ 20:26, 28 May 2012 (UTC)

Habe noch mehr veralteten Code in eo-WP gefunden. Siehe eo:User talk:Tlustulimu. Bitte beachtet, dass seit MediaWiki 1.17 Ihr mindestens ImageAnnotator V2.2b verwenden solltet, und seit ca. MediaWiki 1.19, als Protokoll-relative URLs eingeführt wurden, ImageAnnotator V2.3a verwendet werden sollte. Die Version auf eo-WP ist ImageAnnotator V2.2 von 2010; dass da überhaupt noch etwas funktioniert, grenzt an ein Wunder. Lupo 18:42, 31 May 2012 (UTC)

Ich habe var LAPI_file_store = "http://upload\\.wikimedia\\.org/" zu var LAPI_file_store = "(https?:)?//upload\\.wikimedia\\.org/"; geändert, und nix ist in eo:Tibor Sekelj passiert (keine Verbesserung). Schade ! --Arno Lagrange ✉ 21:04, 31 May 2012 (UTC)

Wie gesagt, ein Upgrade auf V2.3a ist überfällig. Wenn's danach immer noch nicht funktioniert, schau ich nochmals. Lupo 06:09, 1 June 2012 (UTC)

addVIAFdata

Lupo, I am a big fan of User:Inductiveload/addVIAFdata.js tool and would like to propose to add it to the standard set of Commons gadgets; however I am unfamiliar with the process. What would be the steps? --Jarekt (talk) 14:23, 30 May 2012 (UTC)

I'm not sure I understand the question. Are you asking about a social or a technical process?

1. I don't think we have a social process for adding gadgets. Typically, an admin decides that something is worth being a gadget, and then does it.
2. As for the technical side:
   1. Copy User:Inductiveload/addVIAFdata.js to MediaWiki:Gadget-VIAFDataImporter.js.
   2. Create a description of the new Gadget at MediaWiki:Gadget-VIAFDataImporter.
   3. Edit MediaWiki:Gadgets-definition and add the following line in an appropriate category:

      * VIAFDataImporter[ResourceLoader|dependencies=mediawiki.util]|VIAFDataImporter.js

   4. (Optional, but recommended) Write a user manual for the gadget at Help:Gadget-VIAFDataImporter and link it in a talk page header at MediaWiki talk:Gadget-VIAFDataImporter.js. If you have such a user guide, also link it in the gadget description at MediaWiki:Gadget-VIAFDataImporter, and consider redirecting Help talk:Gadget-VIAFDataImporter to MediaWiki talk:Gadget-VIAFDataImporter.js.

I think that's it. If you visit Special:Gadgets after the last step, you should see the new gadget with its description.

HTH, Lupo 18:58, 30 May 2012 (UTC)

I guess I was asking about both social and a technical processes, both are important and I am not involved much in this corner of Commons. Thanks, I will talk with User:Inductiveload and will proceed. --Jarekt (talk) 19:22, 30 May 2012 (UTC)

The security vulnerable should be fixed before. Just go to Creator:" target="anytext and hover the input. This could not be only this friendly message but load an evil script (based on the page's title) that deletes the wikipedia-logo for example, blocks all sysops, ... (FixIt: mw.html.escape(mw.config.get('wgTitle')); or and this is generally a simpler way because you don't have to care a lot about anything $('<input>', { type: 'text', value: mw.config.get('wgTitle'), name: 'viaf_query' }) ) and I think a warning should be added to the gadget-description that is loads scripts form external pages. If it would pass JSHint, or JSLint, it would be great. -- RE rillke questions? 20:52, 30 May 2012 (UTC)

I didn't evaluate the code of this script. $('#viaf_query_input').val() should also be urlencoded in the getJSON() call. But as far as I see it doesn't load scripts from external sites, just JSON(P) data? Lupo 21:14, 30 May 2012 (UTC)

It's upon the server what it returns, right? There is no validation before it's executed, I guess. -- RE rillke questions? 21:21, 30 May 2012 (UTC)

jQuery.getJSON - yes, either as data param of getJSON or as $.param({ query: $('#viaf_query_input').val() }) -- RE rillke questions? 21:25, 30 May 2012 (UTC)

User:Inductiveload would have to answer any technical questions - I can only follow ~ 50% of above conversation. The code is a version of s:en:MediaWiki:Gadget-addViafData.js used on WikiSource modified by its author to run on Commons. I and handful of other users used/tested it for last month. I can not read the code but my (possibly incorrect) understanding is that it uses the page name to construct a search query which is then executed on VIAF website. The results of the query are then used to construct a string with {{Authority control}} template, which is then added to the page. I do not think any other machines or servers are used. See also this discussion. --Jarekt (talk) 23:21, 30 May 2012 (UTC)

Hello all. Firstly, thank you for taking an interest and helping out. Sorry for the long delay, but I have not been around for a while. I have implemented the above suggestions to try to avoid that vulnerability. The data returned is JSONP data. Is there any thing that should be done to protect against dodgy code coming in in case the VIAF server is compromised? Cheers, Inductiveload (talk) 23:51, 5 June 2012 (UTC)

I don't think there is anything you can do, unfortunately browsers have no special JSONP-API.

But I think there is still a problem at show_current_authority_data which injects current_ac_data[0] unescaped into the DOM (e.g. exploitable in this.show_current_authority_data ($('#wpTextbox1').val() )) for example by

{{Authority control|PND=132522136|LCCN=n/94/112934|VIAF=52010985|TSURL=Barack_Obama|bare=1|<script type="text/javascript">alert("Hello! Whahah!");</script>}}

FixIt: this.viafCurrentDataDiv.append($('<tt>', { css: { 'margin-left': '1em' }, id: 'current_authority_control_data', text: current_ac_data[0] })); -- RE rillke questions? 09:30, 6 June 2012 (UTC)

Fixed, and it also passes JSlint (except for regexes and multiple vars, and it assumes a browser, which I think is fair). Thanks for the help with this, and apologies for not using correct idioms. My JS is a still a new-ish skill and I've just picked it up piecemeal as I needed it. Inductiveload (talk) 15:36, 6 June 2012 (UTC)

Just had a quick view on it but looks nice. Perhaps Lupo could check it again before we're going to add it to the gadgets? -- RE rillke questions? 15:55, 6 June 2012 (UTC)

Sorry, I got no time to review the code. Just go ahead, it'll hardly bring MediaWiki to its knees :-) Any lingering bugs can be worked out later. Lupo 20:39, 6 June 2012 (UTC)

Commons:Forum#Bug bei Imports von Flickr

seems to be a problem with the upload form. It would be kind, if you would have a look at it. Thanks in advance. -- Rillke^(q?) 15:31, 30 July 2012 (UTC)

HotCat on Punjabi wiki

Hello. Please help. I definitly did wrong in copying the gadget to pa.wiki or it's Punjabi name (title) there creating the problem? It's not working. Please help fixing it. You can check it here and please try to notify (or contact) me on my English wiki talkpage. --Tari Buttar (talk) 15:05, 8 August 2012 (UTC)

pa:MediaWiki:Gadget-HotCat.js looks fine, but now you should customize it in pa:MediaWiki:Gadget-HotCat.js/local_defaults. And we should have Punjabi user interface texts at MediaWiki:Gadget-HotCat.js/pa. We should have Punjabi translation for these message texts. You could put them at MediaWiki talk:Gadget-HotCat.js/pa; I'd then move them over to the protected MediaWiki namespace.

In pa:MediaWiki:Gadget-HotCat.js/local_defaults, you might define values for:

if (typeof (window.HotCat) != 'undefined') {

// Edit summary localizations: replace the English text by texts in the main language of your wiki

  HotCat.messages.cat_removed      = 'removed [[Category:$1]]';
  HotCat.messages.template_removed = 'removed {{[[Category:$1]]}}';
  HotCat.messages.cat_added    = 'added [[Category:$1]]';
  HotCat.messages.cat_keychange= 'new key for [[Category:$1]]: "$2"'; // $2 is the new key
  HotCat.messages.cat_notFound = 'Category "$1" not found';
  HotCat.messages.cat_exists   = 'Category "$1" already exists; not added.';
  HotCat.messages.cat_resolved = ' (redirect [[Category:$1]] resolved)';
  HotCat.messages.uncat_removed= 'removed {{uncategorized}}';
  HotCat.messages.separator    = '; ';
  HotCat.messages.prefix       = "";
        // Some text to prefix to the edit summary.
  HotCat.messages.using        = ' using [[Help:Gadget-HotCat|HotCat]]';
        // Some text to append to the edit summary. Named 'using' for historical reasons. If you prefer
        // to have a marker at the front, use prefix and set this to the empty string.
  HotCat.messages.multi_change = '$1 categories';
        // $1 is replaced by a number. If your language has several plural forms (c.f. [[:en:Dual (grammatical form)]]),
        // you can set this to an array of strings suitable for passing to mw.language.configPlural().
        // If that function doesn't exist, HotCat will simply fall back to using the last
        // entry in the array.
  HotCat.messages.short_catchange = null;
        // Defaults to '[[' + category_canonical + ':$1]]'. Can be overridden if in the short edit summaries
        // not the standard category name should be used but, say, a shorter namespace alias. $1 is replaced
        // by a category name.

// Mandatory configuration for handling of redirects and disambiguations. Default values are shown here; adapt as needed.

  HotCat.disambig_category  = 'Disambiguation';
        // Any category in this category is deemed a disambiguation category; i.e., a category that should not contain
        // any items, but that contains links to other categories where stuff should be categorized. If you don't have
        // that concept on your wiki, set it to null. Use blanks, not underscores.
  HotCat.redir_category     = 'Category redirects';
        // Any category in this category is deemed a (soft) redirect to some other category defined by the first link
        // to another category. If your wiki doesn't have soft category redirects, set this to null.
  HotCat.uncat_regexp = /\{\{\s*([Uu]ncat(egori[sz]ed( image)?)?|[Nn]ocat|[Nn]eedscategory)[^}]*\}\}\s*(<\!--.*?--\>)?/g ;
        // A regexp matching a templates used to mark uncategorized pages, if your wiki does have that.
        // If not, set it to null.

// Further optional configuration. Default values are shown here; set as desired.

  HotCat.template_categories = {};
        // a list of categories which can be removed by removing a template
        // key: the category without namespace
        // value: A regexp matching the template name, again without namespace
        // If you don't have this at your wiki, or don't want this, set it to an empty object {}.
  HotCat.upload_disabled = false;
        // If upload_disabled is true, HotCat will not be used on the Upload form.
  HotCat.blacklist = null;
        // Single regular expression matching blacklisted categories that cannot be changed or
        // added using HotCat. For instance /\bstubs?$/ (any category ending with the word "stub"
        // or "stubs"), or /(\bstubs?$)|\bmaintenance\b/ (stub categories and any category with the
        // word "maintenance" in its title.

} // end if

If the default value of any of these is fine for the Punjabi wiki, you may omit the corresponding entry.

HTH, Lupo 09:05, 13 August 2012 (UTC)

Category:Arndt Wittig

Etwas unklar, ob er nun "Arnd" oder "Arndt" heißt, aber DNB sagt "Arnd" und eine Ausstellung in Schwedt ebenfalls. Andererseits steht auch auf unserem Bundesarchiv-Bild "Arndt" und GoogleBooks-Treffer gibt es auch ein paar dafür. Kategorie verschieben oder nicht? Auf welcher Basis hast du sie als "Arndt" angelegt, weißt du das noch? Grüße --X-Weinzar (talk) 08:19, 18 August 2012 (UTC)

Die genaue Quelle weiss ich nicht mehr. Ich hatte damals nach dem Bildhauer dieser Skulptur gesucht und offensichtlich Quellen für "Arndt Wittig" gefunden. Wenn der nun "Arnd" heisst (scheint jedenfalls die häufigere Variante zu sein), muss die Kategorie halt umbenannt werden, wobei ich "Arndt" als Category-redirect stehen lassen würde. Lupo 20:16, 19 August 2012 (UTC)

Upload form uselang hack

Hello.

I've been trying to figure out how to get the upload form uselang hack working at hi-wp. I've been told (over IRC) that you might be able to help me with it. Just to be clear, I'm refering to the hack that makes a custom interface message appear over http://commons.wikimedia.org/wiki/Special:Upload?uselang=ownwork

I've created w:hi:Mediawiki:Uploadtext/hi-nonfree, but opening http://hi.wikipedia.org/wiki/Special:Upload?uselang=hi-nonfree does not show the interface message for some reason.

Could you point out what I'm doing wrong/not doing that needs to be done? Thanks and regards--Siddhartha Ghai (talk) 22:23, 28 October 2012 (UTC)

That may just be because the servers cache the interface messages. AFAIK, this cache is refreshed only once every 24h. So, the first approach is to wait 24h. If it then still doesn't appear, something else may be amiss.

You probably also want to change the list of licenses displayed in the drop-down menu. To do that, you'd have to write hi:MediaWiki:Licenses/hi-nonfree and request a configuration change at bugzilla: the global configuration would need to be changed to include the 'licenses' message in the $wgForceUIMsgAsContentMsg variable.

If your Uploadtext/hi-nonfree isn't shown after 24h, you'll probably also need 'uploadtext' in $wgForceUIMsgAsContentMsg.

Also see Commons:Redesigning the upload form, originally written by User:Pfctdayelise when she originally implemented this here.

HTH, Lupo 12:38, 29 October 2012 (UTC)

Thanks a ton. You were right about the caching, the message just started showing up. Also, that page is a great help in localizing the hack. Thank you! --Siddhartha Ghai (talk) 18:54, 29 October 2012 (UTC)

Request at Village Pump

Hi Lupo - you've been suggested as the person most likely to know what's caused a bug I've had with uploading - can you look in on the Commons:Village_pump#Upload_bug to suggest any possible causes, please? Thanks! - MPF (talk) 23:22, 5 December 2012 (UTC)

Problem with de-tile.scm

Hi Lupo, I've tried the de-tile.scm script under Gimp 2.8.2/win32 and always getting an error: "Error: (<unknown> : 17594420) car: argument 1 must be: pair" The files are named 13-0-0.jpg ... 13-28-24.jpg - Do you have an idea whats wrong? --Alexrk2 (talk) 11:46, 9 December 2012 (UTC)

Nevermind. I was able to do the stitching with ImageMagick's montage command line tool. It's pretty fast, but the file names must be in the right alphabetical order.

13-001-001.jpg
13-001-002.jpg
...
13-025-029.jpg

montage *.jpg -mode concatenate -tile 29x25 result.jpg

--Alexrk2 (talk) 13:11, 9 December 2012 (UTC)

Annotator save exception

Hello. For a while I've been unable to save image annotations with Google Chrome (Windows). The save always fails with TypeError: Cannot call method 'replace' of undefined from this line in LAPI.js: tas[i].value = tas[i].value.replace(LAPI.Ajax.getHTML.extraNewlineRE, ""); tas[i] exists and is an element object, but lacks HTML object properties such as value, innerHTML, name, etc. Firefox works for me and doesn't get into that line of code because its isFake == true.

I tracked that difference to parseHTML(): Chrome's getElementById(sanity_check) returns something where Firefox returns null. Thus, Chrome uses the parseFromString() document where Firefox uses the fake document. I've verified that Chrome saves correctly with the fake document, which leads me to think that the comment "(Hm. Maybe we should just always use a fake doc?)", if implemented, could be the solution to my problem. Thanks. Mrwojo (talk) 06:56, 28 December 2012 (UTC)

Looks like fall-out from the switch to HTML5. I'll take a look at this. Reading a page as XML and then treating it as HTML worked fine while the servers were sending HTML4, but with HTML5 that is not entirely correct. Lupo 15:41, 6 January 2013 (UTC)

Should be fixed now. If you reload your browser's cache, it should work again in Chrome. (I indeed opted to always use a fake document to fix this. Some other code may now be unnecessary, but for safety, I left it in. Otherwise I'd have to re-test on umpteen different browser versions, which I'd rather avoid.) Lupo 16:47, 6 January 2013 (UTC)

Verified fixed on Chrome; for completeness I also verified that it continues to work on FF and IE. Thank you! Mrwojo (talk) 18:39, 6 January 2013 (UTC)

You're welcome. I tested FF myself, but omitted Safari/Opera/Konqueror as well as older browser versions. Lupo 06:58, 7 January 2013 (UTC)

File:Deutscher Bund.svg

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

Ziegelbrenner (talk) 17:45, 7 January 2013 (UTC)

Commons_Talk:Upload

Hello, Lupo. You have new messages at Commons_Talk:Upload#Delete Template:PD-USGov-OWI from US Gov't. license pull-down. You may remove this notice at any time by removing the {{Talkback}} or {{Tb}} template.

Grolltech (talk) 03:07, 22 March 2013 (UTC)

Complicated French copyright

Hi Lupo; it has been some time... but sometimes when an opaque copyright question crops up, I think of you ;-) - maybe you could throw some light on the questions at Commons:Village_pump/Copyright#Template:PD-Internationale? If so, then thanks in advance :-) Gestumblindi (talk) 00:19, 1 May 2013 (UTC)

I would think that Asclepias has it right. [4] is a good summary: if on 1995-07-01, a term longer than 70 years already ran, that longer term remains valid. Did a longer term run? Well' it's a musical work, so initially, it got 50 years plus later the wartime extensions (in total 14 years 272 days). In 1985, that was extended to 70 years + wartime extensions for musical works, so 84 years 272 days. So in 1995, it certainly had a longer term, and that term is still valid. See also fr:Prorogations de guerre. I don't quite see how the music of the Internationale could be out of copyright in France yet, given that the composer died in 1932. 1932 + 84 = 2016, then add in the 272 days starting from the composer death day (September 29), which brings us to the middle of 2017. So I guess it'll be PD in France as of January 1, 2018. (The lyrics, of course, already are PD, as the writer died 1887, and no matter what kind of prolongation one wants to apply, their copyright term has expired.) Lupo 06:10, 2 May 2013 (UTC)

How do you find relevant discussions so quickly

Hallo Lupo, magst Du mir verraten, wie du relevante Diskussionen so schnell ausfindig machst? Liest Du oft Deine Beobachtungsliste oder benutzt Du einen Crawler?

Übrigens bin ich nicht besonders interessiert, die Wartung für Cat-a-lot zu übernehmen. Das habe ich nur notgedrungen gemacht und auch bisher eher schlecht als recht (werde demnächst die UI vom Core trennen, modularisieren, in instanzierbare Klassen umwandeln und Unit Tests dafür schreiben; das wird wieder viel Zeit kosten ...)

Gibt es nicht eine Möglichkeit, die gemeinsam verwendeten Komponenten auch gemeinsam zu warten (so dass ich nicht alles kopieren zu brauche; dann stimmt es auch besser mit der Attribution). Ich würde ja gern RL verwenden; das ist aber immer problematisch bei der Einbindung in andere Wikis...

Für verschiedene Anwendungen bin ich noch auf der Suche nach folgendem: Weiß Du ein Script, das einen Wikitext(raw) DOM-Baum aufbaut und mir erlaubt Änderungen daran vorzunehmen? Ich hatte mal auf Skin/Werkstatt gefragt; bisher aber nurde:Benutzer:P.Copp/scripts/preprocessor.js als brauchbar empfunden. Mit etwas Arbeit sollte es auch möglich sein, Vorlagen, Kategorien, Bilder in eigene Auflistungen zu stecken (flat list), was das Arbeiten damit dann ungemein erleichtern wird (man muss sich nicht durch den DOM-Tree hangeln und braucht auch keine Angst vor verkorksten Ersetzungen zu haben).

de:User:PerfektesChaos/js/WikiSyntaxTextMod sieht zwar vielversprechend aus; leider wird mir nicht klar, wie man es nutzen kann. Aussagekräftige Namen wie dO.js und die ganzen Abkürzungen verwirren mich, weshalb ich dessen Schöpfer um Hilfe gebeten habe. Mal sehen, ob und was er antwortet.

Vielen Dank für Deine Hilfe. -- Rillke^(q?) 17:34, 7 May 2013 (UTC)

Es war Zufall, dass ich gerade zu dem Zeitpunkt meine Beobachtungsliste 'mal anschaute.

Natürlich wäre es schön, wenn man das so refactoren könnte, dass gemeinsame Teile nur einmal vorkämen. HotCat jedoch wird auf zig anderen Projekten verwendet, meist durch direkten Import von Commons. Deshalb ist HotCat auch der Einfachheit halber eine einzige Datei. Es genügt, diese zu importieren, und schon hat man ein lauffähiges HotCat auf einem anderen Projekt. Das sollte auch so bleiben, denn wenn man das ändert, läuft man Gefahr, auf zig anderen Projekten Anpassungen vornehmen zu müssen. HotCat wurde auch geschrieben, bevor es RL oder auch nur jQuery hier gab. Heute könnte man da einiges anders machen. Dafür läuft HotCat auch auf alten MW-Versionen (ja, es wird sogar auf nicht-WMF-Wikis verwendet), und auch auf alten Browsern, die von jQuery nicht unterstützt werden (z.B. IE6).

In erster Linie wollte ich einfach darauf hinweisen, dass das BiDi-Problem in HotCat so einigermassen gelöst ist und man sich das dort für Cat-a-lot abkupfern könnte.

Ein wirklich zuverlässiges Wiki_DOM-Script ist mir nicht bekannt. Ist das nicht gerade das Hauptproblem, dass Parsoid/Visual Editor hatten und zu lösen versuchen?

Lupo 20:54, 7 May 2013 (UTC)

Stimmt. Für den VisualEditor müssten sie so etwas geschrieben haben. Werde morgen mal nachgucken. -- Rillke^(q?) 23:12, 7 May 2013 (UTC)

Sie verwenden Parsoid. Grob gesagt gibt action=visualeditor HTML zurück, das mit Attributen gespickt ist, die die Wiki-Syntax enthalten. -- Rillke^(q?) 14:46, 10 June 2013 (UTC)

HotCat in den sorbischen Wikipedien

Hallo, Lupo. Mir ist heute aufgefallen, daß in den beiden sorbischen Wikipedien das Gadget HotCat ziemlich veraltet ist: dsb:MediaWiki:Gadget-HotCats.js und hsb:MediaWiki:Gadget-HotCats.js. Welche Aktualisierung ist besser von den beiden möglichen?

• Einbindung von Commons mit dortiger Lokalisierung
• Kopie von Commons mit Lokalisierung in der entsprechenden Wikipedia.

Gruß --Tlustulimu (talk) 16:01, 12 May 2013 (UTC)

Am besten ist Einbindung von Commons, Lokalisation der UI-Texte auf Commons, und Lokalisation der restlichen Texte (Edit summaries etc.) sowie Konfiguration lokal in dsb:MediaWiki:Gadget-HotCat.js/local defaults (bzw. hsb:MediaWiki:Gadget-HotCat.js/local defaults). Wenn Du mir die Texte für dsb: und hsb: auf MediaWiki talk:Gadget-HotCat.js/dsb und MediaWiki talk:Gadget-HotCat.js/hsb ablegst, kann ich sie in den MediaWiki-NR verschieben. Als Vorlage kannst Du MediaWiki:Gadget-HotCat.js/de verwenden.

Der Vorteil einer Einbindung von Commons ist, dass allfällige Verbesserungen/Korrekturen auch auf den sorbischen WPs direkt verfügbar werden. Selbst die grosse de-WP macht das schon seit einiger Zeit so.

Lupo 16:13, 12 May 2013 (UTC)

Allerdings sehe ich gerade, dass die sorbischen WPs gar nie "unser" HotCat verwendet haben, sondern die Variante aus der Französischen Wikipedia! Da gibt's schon ein paar Unterschiede... hast Du dort 'mal abgeklärt, ob es überhaupt erwünscht ist, das Commons-HotCat (ohne "s" am Schluss!) einzusetzen? Lupo 16:21, 12 May 2013 (UTC)

Ich habe gerade mal auf den beiden Diskussionsseiten wegen der alten Versionen nachgefragt und dort vorgeschlagen, auf die Commons-Version zu wechseln. Wenn sich dort nichts tut, können wir es denn so machen. Die Wahrscheinlichkeit, daß jemand dort antwortet, ist aber sehr gering, weil dort leider ziemlich wenig Benutzer aktiv sind und sich die meisten nicht für den technischen Kram interessieren. --Tlustulimu (talk) 16:51, 12 May 2013 (UTC)

Ja, das ist leider auf den kleinen WPs häufig so. Nur schon deshalb finde ich die Commons-Einbindung besser: einmal eingerichtet, braucht sich dort niemand mehr darum zu kümmern, und es wird automatisch stets die aktuellste Version verwendet. Danke für die Texte, habe diese nun nach MediaWiki:Gadget-HotCat.js/dsb und MediaWiki:Gadget-HotCat.js/hsb verschoben. Damit sind sie aktiviert; wenn Du Deine Spracheinstellung hier nun auf dsb oder hsb änderst (oder einfach ?uselang=dsb and die URL einer Seite hängst), werden die Texte schon verwendet. Lupo 18:20, 12 May 2013 (UTC)

Danke für die Verschiebung der beiden Seiten. Könntest du die beiden Seiten denn noch oben bei "Gadget translations:" auf MediaWiki talk:Gadget-HotCat.js verlinken? Für dsb sollte dort denn "dolnoserbski" und für hsb "hornjoserbsce" stehen, also wie auch bei den Interwikilinks.

Wie lange warte ich denn am besten auf eine Antwort auf meinen Vorschlag? Gruß --Tlustulimu (talk) 11:20, 13 May 2013 (UTC)

Die "Gadget translations" links habe ich auf Template talk:Lang links#Missing languages beantragt. Bezüglich Wartezeit: das ist letztlich Dein Ding. Wenn Du nur auf den Diskussionsseiten des Gadgets nachfragst, wird kaum jemand antworten. Haben diese WPs keine "Village pump"? Aber Du kannst die Umstellung natürlich auch machen, ohne nachzufragen. Erfahrungsgemäss sind dann einige Beutzer ziemlich überrascht... Lupo 12:31, 13 May 2013 (UTC)

MediaWiki talk:UploadForm.js

Hallo Lupo, könntest Du die Anfrage auf MediaWiki talk:UploadForm.js#Shortcut for preview button abwickeln? Es hört sich zwar trivial an; die Tücke lauert aber bekanntlich im Detail. Danke. -- Rillke^(q?) 23:03, 17 May 2013 (UTC)

Danke. -- Rillke^(q?) 17:46, 20 May 2013 (UTC)

MediaWiki:Gadget-HotCat.js/ku

Hi Lupo

könntest du die von mir übersetzte kurdische Version von Gadget-HotCat.js hier hinzufügen.Danke im voraus und Liebe Grüsse--George Animal (talk) 10:56, 30 May 2013 (UTC)

 Done Danke! Lupo 11:30, 30 May 2013 (UTC)

HotCat — A default gadget?

Hi Lupo, after this change, the documentation states that HotCat would be default but I can't see a default flag, neither in MediaWiki:Gadgets-definition nor in $wgDefaultUserOptions. There is an "RfC" now to activate it by default you possibly would like to comment on. Thank you. -- Rillke^(q?) 08:41, 10 June 2013 (UTC)

It was enabled by default at the English Wikipedia. No idea why Phoebe made the edit she did. Lupo 12:56, 10 June 2013 (UTC)

COM:FORUM#MediaWiki:Gadget-ImageAnnotator.js

Hallo Lupo, kannst du auf o. g. Abschnitt mal bitte vorbeischauen und deinen Senf dazu abgeben? Danke --тнояsтеn ⇔ 10:36, 10 June 2013 (UTC)

Und damit es nicht ganz in Vergessenheit gerät: Commons:Forum/Archiv/2013/June#MediaWiki:Gadget-ImageAnnotator.js. Wär schön, wenn sich da was machen ließe. --тнояsтеn ⇔ 19:29, 24 June 2013 (UTC)

Please comment at Commons:Deletion requests/Internationale melody if you can

Other than France and based on w:List of countries' copyright lengths, only Côte d'Ivoire (life + 99 years) and Mexico (life + 100 years) would definitely copyright the Internationale melody while copyrighting non-posthumous works for life plus more than 80 years. Have you heard of any countries and areas that DO honor the very long French copyright term even if longer than their domestic copyright terms? Your thoughts would be greatly appreciated. Thanks.--Jusjih (talk) 05:05, 12 June 2013 (UTC)

MediaWiki:ImageLinks.js issue

Hi Lupo, I just got an error "image_links_desc.google" would be undefined (gadget gallery details) using the German user interface. A look at MediaWiki:ImageLinks.js/de reveals the cause: There are translations that are leaking some keys. Could you take care of the remaining translations? Thanks in advance. -- Rillke^(q?) 11:28, 27 June 2013 (UTC)

Freedom of Panorama in Burkina Faso

Greetings, Lupo. An article on Diébédo Francis Kéré includes a number of photographs of architectural works located in Burkina Faso. Unfortunately, Commons:Freedom of panorama doesn't have any information on whether these are considered derivative works or not. Do you have any information on this? All the best, – Quadell (talk) 18:33, 1 July 2013 (UTC)

The copyright law of Burkina Faso is available at WIPO Lex: [5]. The country does not have full FOP as we need it. See article 25: "except where the image of the work is the main subject of such reproduction or communication and where it is used for commercial purposes." So FOP for non-commercial use only. Lupo 20:36, 1 July 2013 (UTC)