I've worked some more on my SumIrUp tool [1], which can generate a list of language templates with one-line descriptions for a new article. All it needs is a starting point, namely this article in any language. From there, it will spider all the language links, and gather the initial paragraph/sentence of each article. It then generates a copy-and-paste-ready text, including language links.
I was wondering - why not link to this tool in the instructions text for new articles? There could be a link to this tool using the name of the page to be created, and en.wikipedia as default. If an article with that name exists on en.wikipedia, it will generate said list of one-line descriptions which can be copied into that article. As this is exactly what commons articles/categories *should* contain, it might be a huge help.
Magnus
On 18/08/06, Magnus Manske magnus.manske@web.de wrote:
I was wondering - why not link to this tool in the instructions text for new articles?
What instruction text for new articles, exactly? You're welcome to add it yourself, as is anyone.
Or do you mean the "this page doesn't exist. click here to create it" type text?
As this is exactly
what commons articles/categories *should* contain, it might be a huge help.
Well, I have encountered some opposition to the idea that an article with six pictures should have 30 different language introductions. :)
For proper nouns (people & places, mostly), I tend to feel only different scripts are necessary. eg for the Australian city 'Melbourne', there would be at least 40 different articles on it, but 28 of those articles are at exactly "Melbourne". Although if we ever want to supply better quality lang support, it would be best to supply all. Hm. Perhaps better 'hiding' would be better, less annoying at least...
cheers Brianna
Hallo Markus,
Das ist eine wirklich gute Idee, die du da umgesetzt hast.
Ich hätte nur eine kleine Anmerkung: Wenn ich dein Tool mit "en:Soup" befülle, zeigt es auf der Ergebnisseite "{{de|----}}" an, weil der Artikel mit einer Vorlage und einer horizontalen Linie beginnt. Wäre toll, wenn du das beheben könntest.
Schöne Grüße,
Christian
On Fri, 18 Aug 2006 14:07:22 +0100, Magnus Manske magnus.manske@web.de wrote:
I've worked some more on my SumIrUp tool [1], which can generate a list of language templates with one-line descriptions for a new article. All it needs is a starting point, namely this article in any language. From there, it will spider all the language links, and gather the initial paragraph/sentence of each article. It then generates a copy-and-paste-ready text, including language links.
I was wondering - why not link to this tool in the instructions text for new articles? There could be a link to this tool using the name of the page to be created, and en.wikipedia as default. If an article with that name exists on en.wikipedia, it will generate said list of one-line descriptions which can be copied into that article. As this is exactly what commons articles/categories *should* contain, it might be a huge help.
Magnus
I'd like to apologise for my German post to everybody. I didn't check the "To:" in my email client and this mailing list is configured to send replies to back to the list -- I didn't intend that and would like to apologise for it.
Christian
On Fri, 18 Aug 2006 14:39:50 +0100, Christian Richardt cr333@cam.ac.uk wrote:
Hallo Markus,
Das ist eine wirklich gute Idee, die du da umgesetzt hast.
Ich hätte nur eine kleine Anmerkung: Wenn ich dein Tool mit "en:Soup" befülle, zeigt es auf der Ergebnisseite "{{de|----}}" an, weil der Artikel mit einer Vorlage und einer horizontalen Linie beginnt. Wäre toll, wenn du das beheben könntest.
Schöne Grüße,
Christian
On Fri, 18 Aug 2006 14:07:22 +0100, Magnus Manske magnus.manske@web.de wrote:
I've worked some more on my SumIrUp tool [1], which can generate a list of language templates with one-line descriptions for a new article. All it needs is a starting point, namely this article in any language. From there, it will spider all the language links, and gather the initial paragraph/sentence of each article. It then generates a copy-and-paste-ready text, including language links.
I was wondering - why not link to this tool in the instructions text for new articles? There could be a link to this tool using the name of the page to be created, and en.wikipedia as default. If an article with that name exists on en.wikipedia, it will generate said list of one-line descriptions which can be copied into that article. As this is exactly what commons articles/categories *should* contain, it might be a huge help.
Magnus
Commons-l mailing list Commons-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/commons-l
This should be a multilingual list.People are welcome to write in whichever language(s) they choose.
Brianna
On 18/08/06, Christian Richardt cr333@cam.ac.uk wrote:
I'd like to apologise for my German post to everybody. I didn't check the "To:" in my email client and this mailing list is configured to send replies to back to the list -- I didn't intend that and would like to apologise for it.
Christian
On Fri, 18 Aug 2006 14:39:50 +0100, Christian Richardt cr333@cam.ac.uk wrote:
Hallo Markus,
Das ist eine wirklich gute Idee, die du da umgesetzt hast.
Ich hätte nur eine kleine Anmerkung: Wenn ich dein Tool mit "en:Soup" befülle, zeigt es auf der Ergebnisseite "{{de|----}}" an, weil der Artikel mit einer Vorlage und einer horizontalen Linie beginnt. Wäre toll, wenn du das beheben könntest.
Schöne Grüße,
Christian
On Fri, 18 Aug 2006 14:07:22 +0100, Magnus Manske magnus.manske@web.de wrote:
I've worked some more on my SumIrUp tool [1], which can generate a list of language templates with one-line descriptions for a new article. All it needs is a starting point, namely this article in any language. From there, it will spider all the language links, and gather the initial paragraph/sentence of each article. It then generates a copy-and-paste-ready text, including language links.
I was wondering - why not link to this tool in the instructions text for new articles? There could be a link to this tool using the name of the page to be created, and en.wikipedia as default. If an article with that name exists on en.wikipedia, it will generate said list of one-line descriptions which can be copied into that article. As this is exactly what commons articles/categories *should* contain, it might be a huge help.
Magnus
Commons-l mailing list Commons-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/commons-l
Commons-l mailing list Commons-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/commons-l
"Christian Richardt" cr333@cam.ac.uk wrote on Friday, August 18, 2006 3:39 PM:
Das ist eine wirklich gute Idee, die du da umgesetzt hast.
I second that :)
What exactly does "Suggest categories for images on commons page" do?
Thanks for the great tool,
Flo
Florian Straub wrote:
"Christian Richardt" cr333@cam.ac.uk wrote on Friday, August 18, 2006 3:39 PM:
Das ist eine wirklich gute Idee, die du da umgesetzt hast.
I second that :)
Thanks, both of you :-)
What exactly does "Suggest categories for images on commons page" do?
It will have that WikiSense tool suggest categories. It's probably not an important function in this context. I'll leave it in for sentimental reasons ;-)
Magnus
Christian Richardt wrote:
Hallo Markus,
Das ist eine wirklich gute Idee, die du da umgesetzt hast.
Ich hätte nur eine kleine Anmerkung: Wenn ich dein Tool mit "en:Soup" befülle, zeigt es auf der Ergebnisseite "{{de|----}}" an, weil der Artikel mit einer Vorlage und einer horizontalen Linie beginnt. Wäre toll, wenn du das beheben könntest.
Done.
Hi Magnus,
vielen Dank für das tolle Tool. Ich hätte da aber noch zwei kleine Vorschläge für "Missing language links". Zum einen wäre ein Zeilenumbruch nach jedem fehlenden Interwiki-Link zum Rauskopieren praktischer - zum anderen wäre ein [edit]-Button neben dem Link zur Seite mit den fehlenden IW-Links eine Kleinigkeit, die die Produktivität trotzdem noch minimal steigern könnte und die Ladezeit und damit die Serverbelastung reduzieren würde.
Vielen Dank im Voraus,
Flo
-- Wie nennt man den Großvater des ägyptischen Sonnengottes? - Opera ----- Original Message ----- From: "Magnus Manske" magnus.manske@web.de To: "Wikimedia Commons Discussion List" commons-l@wikimedia.org Sent: Friday, August 18, 2006 3:07 PM Subject: [Commons-l] Commons SumItUp
Commons-l mailing list Commons-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/commons-l
Florian Straub wrote:
Hi Magnus,
vielen Dank für das tolle Tool. Ich hätte da aber noch zwei kleine Vorschläge für "Missing language links". Zum einen wäre ein Zeilenumbruch nach jedem fehlenden Interwiki-Link zum Rauskopieren praktischer - zum anderen wäre ein [edit]-Button neben dem Link zur Seite mit den fehlenden IW-Links eine Kleinigkeit, die die Produktivität trotzdem noch minimal steigern könnte und die Ladezeit und damit die Serverbelastung reduzieren würde.
Done.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Magnus Manske schrieb:
I've worked some more on my SumIrUp tool [1], which can generate a list of language templates with one-line descriptions for a new article. All it needs is a starting point, namely this article in any language. From there, it will spider all the language links, and gather the initial paragraph/sentence of each article. It then generates a copy-and-paste-ready text, including language links.
I was wondering - why not link to this tool in the instructions text for new articles? There could be a link to this tool using the name of the page to be created, and en.wikipedia as default. If an article with that name exists on en.wikipedia, it will generate said list of one-line descriptions which can be copied into that article. As this is exactly what commons articles/categories *should* contain, it might be a huge help.
Magnus
A very very nice tool. It's new to me and I will use it in the future.
But we need on Commons a technique to show only those translations of the users language (stored in preferences) with a fallback option to englisch and/or all.
Also usefull for the display of multilanguage descriptions in galleries.
Raymond.
On 31/08/06, Raimond Spekking raimond.spekking@gmail.com wrote:
A very very nice tool. It's new to me and I will use it in the future.
But we need on Commons a technique to show only those translations of the users language (stored in preferences) with a fallback option to englisch and/or all.
Also usefull for the display of multilanguage descriptions in galleries.
This can be achieved via CSS, for individual users. Put this into your monobook.css:
.description { display: none; } .en { display: block; } .de { display: block; }
This will hide all descriptions by default, then show any English or German.
The major problem with this is that the vast majority of text is incorrectly or not at all tagged. This technique works for things tagged like
{{en|Explanation or caption}}
It won't work for things like
{{English}} Explanation or caption
or
'''en:''' Explanation or caption
There is a technique being developed at Meta called "Language select" ( http://meta.wikimedia.org/wiki/Meta:Language_select ), which uses Javascript and CSS, but is also not site-wide. (See that talk page for discussion about using it on Commons)
I guess what we actually need is another entry in Special:Preferences along the lines of 'show these languages' on multilingual sites. Because for the interface, you can only set one language, whereas there are many multilingual people who would be interested in having multiple languages shown. There are also administrative types like myself who are interested in seeing all languages, even though I can't read most of them, to notice what kind of coverage we have, which languages are needed, spot obvious vandalism, etc.
cheers Brianna