Wikisource:Scriptorium/Archives/2013 - Wikisource

Wikisource:Scriptorium/Archives/2013 - Wikisource
Jump to content
From Wikisource
Wikisource:Scriptorium
Assamese Wikisource
edit
Hi,
Assamese Wikisource
has been created today and I have imported the content from
Category:অসমীয়া
and subcategories; they can now probably be deleted here. I put a list on
User:MF-Warburg#Assamese_pages
. Best regards, --
MF-Warburg
talk
20:18, 3 January 2013 (UTC)
reply
Be a Wikimedia fundraising "User Experience" volunteer!
edit
Thank you to everyone who volunteered last year on the Wikimedia fundraising 'User Experience' project. We have talked to many different people in different countries and their feedback has helped us immensely in restructuring our pages. If you haven't heard of it yet, the 'User Experience' project has the goal of understanding the donation experience in different countries (outside the USA) and enhancing the localization of our donation pages.
I am (still) searching for volunteers to spend some time on a Skype chat with me, reviewing their own country's donation pages. It will be done on a 'usability' format (I will ask you to read the text and go through the donation flow) and will be asking your feedback in the meanwhile.
The only pre-requisite is for the volunteer to actually live in the country and to have access to at least one donation method that we offer for that country (mainly credit/debit card, but also real time banking like IDEAL, E-wallets, etc...) so we can do a live test and see if the donation goes through. **All volunteers will be reimbursed of the donations that eventually succeed (and they will be very low amounts, like 1-2 dollars)**
By helping us you are actually helping thousands of people to support our mission of free knowledge across the world. If you are interested (or know of anyone who could be) please email ppena@wikimedia.org. All countries needed (excepting USA)!!
Thanks!
Pats Pena
Global Fundraising Operations Manager, Wikimedia Foundation
Sent using
Global message delivery
, 21:23, 8 January 2013 (UTC)
Bugzilla request to deploy Universal Language Selector here
edit
A user has submitted
bugzilla:44032
to deploy Narayam or Universal Language Selector (ULS) on mulWS. From my (limited) view of where WMF is progressing, it seems to make sense that mulWS (w|sh)ould look to preferably deploy
mw:Extension:Universal Language Selector
. A quick search finds
this
and
this
covers the matter. For those who have seen WebFonts in various places, this is the successor to that.
The primary aim is to allow users to select a language and configure its support in an easy way.
The extension provides the following features:
Flexible and easy way to select a language from a large set of languages.
Selection can be based on geographical region based browsing, searching.
Search can be based on ISO language code, language name written in current user interface language or in its own script(autonym)
Cross language search - search language names using any script
Autocompletion of language names
Auto correction of spelling mistakes in search strings
Geo IP based language suggestions
Language selection based on users browser/OS language
Input methods
An easily selectable input method collection, readily available in every editable field
Provides a large set of input methods for wide range of languages
Per-language input method preferences
Webfonts
A large collection of fonts to choose for each language to use as embedded font for the page
Per-language font preferences
mw:Extension:Universal Language Selector
The change will only take place if a community discussion has taken place (which I am obviously starting), though it would be useful that the community's considered opinion be added to the bugzilla to allow the extension to be added, or for the status quo to remain.
billinghurst
sDrewth
05:09, 17 January 2013 (UTC)
reply
Not that it is my bugzilla, however, I propose that the mulWS community looks to support the deployment on mulWS of the
Universal Language Selector Extension
support
as nominee
billinghurst
sDrewth
support
--
Zyephyrus
talk
08:04, 17 January 2013 (UTC)
reply
support
Tpt
talk
20:04, 17 January 2013 (UTC)
reply
support
Candalua
talk
20:32, 17 January 2013 (UTC)
reply
closing as
supported
and noting to that effect in Bugzilla. I hope that the admins are happy with that approach. If not please disagree in the bugzilla and note whatever reason and for it not to progress.
billinghurst
sDrewth
08:03, 2 February 2013 (UTC)
reply
ULS is now deployed.
Tpt
talk
20:07, 15 February 2013 (UTC)
reply
Is it known than ULS is not compatible with FF 3.6, and perhaps other version ? By not compatible I mean than if you click on the link and start to interact with the window, it display a huge grey area and you can't do anything to recover except close the tab. —
Phe
I don't know. You should report this issue on
bugzilla
Tpt
talk
14:45, 16 February 2013 (UTC)
reply
New feature for the ProofreadPage extension
edit
Creating Index pages starting from the "Search" field is a bit rough. Thus I propose to add a new special page to the
ProofreadPage extension
(potential name: "Special:CreateIndexPage") and to add it to the sidebar's toolbox, under "Upload file".
The special page may include:
an introductory text ("Would you like to transcribe a text from its scans? Ensure they have been uploaded either to
Wikimedia Commons
or here to {{SERVERNAME}}. Then enter the file name without the "File:" prefix in the below text field. [[$1|Learn more about Index pages]]")
a text field for entering the file name without the "File:" prefix. Beside the field, a notification may appear when text is typed or pasted:
✔ This file exists on {{SERVERNAME}}
if there is a file with that name on that domain or both on Wikimedia Commons and on that domain
✔ This file exists on Wikimedia Commons
if there is a file with that name on Wikimedia Commons only
✘ This file exists neither on Wikimedia Commons nor on {{SERVERNAME}}
if there isn't a file with that name
the "Create button"
The special page is especially intended for newcomers. What is your opinion? Who knows how to do this in practice?--
Erasmo Barresi
talk
18:17, 17 January 2013 (UTC)
reply
Answer as contributor: I believe that, instead of creating a new special page and a new link in the sidebar, a better thing to do to help newcomers is maybe to make more visible the link to the index pages in the file pages (
an example of file page
) because, before creating an index page, the user will search for a scan and, so, go to the file page. But there is an issue with that work-flow: this link isn't shown currently in commons if the description of the file doesn't use the book template with the Wikisource field. In the future, it would be wonderful to have a specific version of the upload wizard for books that allow to set fields of the Book template and create the index page in Wikisource.
Tpt
talk
20:06, 18 January 2013 (UTC)
reply
Answer as ProofreadPage maintainer: if there is a consensus of the community to create this index page, I am ready to create it and integrate it into the extension. It's a very easy thing.
Tpt
talk
20:06, 18 January 2013 (UTC)
reply
Can I come back to the basic premise. Do people searching at one of the Wikisources arrive with the intention of transcribing a book? Further if they are new to the sites, is the first thing that we want them to be doing is to say "I will transcribe 'such and such' a book? and start on the process from scratch and in isolation? My guess is that we will have a whole lot of Index: pages created and not a lot more in the way of transcription, and I am seeing other possible errors like .jpg book covers, etc. having an index page. To me, the introductory component is correct and this is about the engagement and the help. If we don't have a specific work, then we should be looking to engage people context specific and helpful information, point them to where they can find help and ask questions about how to start. We may come to having a special tool, however, the wish and intent to transcribe should first be tested and supported.
To Tpt's suggestion about File: ns pages, I do like your idea on being clever in that regard. I cannot see how you have implemented
MediaWiki:Proofreadpage image message
, though presume that it relies on an
#ifexist:
test. So we just need the ability to configure when the result is
does not exist
and I would suggest that it is to help pages (specialised?) where each WS can have their context relevant and customised help text.
billinghurst
sDrewth
23:50, 19 January 2013 (UTC)
reply
No, most people visiting Wikisource do not have the intention of transcribing a book. Nevertheless, we must lead visitors to transcribe a book. As an example, Commons and YouTube have got an "Upload" button. Wikipedia articles start from red links, as well as Wikisource author pages and main-namespace pages. Instead, Index pages have got no place to start from. This does not mean that we should encourage users to starting transcriptions that they will never finish.--
Erasmo Barresi
talk
19:57, 21 January 2013 (UTC)
reply
Erasmo, to
lead
our visitors would result into making them angry and with some reason don’t you think so?  :) there is no obligation to do that. — Clear indications about how to help to build the world library that we are building, in case our readers wish to help, is a different thing though, so I agree with this side of your proposition. --
Zyephyrus
talk
14:14, 22 January 2013 (UTC)
reply
I wrote
lead
in the sense of
guide
them to the right place. Other websites are more successful because thy are more intuitive.--
Erasmo Barresi
talk
16:51, 22 January 2013 (UTC)
reply
There is a strange synchronicity because I discussed the very same issue in private with other wikilibrarians just few days ago :-). My original idea was to pre-load the template book in Commons, when there a .djvu is uploaded. this would be useful for wikilibrarians and would add a bit of coherence there.
A special Upload Wizard, for wikisources, is of course much needed. It would be very useful for both experienced users and newcomers to be able to just stay on Wikisource and upload (from here!) a book on Commons. But this would also need a lot of work for metadata. As you all very well know we write metadata on Commons (book template), Wikisource (index and ns0 header) and sometimes even Wikipedia. It would be massively useful to store the data on Wikidata, and have them all transcluded in various wiki projects when needed. Moreover, just think about that we never use OpenLibrary/Worldcat/OPAC metadata for our books, and that we are just recataloguing them for the nth time... Could we maybe discuss a strategy as Wikilibrarians all together?
Aubrey
talk
15:59, 28 January 2013 (UTC)
reply
Really, I think we should wait for further developments in order to use Wikidata for this purpose. Currently, Wikidata handles neither Wikisource links nor infoboxes.--
Erasmo Barresi
talk
19:02, 30 January 2013 (UTC)
reply
See
#Grant_application_for:_.22New_Wikisource_relationship_with_Commons.2C_Wikidata_and_Wikipedia.22
. :-)
Aubrey
talk
11:11, 31 January 2013 (UTC)
reply
Wikimedia sites to move to primary data center in Ashburn, Virginia. Read-only mode expected.
edit
(Apologies if this message isn't in your language.) Next week, the Wikimedia Foundation will transition its main technical operations to a new data center in Ashburn, Virginia, USA. This is intended to improve the technical performance and reliability of all Wikimedia sites, including this wiki. There will be some times when the site will be in read-only mode, and there may be full outages; the current target windows for the migration are January 22nd, 23rd and 24th, 2013, from 17:00 to 01:00 UTC (see
other timezones
on timeanddate.com). More information is available
in the full announcement
If you would like to stay informed of future technical upgrades, consider
becoming a Tech ambassador
and
joining the ambassadors mailing list
. You will be able to help your fellow Wikimedians have a voice in technical discussions and be notified of important decisions.
Thank you for your help and your understanding.
Guillaume Paumier
, via the
Global message delivery system
wrong page? You can fix it.
15:48, 19 January 2013 (UTC)
reply
Picture of the Year voting round 1 open
edit
Dear Wikimedians,
Wikimedia Commons is happy to announce that the 2012 Picture of the Year competition is now open. We're interested in your opinion as to which images qualify to be the Picture of the Year for 2012. Voting is open to established Wikimedia users who meet the following criteria:
Users must have an account, at any Wikimedia project, which was registered
before Tue, 01 Jan 2013 00:00:00 +0000
[UTC].
This user account must have more than
75 edits
on
any single
Wikimedia project
before Tue, 01 Jan 2013 00:00:00 +0000
[UTC]. Please check your account eligibility at the
POTY 2012 Contest Eligibility tool
Users must vote with an account meeting the above requirements either on Commons or another SUL-related Wikimedia project (for other Wikimedia projects, the account must be attached to the user's Commons account through
SUL
).
Hundreds of images that have been rated Featured Pictures by the international Wikimedia Commons community in the past year are all entered in this competition. From professional animal and plant shots to breathtaking panoramas and skylines, restorations of historically relevant images, images portraying the world's best architecture, maps, emblems, diagrams created with the most modern technology, and impressive human portraits, Commons features pictures of all flavors.
For your convenience, we have sorted the images into topic categories. Two rounds of voting will be held: In the first round, you can vote for as many images as you like. The first round category winners and the top ten overall will then make it to the final. In the final round, when a limited number of images are left, you must decide on the one image that you want to become the Picture of the Year.
To see the candidate images just go to
the POTY 2012 page on Wikimedia Commons
Wikimedia Commons celebrates our featured images of 2012 with this contest. Your votes decide the Picture of the Year, so remember to vote in the first round by
January 30, 2013
Thanks,
the Wikimedia Commons Picture of the Year committee
This message was delivered based on
m:Distribution list/Global message delivery
. Translation fetched from:
commons:Commons:Picture of the Year/2012/Translations/Village Pump/en
--
Rillke
talk
23:57, 22 January 2013 (UTC)
reply
Bot request;
RileyBot
edit
I request a bot flag for my bot
Operator: -
Riley Huntley
Purpose: Fix broken and double redirects.
Script used: Python, pywikipedia.
Already has the bot flag on: enwikivoyage, frwikivoyage and enwikipedia.
Riley Huntley
(SWMT)
04:24, 27 January 2013 (UTC)
reply
Malaysian Wikisource
edit
Hi, I would like to suggest moving
Perlembagaan Persekutuan Malaysia
and it's subpages to prefix Ms/. (by way of
meta:Requests for new languages/Wikisource Malay
). See also unindexed page in
Category:Bahasa Melayu
I'm comparing it with
Jv
and
Category:Javanese
, so CMIIW
Bennylin
talk
14:38, 29 January 2013 (UTC)
reply
Help turn ideas into grants in the new IdeaLab
edit
I apologize if this message is not in your language. Please help translate it.
Do you have an idea for a project to improve this community or website?
Do you think you could complete your idea if only you had some funding?
Do you want to help other people turn their ideas into project plans or grant proposals?
Please join us in the
IdeaLab
, an incubator for project ideas and Individual Engagement Grant proposals.
The Wikimedia Foundation is seeking new ideas and proposals for Individual Engagement Grants. These grants fund individuals or small groups to complete projects that help improve this community. If interested, please submit a completed proposal by February 15, 2013. Please visit
for more information.
Thanks! --
Siko Bouterse, Head of Individual Engagement Grants, Wikimedia Foundation
20:59, 30 January 2013 (UTC)
reply
Distributed via
Global message delivery
. (Wrong page?
Correct it here
.)
Grant application for: "New Wikisource relationship with Commons, Wikidata and Wikipedia"
edit
Since the Wikidata project is allowing us new ways of handling content, I have started a grant proposal to define a vision about how to integrate Wikisource content in Commons and Wikipedia. Please, check my
grant application
and share your thoughts. Thanks! --
Micru
talk
06:42, 28 January 2013 (UTC)
reply
Copied the above from
commons:COM:VP
: for mysterious reasons, it wasn't shared with Wikisource. --
Nemo
08:20, 31 January 2013 (UTC)
reply
Please comment on Individual Engagement Grant proposals until February 21
edit
I apologize if this message is not in your language. Please help translate it.
The Wikimedia Foundation is considering
Individual Engagement Grant
proposals from community members. Please
join the discussion
and share your thoughts about these ideas, until February 21. The following proposal may be of particular relevance for this Wikimedia project:
Grants:IEG/Elaborate Wikisource strategic vision
(10000 EUR)
Thanks! --
Siko Bouterse, Head of Individual Engagement Grants, Wikimedia Foundation
01:05, 20 February 2013 (UTC)
Distributed via
Global message delivery
. (Wrong page?
Correct it here
.)
reply
Picture of the Year 2012
edit
Results, here’s the winner:
Pair of Merops apiaster feeding
European Bee-eater
Ariège
, France.
The female (in front) awaits the offering which the male will make...
--
Zyephyrus
talk
19:00, 22 February 2013 (UTC)
reply
Fable de Schleicher
edit
Hi,
fr:Fable de Schleicher
is proposed for deletion on the french-speaking wikisource (writen by August Schleicher, 1821 – 1868 ; see
w:en:Schleicher's fable
for some more explanations). What do you think : could these texts be import on oldwikisource or not ?
Cdlt,
VIGNERON
talk
11:14, 2 March 2013 (UTC)
reply
Self-link to wikidata
edit
Hi all.
I mounted into it.wikisource, commons and it.wikivoyage a sctipt derived from the tool suggested [
here
] and it runs.It adds a link to wikidata into any page with an item into wikidata; and it saves into a $("body").data() variable the whole set of data got from wikidata. I'm going to test a old.wikisource version of it here into
User:Alex brollo/common.js
: feel free to use it if you like.
Italic text
--
Alex brollo
talk
17:35, 4 March 2013 (UTC)
reply
Test the result here (it runs!):
Author:Giuseppe Peano
. I'm going to mount the same script into
en:User.Alex brollo/common.js
, I found that here Authors linking to wikidata are not so many. --
Alex brollo
talk
17:44, 4 March 2013 (UTC)
reply
Convert complex templates to Lua to make them faster and more powerful
edit
(Please consider translating this message for the benefit of your fellow Wikimedians)
Greetings. As you might have seen on the
Wikimedia tech blog
or the
tech ambassadors list
, a new functionality called "Lua" is being enabled on all Wikimedia sites today.
Lua
is a scripting language that enables you to write faster and more powerful MediaWiki templates.
If you have questions about how to convert existing templates to Lua (or how to create new ones), we'll be holding two support sessions on IRC next week:
one on Wednesday
(for Oceania, Asia & America) and
one on Friday
(for Europe, Africa & America); see
m:IRC office hours
for the details. If you can't make it, you can also get help at
mw:Talk:Lua scripting
If you'd like to learn about this kind of events earlier in advance, consider becoming a
Tech ambassador
by subscribing to the
mailing list
. You will also be able to help your fellow Wikimedians have a voice in technical discussions and be notified of important decisions.
Guillaume Paumier
, via the
Global message delivery system
20:30, 13 March 2013 (UTC)
wrong page? You can fix it.
reply
Wikisources asked for ideas re: Google Summer of Code
edit
WMF has prodded me and wanted to make sure that the Wikisources were putting on their thinking caps for Google Summer of Code
It's time to start defining what we want our Google Summer of Code to be all about. Let's look at the ideas we are proposing to potential students:
mw:Mentorship programs/Possible projects
Many of the ideas listed there are too generic ("Write an extension"), improvements of existing features ("Improve Extension:CSS") or work-in-progress tasks ("Fix Parsoid bugs"). Many others are not directly related with development, and therefore not suitable either for GSOC.
After this filtering, we seem to be left with:
Article evolution playback tool idea
An easy way to share wiki content on social media services
Write an extension to support XML Sitemaps without using command line
Extension:OEmbedProvider
Add support for x3d 3D files to MediaWiki
Allow smoother and easier Wikimedia Commons pictures discovery
Build an interwiki notifications framework and implement it for InstantCommons
Automatic category redirects
(If you think your project should also be considered here please speak up!)
Most of these projects seem to be extension (and PHP?) centric. Can we have more diversity? Maybe gadgets and templates are too simple for a GSOC project? What about the mobile front? Do we have skin development projects that could make it here? Anything in the DevOps area? Anything the MediaWiki core maintainers would like to see happening?
It would be also nice to have more candidates benefiting specific Wikimedia projects. Beyond Wikipedia, we have several proposals related to Commons. Wikidata seems to be joining soon. What else? Could this be a chance to help Wiktionary, Wikibooks or any other project with specific needs craving for tech attention?
Also to the many students that have already showed their interest: feel free pushing your project ideas now!
—Quim Gil, Technical Contributor Coordinator @ Wikimedia Foundation, via mailing lists
We have some information at
Wikisource:Wishlist
, however, this is probably the opportunity to think of a fresh idea that is an opportunity for a short and limited time period.
I am going to send similar to the Wikisource-l mailing list and to enWS, and ask for them to contribute here. I think that something that is holistic for the WSes is more likely than a single wiki suggestion.
billinghurst
sDrewth
01:59, 23 March 2013 (UTC)
reply
I copy here a mail I sent to wikisource-l:
That is a really good opportunity. We also have
that we set up at Wikimania 2012. Few of those thought are now in the Wikisource Grant proposal, too:
I would say that a proper metadata handling system is maybe the first priority, but maybe we can accomplish that via Lua templates on WS and metadata stored in Wikidata.
Another thing would be working with OKFN tools for seeking and integration (TEXTUS, for example).
Moreover, Djvu support/handling was an interest also of the WMF:
Well, there's a lot of stuff we can do :-)
Aubrey
talk
11:45, 23 March 2013 (UTC)
reply
An idea: One-click import from the Internet Archive, with Djvu upload to Wikimedia Commons, same metadata, right copyright template, create Index page on the right language version of Wikisource, create all Pages with the existing OCR text, so they are ready for Google indexing, and later proofreading.
The user finds an interersting book at the Internet Archive.
User presses one button.
The text is ready for proofreading.
No, I'm not volunteering to write the software. --
LA2
talk
16:21, 23 March 2013 (UTC)
reply
There is already
that allows to upload easily IA files to Wikimedia Commons.
I've opened a GSoc proposal about Proofread Page in order to improve Page: pages edition interface and allow edition of these pages with the
Visual Editor
Tpt
talk
06:29, 9 April 2013 (UTC)
reply
idea (hope not too late); request wikisource upload wizard - process flow = upload pdf to commons -> automatically convert to deja-vu -> automatically create work & toc at wikisource -> automatically match and split pages at source
the objective is to provide a tool for cultural professionals who are not coders to upload their content. design of user experience will be the hard part ?
Slowking4
talk
16:32, 9 April 2013 (UTC)
reply
Wikisource improvements for Summer of Code 2013
edit
Hello! I am planning to submit a proposal regarding
Extension:Collection
for this summer's
Google Summer of Code
and
Outreach Program for Women
. I'm still working to narrow down the focus of this project, as I have many ideas on what can be improved (idea page can be found at
User:GorillaWarfare/GSoC
). My ideas include improvements that would affect Wikisource. Currently, printing or saving a Wikisource book is quite challenging, as the Collection extension has no way of identifying which pages make up a book. One of my project ideas is implementing a method to associate various pages with a book, an idea which will have more benefits to Wikisource than just improving printing and export. The other parts of my proposal include improving Extension:Collection's ease of use, improving exportation quality and possibly expanding the list of formats to which books and articles can be exported, adding easy formatting options to Extension:Collection, and various others.
I was hoping to get some feedback from the Wikisource community about these ideas. Do you think they're feasible (keeping in mind I'm certainly not planning to tackle
all
of these in a three-month period)? Are these changes you'd personally like to see? Are there other related improvements that you'd be interested in? Really, any advice/critique/comments/suggestions would be very much appreciated. Thank you!
GorillaWarfare
(talk)
13:31, 8 April 2013 (UTC)
reply
Hi! That is great,
Aubrey
and
me
we are working on
this grant
. Maybe we could have a talk soon? I'll send you an email with more information.--
Micru
talk
18:21, 9 April 2013 (UTC)
reply
I look forward to hearing from you.
GorillaWarfare
(talk)
19:29, 9 April 2013 (UTC)
reply
As an update, I've started
my actual proposal
. Instead of focusing on Extension:Collection, I'm going to focus my proposal on
Extension:BookManager
. The problem with effectively printing an entire book is blocked by the need to organize a book's individual pages and chapters into a single unit, and I'm excited about the developments that solving this problem will allow:
dependencies of bug 15071
. I'm hoping to receive feedback on this, as it's an extension I'm really hoping to see deployed on Wikisource and Wikibooks.
GorillaWarfare
(talk)
02:12, 16 April 2013 (UTC)
reply
Lost Collection extension issues
edit
Here's a list of issues that would use help of people using the Collection extension and knowing if they're still valid. Same can be said of
those on bugzilla
, which at least are not lost. --
Nemo
11:26, 12 April 2013 (UTC)
reply
Copyright Issues by Language
edit
I looked at
Wikisource:Language policy
and did not find any guidance on this question.
At English Wikisource we are in the process of approving a policy to allow translations with a requirement that requires a
"scan supported original language work on the appropriate language wiki"
. It has been pointed out in
this discussion
that do to different copyright concerns, some works that are PD in English are not PD in the original language. Would here (oldwikisource) be an appropriate language wiki for works that are PD in the US but not in the country/language of origin?
JeepdaySock
talk
14:39, 17 April 2013 (UTC)
reply
See
here
and
older discussion
. But I don't think it's a good idea anymore, because it might lead to competition with the other WS-language-domains etc. --
D.H
talk
15:17, 17 April 2013 (UTC)
reply
I disagree, the first link D.H. provides is to long standing policy; such works do and should exist here. For example, the pre-1923 works of Hermann Hesse won't be PD in Germany and therefore not eligible for posting on de.ws until 2032. They are PD in the US, this would include the German version of Siddhartha and many of his other works. I am currently (albeit very slowly) working on a collection of his poetry here.--
Doug.
talk
contribs
20:09, 26 April 2013 (UTC)
reply
Implementing Easier and More Efficient Metadata Tags on Wikisource
edit
Disclosure: I am contracted by Creative Commons
LRMI Project
I would like to propose adopting the use of a by-default-disabled Mediawiki metadata feature that would greatly improve the organization and search engine visibility of the content of Wikisource. These metadata tags are part of Schema.org which was developed by Google, Bing, Yahoo, and Yandex, and can be viewed
here
. The benefit of these tags is that when used within educational content such as on Wikisource, the information contained on the page is made into a way that is easily intelligible to machines by changing just one line with the Mediawiki configuration. An example of MediaWiki using Schema can be seen by using Google's
testing tool
. These metatags were originally developed by LRMI but their recent adoption of Schema.org is a huge milestone that has great potential to improve the efficiency of the way we are able to search educational resources and content on places like Wikisource.
Maximilian.Klein.LRMI
talk
22:21, 18 April 2013 (UTC)
reply
Request for comment on inactive administrators
edit
(Please consider translating this message for the benefit of your fellow Wikimedians. Please also consider translating
the proposal
.)
Read this message in English
Lleer esti mensaxe n'asturianu
বাংলায় এই বার্তাটি পড়ুন
Llegiu aquest missatge en català
Læs denne besked på dansk
Lies diese Nachricht auf Deutsch
Leś cal mesag' chè in Emiliàn
Leer este mensaje en español
Lue tämä viesti suomeksi
Lire ce message en français
Ler esta mensaxe en galego
हिन्दी
Pročitajte ovu poruku na hrvatskom
Baca pesan ini dalam Bahasa Indonesia
Leggi questo messaggio in italiano
ಈ ಸಂದೇಶವನ್ನು ಕನ್ನಡದಲ್ಲಿ ಓದಿ
Aqra dan il-messaġġ bil-Malti
norsk (bokmål)
Lees dit bericht in het Nederlands
Przeczytaj tę wiadomość po polsku
Citiți acest mesaj în română
Прочитать это сообщение на русском
Farriintaan ku aqri Af-Soomaali
Pročitaj ovu poruku na srpskom (Прочитај ову поруку на српском)
อ่านข้อความนี้ในภาษาไทย
Прочитати це повідомлення українською мовою
Đọc thông báo bằng tiếng Việt
使用中文阅读本信息。
Hello!
There is
a new request for comment
on Meta-Wiki concerning the removal of administrative rights from long-term inactive Wikimedians. Generally, this proposal from stewards would apply to wikis without an administrators' review process.
We are also compiling a
list of projects
with procedures for removing inactive administrators on the talk page of the request for comment. Feel free to add your project(s) to the list if you have a policy on administrator inactivity.
All input is appreciated. The discussion may close as soon as 21 May 2013 (2013-05-21), but this will be extended if needed.
Thanks,
Billinghurst
(thanks to all the
translators
!)
05:29, 24 April 2013 (UTC)
reply
Distributed via
Global message delivery
(Wrong page?
You can fix it
.)
Wikisource vision development: News April 2013
edit
I apologize if this message is not in your language. Please help translate it.
Dear Wikisourcerors, it has been almost a month since we have started with the
Elaborate Wikisource strategic vision
grant and we would like to share some news with you:
The
Wikisource vision development
pages are open to discussion. Specially important: what do you think of creating together an international
Wikisource User Group
In case some Wikisources want to use Wikidata to store book metadata and share it with Commons, we have started
Wikidata:Books task force
to decide which properties are needed. We think it's very important to discuss book metadata there, both for Wikisource and for all other projects.
We also started some relevant Requests for Comments for Wikisource:
Interproject links interface
: how can we improve sister projects visibility?
Musical score transcription project proposal
: now that
Extension:Score
allows musical scores both in
Wikipedia
and in (
example 1
example 2
), we need to define where we want music sheets to be hosted.
We are following and promoting a Google Summer of Code project for Wikisource:
Improve support for book structures
. We are also helping to convert the
UploadWizard customisation for books
proposal into another GSoC.
First contacts have been initiated with Open Library, Internet Archive and Open Knowledge Foundation for possible partnerships. Please check out
this page
And that's it for now! During the month of May, we (
Aubrey and Micru
) would like to organize at least one Skype or Google Hangout meeting for the users of each one of the
10 biggest wikisources
plus another one or two for the other languages (depending on interest). We want to know your opinion on what Wikisource should become in the next years.
Thanks! --
Micru
and
Aubrey
01:01, 27 April 2013 (UTC)
Distributed via
Global message delivery
. (Wrong page?
Correct it here
.)
[en] Change to wiki account system and account renaming
edit
Some accounts will soon be renamed due to a technical change that the developer team at Wikimedia are making.
More details on Meta
(Distributed via
global message delivery
04:18, 30 April 2013 (UTC). Wrong page?
Correct it here
.)
[en] Change to section edit links
edit
The default position of the "edit" link in page section headers is going to change soon. The "edit" link will be positioned adjacent to the page header text rather than floating opposite it.
Section edit links will be to the immediate right of section titles, instead of on the far right. If you're an editor of one of the wikis which already implemented this change, nothing will substantially change for you; however, scripts and gadgets depending on the previous implementation of section edit links will have to be adjusted to continue working; however, nothing else should break even if they are not updated in time.
Detailed information and a timeline
is available on meta.
Ideas to do this all the way to 2009 at least. It is often difficult to track which of several potential section edit links on the far right is associated with the correct section, and many readers and anonymous or new editors may even be failing to notice section edit links at all, since they read section titles, which are far away from the links.
(Distributed via
global message delivery
19:07, 30 April 2013 (UTC). Wrong page?
Correct it here
.)
Tech newsletter: Subscribe to receive the next editions
edit
Latest
Tech news
from the Wikimedia technical community.
Please inform other users about these changes.
Recent software changes
(Not all changes will affect you.)
The latest version of MediaWiki (version
1.22/wmf4
) was added to non-Wikipedia wikis on May 13, and to the English Wikipedia (with a Wikidata software update) on May 20. It will be updated on all other Wikipedia sites on May 22.
[1]
[2]
A software update will perhaps result in temporary issues with images. Please
report any problems
you notice.
[3]
MediaWiki recognizes links in twelve new
schemes
. Users can now link to
SSH
XMPP
and
Bitcoin
directly from wikicode.
[4]
VisualEditor was added to
all content namespaces
on mediawiki.org on May 20.
[5]
A new extension ("TemplateData") was added to all Wikipedia sites on May 20. It will allow a future version of VisualEditor to
edit templates
[6]
New sites:
Greek Wikivoyage
and
Venetian Wiktionary
joined the Wikimedia family last week; the total number of project wikis is now 794.
[7]
[8]
The logo of 18 Wikipedias was changed to
version 2.0
in a
third group of updates
[9]
The
UploadWizard
on Commons now shows links to the old upload form in 55 languages (
bug 33513
).
[10]
Future software changes
The next version of MediaWiki (version 1.22/wmf5) will be added to Wikimedia sites starting on May 27.
[11]
An updated version of
Notifications
, with new features and fewer bugs, will be added to the English Wikipedia on May 23.
[12]
The
final version
of the "single user login" (which allows people to use the same username on different Wikimedia wikis) is moved to August 2013. The software will
automatically rename
some usernames.
[13]
new discussion system
for MediaWiki, called "Flow", is under development. Wikimedia designers need your help to inform other users,
test the prototype
and discuss the interface.
[14]
The Wikimedia Foundation is hiring people to act as links between software developers and users for VisualEditor.
[15]
Tech news
prepared by
tech ambassadors
and posted by
Global message delivery
Contribute
Translate
Get help
Give feedback
Unsubscribe
• 21:21, 20 May 2013 (UTC)
Important note:
This is the first edition of the
Tech News
weekly summaries, which help you monitor recent software changes likely to impact you and your fellow Wikimedians.
If you want to continue to receive the next issues every week
, please
subscribe to the newsletter
. You can subscribe your personal talk page and a community page like this one. The newsletter can be
translated into your language
You can also
become a tech ambassador
help us write the next newsletter
and
tell us what to improve
. Your feedback is greatly appreciated.
guillom
21:21, 20 May 2013 (UTC)
reply
I've added our scriptorium to the targets list. --
Zyephyrus
talk
22:03, 20 May 2013 (UTC)
reply
Tech news: 2013-22
edit
Latest
tech news
from the Wikimedia technical community.
Please inform other users about these changes.
Recent software changes
(Not all changes will affect you.)
The
Translate extension
and
Universal Language Selector
were enabled on Wikimedia Commons on May 20. Commons users can now easily change languages, and translate pages with a friendly interface.
[16]
The
Notifications
feature, active on the English Wikipedia, now supports
local blacklists and whitelists
. It is possible to hide users (for example certain bots) from all notifications on the wiki. Also, e-mail notifications are now grouped.
[17]
[18]
The first stable release of
MediaWiki 1.21
for sites outside Wikimedia was published on May 25.
[19]
The tool storing information about languages (
CLDR
) was updated to the
latest version
(23.1).
[20]
Due to a
software issue
, users couldn't enable or disable
Gadgets
. The issue is now fixed.
Future software changes
MediaWiki will stop supporting
XHTML 1.0
and
HTML
versions lower than version 5.
HTML5
will now be the default language for pages created by the software.
[21]
[22]
The software will check if all uploaded files are secure and match their
type
[23]
The Wikimedia Commons
Android app
will come out of the
beta phase
on its next release.
[24]
Account creation by manual log-in will now be recorded in the
account creation log
bug 42434
).
[25]
Links to file description pages will again be accessible directly from within videos (
bug 43747
).
[26]
The software behind recent changes patrolling was re-written; the change fixes issues related to patrolling new pages, among other things.
[27]
During a
meeting
, developers
agreed on rules
about making big changes to the software.
[28]
There is now a category to list pages with invalid
music code
[29]
Tech news
prepared by
tech ambassadors
and posted by
Global message delivery
Contribute
Translate
Get help
Give feedback
Unsubscribe
Help!!!
edit
I'm in serious need of help at Wikilivres.ca. We have been under persistent attack by spammers, and no-one has the technical skills to implement Captcha's or other countermeasures. Less urgent but still important is a need to upgrade the software from version 1.16, and to deal with the extremely slow speed of the site. Help will be very appreciated.
Eclecticology
talk
09:37, 2 June 2013 (UTC)
reply
Hi! A quick fix is maybe to block the account creation right of anonymous user. It can be done by adding to your LocalSettings.php
$wgGroupPermissions
'*'
][
'createaccount'
false
$wgGroupPermissions
'user'
][
'createaccount'
true
PS: If you give me a shell access to your server I can upgrade your Wiki to 1.19 (the
long term support version
) and install the
mw:Extension:ConfirmEdit
that use the reCapcha service. I'm
the current maintainer of the ProofreadPage extension
Tpt
talk
13:15, 3 June 2013 (UTC)
reply
That would be great! I have given User:Alan.ca your name and mediawiki link so that he can give the necessary permissions. I have cPanel access to the site but that does not seem to be enough. I could say more about the situation ... but not in public.
Eclecticology
talk
23:38, 3 June 2013 (UTC)
reply
Sorry, I've to do something unexpected this week and the next one. So I won't be able to work on Wikilivres these two weeks. Sorry again.
Tpt
talk
17:10, 4 June 2013 (UTC)
reply
OK, I can understand. Still if you make contact with Alan, please get the shell access when you can even if you need to wait before using it. Meanwhile, if someone else can help with the spamming that too would be good.
Eclecticology
talk
03:49, 5 June 2013 (UTC)
reply
The most important is to stop the spam bot, e.g by blocking its IP address (or the range of its IP adresses)... If you are beaurocrat of the wiki you should have access to special page with this fiture. After that is a good idea to delete all user pages with the spam using a bot (now there are more then 1000 such pages). I can help of cource but without special rights I am not able to do much.
Electron

09:11, 5 June 2013 (UTC)
reply
The spam has been coming from multiple IP addresses in multiple ranges. I have been using range blocks without much effect.
Eclecticology
talk
06:17, 7 June 2013 (UTC)
reply
Maybe a good idea is to block as wide IP ranges as possible temporally (eg. for a week or two) - it will stop to create new user accounts and won't stop the present users to edit. Site will be visible for everyone but no one can create new accoun't. The spam bot creates about 100 new user account per day and this can be a problem in the future. So...
Electron

07:42, 7 June 2013 (UTC)
reply
Tech news: 2013-23
edit
Latest
tech news
from the Wikimedia technical community.
Please inform other users about these changes.
Recent software changes
(Not all changes will affect you.)
The latest version of MediaWiki (
1.22/wmf5
) was added to non-Wikipedia wikis on May 29. It
will be enabled
on the English Wikipedia on June 3, and on all other Wikipedias on June 5.
[30]
The Tamil Wikipedia shared a
Lua module
they created to automate their Main Page.
[31]
There is now a
test wiki
to test new features in right-to-left languages.
[32]
The
Thanks
feature was added to the English Wikipedia; users can now thank others for individual edits.
[33]
The
new interface
for account creation and log-in is now the default on 30 wikis, including the English Wikipedia, Commons, Meta, and Wikidata. The feature will be added to all wikis
after June 5
. Users can return to the old look by
adding ?useNew=0
to the web address.
[34]
Videos are now
played in pop-up windows
if their size on the page is smaller than 200 pixels (800 pixels on the English Wikipedia).
[35]
Opening your talk page now marks notifications as read, for wikis using the
Notifications
feature. (
bug 47912
[36]
All autoconfirmed users can now reset
transcoding
of video files; previously only administrators could do this.
[37]
The
Nearby
feature allows people who use mobile devices to see Wikipedia articles about objects and places around them.
[38]
Future software changes
The
PostEdit
feature is now part of MediaWiki, and will work on all wikis. (
bug 48726
[39]
The
Narayam
and
WebFonts
extensions will be
replaced
by the
Universal Language Selector
extension.
[40]
MediaWiki will now be updated
every week
, starting on June 6. Thanks to this, bugs will be fixed and features will be added faster than they are now.
[41]
Tech news
prepared by
tech ambassadors
and posted by
Global message delivery
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
Trademark discussion
edit
Hi, apologies for posting this in English, but I wanted to alert your community to a discussion on Meta about potential changes to the Wikimedia Trademark Policy. Please translate this statement if you can. We hope that you will all participate in the discussion; we also welcome translations of the legal team’s statement into as many languages as possible and encourage you to voice your thoughts there. Please see the
Trademark practices discussion (on Meta-Wiki)
for more information. Thank you! --
Mdennis (WMF)
talk
Uploading here test scripts: request for comments
edit
While waiting for a formal purpouse and a detailed project, I'd like to begin to post here some templates, js scripts and Lua modules, and one or two Italian or - better - multilengual books to test tools. I usually work into it.source only (dealing with scripts) and I'd like to test them into a different environment, to generalize them and to discuss them into a different community. If you agree with my project, what can be the best strategy to avoid confusion and any drawback to this community? --
Alex brollo
talk
12:40, 4 June 2013 (UTC)
reply
I think that we could use a page like
Wikisource:Lua modules
as a collector, and put all the scripts in Module: namespace. To avoid conflict, every module could have the name in the language from the wiki it comes from, so to have also a direct source. For example, you could copy
it:Modulo:Dati
in
Module:Dati
. What do you think? --
Aubrey
talk
20:23, 6 June 2013 (UTC)
reply
Really I was thinking about a unique prefix so that candidate file for sharing (js, templates, modules) would be clearly identified/retrieved by a bot to be copied (or called when js) into other projects. Convention should be, to edit then
here only
(t.i.
never edit their copies into other projects
). A prefix could be character "!": i.e., a work copy of it.source Template:Pg and Modulo:Pg could be uploaded here as Template:!pg and Module:!pg. A global bot could update local copies into willing projects easily. Doc of local copies of pages could mention the convention "edit into oldwikisorce, since your edits of this will not been saved". IMHO it could run. --
Alex brollo
talk
22:00, 6 June 2013 (UTC)
reply
Please move to
Talk:Wikisource vision development
if interested; I posted same thoughts there. --
Alex brollo
talk
04:51, 10 June 2013 (UTC)
reply
Tech news: 2013-24
edit
Latest
tech news
from the Wikimedia technical community.
Please inform other users about these changes.
Recent software changes
(Not all changes will affect you.)
The latest version of MediaWiki (
1.22/wmf6
) was added to test wikis and MediaWiki.org on June 6, and to non-Wikipedia wikis on June 10. It
will be enabled
on all Wikipedias on June 13.
[42]
An alpha version of the
VisualEditor
was enabled on all Wikipedias on June 6. Please
test it and report problems
[43]
Several VisualEditor bugs
have been fixed
; users can now add, edit and remove categories using the editor's "Page settings" menu.
Wikimedia error messages will no longer link to the #wikipedia
IRC channel
on
Freenode
[44]
The logo of 16 Wikipedias was changed to
version 2.0
in a fourth group of updates.
[45]
A test instance of Wikidata is now available at
test.wikidata.org
[46]
Users can now patrol the first version of a newly created page if they visit it from
Special:NewPages
or
Special:RecentChanges
[47]
Translation pages will no longer include edit section links (
bug #40713
).
[48]
Future software changes
A report on mobile upload errors
was published
, and software changes to reduce their number will come soon.
[49]
A request for comments on
updating MediaWiki
to use
RDFa
version 1.1 was started on MediaWiki.org (Gerrit change
#67608
).
Tech news
prepared by
tech ambassadors
and posted by
Global message delivery
Contribute
Translate
Get help
Give feedback
Unsubscribe
20:15, 11 June 2013 (UTC)
Tech News: 2013-25
edit
Latest
tech news
from the Wikimedia technical community. Please inform other users about these changes.
Translations
are available.
Recent software changes
(Not all changes will affect you.)
The latest version of MediaWiki (
1.22wmf7
) was added to test wikis and MediaWiki.org on June 13. It
will be enabled
on non–Wikipedia sites on June 17, and on all Wikipedias on June 20.
[50]
The
Narayam
and
WebFonts
extensions were successfully
replaced
by
Universal Language Selector
on June 11.
[51]
VisualEditor
news:
VisualEditor was temporarily disabled on Wikipedia sites on June 14 due to
an issue
that inserted a lot of HTML code. The issue is now fixed and VisualEditor works as before.
Users can now use VisualEditor to add images and other media items from their local wikis and Wikimedia Commons.
[52]
VisualEditor also allows editing references.
[53]
The new
Disambiguator
extension, which was previously part of MediaWiki itself, was enabled on test wikis. It adds the magic word
__DISAMBIG__
to mark disambiguation pages.
[54]
The newly enabled
Campaigns
extension allows Wikimedia Foundation data analysts to track account creations that result from a specific outreach campaign.
Future software changes
Universal Language Selector
will be added
to the Catalan (ca), Cebuano (ceb), Persian (fa), Finnish (fi), Norwegian Bokmål (no), Portuguese (pt), Ukrainian (uk), Vietnamese (vi), Waray-Waray (war) and Chinese (zh) Wikipedias on June 18.
[55]
Starting on June 18, VisualEditor will be randomly enabled by default for half of newly created accounts on the English Wikipedia to test stability, performance and features.
[56]
Two new webfonts (UnifrakturMaguntia and Linux Libertine) will be added to wikis that use Universal Language Selector.
[57]
[58]
It will now be possible to hide the sidebar while using the
Translate
extension to reduce distractions (
bug #45836
).
[59]
A patrolling link will now be visible for un-patrolled pages, even if users don't visit it from
Special:NewPages
or
Special:RecentChanges
bug #49123
).
[60]
A request for comments on
enabling a new search engine for MediaWiki
was started.
Tech news
prepared by
tech ambassadors
and posted by
Global message delivery
Contribute
Translate
Get help
Give feedback
Unsubscribe
EdwardsBot
talk
22:39, 16 June 2013 (UTC)
reply
Uniforming "poem" syntax
edit
When taking some text from many different language versions of Wikisource, I find myself stuck with as many different writing formats:
fi:Ensimmäinen laulu »Jumalaisesta näytelmästä»
uses ": " as line delimiter;
it:Divina Commedia/Inferno/Canto I
uses standard

tags, but "pollutes" the text with many {{
}} templates, which could be replaced with a proper command to "

";
en:The Divine Comedy/Inferno/Canto I
is quite clean, but includes images within the

tag.
They all should use a standard format, line-marking templates could be avoided, and indentation could be controlled via "

".
Any thoughts on this? --
Ricordi
samoa
04:28, 20 June 2013 (UTC)
reply
Very interesting talk. But....
They all should use a standard format
: why? To make user editing simpler? To produce a cleaner wiki code for bots, or other uses? To produce a cleaner, standardized html to be used in html/xhtml/xml exports? --
Alex brollo
talk
05:59, 20 June 2013 (UTC)
reply
For all those purposes: see
dvncmd.tk
for an example; I don't know exactly which is the best format ever, but we should at least be consistent within all language versions, to ease cross-wikiness (and save storage, too). --
Ricordi
samoa
06:04, 20 June 2013 (UTC)
reply
Can we list here a set of requisites of an "ideal" poem tag?
Here some requisite I'd like:
simple but "elastic" wiki code (covering indentation of verses, spacing between strophes, broken verses very common in theater texts
clean, well-structured html easy to parse
verse numbering with anchors to all verses to make verse-specific linking easy
easy selective transclusion of sets of verses
.....
IMHO, Scribuntu/Lua should be explored to get all these results, keeping in mind the features of VisualEditor. No present solution respects "ideal requisites". --
Alex brollo
talk
07:50, 20 June 2013 (UTC)
reply
File:Wikisource.png
edit
Shouldn't it be deleted in favor of
commons:File:Wikisource.png
? They are perfectly equal, bit-by-bit. --
Ricordi
samoa
15:10, 20 June 2013 (UTC)
reply
GU Wikisource
edit
Gujarati language domain of wikisource came in to existence on 27th March 2012. Why it is still listed at
Wikisource:Languages
? Also there are many Gujarati pages exist here. All of them are already transferred to Gujarati domain then why duplication? Thank you.--
Vyom25
talk
18:16, 21 June 2013 (UTC)
reply
X!'s Edit Counter
edit
(Sorry for writing in English. You can
translate the proposal
.)
Should
X!'s edit counter
retain the opt-in requirement? Your input is strongly encouraged.
Voice your input here
.——
cyberpower
Chat
Automation
05:09, 23 June 2013 (UTC)
Distributed via
Global message delivery
. (Wrong page?
Fix here
.)
Tech news: 2013-26
edit
Latest
tech news
from the Wikimedia technical community. Please inform other users about these changes.
Translations
are available.
Recent software changes
(Not all changes will affect you.)
The latest version of MediaWiki (
1.22wmf8
) was added to test wikis and MediaWiki.org on June 20. It
will be enabled
on non–Wikipedia sites on June 24, and on all Wikipedias on June 27.
[61]
Universal Language Selector
was successfully enabled
on the Catalan (ca), Cebuano (ceb), Persian (fa), Finnish (fi), Norwegian Bokmål (no), Portuguese (pt), Ukrainian (uk), Vietnamese (vi), Waray-Waray (war) and Chinese (zh) Wikipedias.
[62]
The
new interface
for account creation and log–in is now the default on all Wikimedia wikis. The
old
look is no longer available (
bug #46333
).
[63]
The
TimedMediaHandler
extension now supports native
FLAC
files.
A discussion
to allow this file type is taking place on Commons (
bug #49505
).
[64]
After a test period, the
Disambiguator
extension was enabled on the English Wikipedia on June 18.
[65]
VisualEditor
news:
A VisualEditor bug temporarily made all new accounts unusable. The issue is now fixed and account creation works as before (
bug #49727
).
A high importance
file insertion bug
has been fixed, but the feature
does not
work perfectly yet.
[66]
It is now possible
to synchronise
local CSS and JavaScript files with the
beta cluster
. This should make it easier to test software features before they are enabled on live wikis.
[67]
Future software changes
The default link to a help page on editing, visible below the editing window,
will change
on almost 600 Wikimedia wikis and will now link to
MediaWiki.org
bug #45977
).
[68]
Universal Language Selector will be enabled on wikis without language versions (such as
Wikisource
and
Wikispecies
) on June 25.
[69]
The
AbuseFilter
extension will allow filtering links and HTML code for page creations.
[70]
The
related changes
special page will now include upload log entries.
[71]
It will soon be possible to choose the language of
SVG files
that contain translations.
[72]
MediaWiki will now allow converting audio files from one format to another.
[73]
The Wikidata technical team has
started a discussion
about how Wikidata can support Wiktionary.
[74]
The search feature on Wikimedia sites is planned to be modified to use
Solr
on all wikis by the end of 2013.
[75]
Tech news
prepared by
tech ambassadors
and posted by
Global message delivery
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
18:18, 23 June 2013 (UTC)
Proposal to move Oldwikisource to the incubator
edit
I've seen that there is
a proposal to move the Oldwikisource projects to the Incubator
.--
Micru
talk
14:49, 24 June 2013 (UTC)
reply
As far as I can see this proposal comes from people who don't have any contributions in the Wikisource's realisations.--
Zyephyrus
talk
15:16, 24 June 2013 (UTC)
reply
Book management request for comment
edit
I've created a
Request for Comment
on my planned extension for my Google Summer of Code project (
"Improve support for book structures"
). Any feedback on this would be much appreciated!
GorillaWarfare
(talk)
19:33, 24 June 2013 (UTC)
reply
Tech news: 2013-27
edit
Latest
tech news
from the Wikimedia technical community. Please inform other users about these changes.
Translations
are available.
Recent software changes
(Not all changes will affect you.)
The latest version of MediaWiki (
1.22/wmf9
) was added to test wikis on June 27. It
will be enabled
on non–Wikipedia sites on July 8, and on all Wikipedias on July 11.
On Wikisource, the canonical names of the "Index" and "Page" namespaces in the
Proofread Page
extension are no longer localized (
bug #47596
). Please check scripts that depend on
$wgCanonicalNamespace
[76]
A JavaScript problem caused the "View history" and "Add topic" tabs in the Vector skin to be moved into the drop-down menu on right-to-left wikis. The issue is now fixed and links are visible as before (
bug #50196
).
[77]
There was a short
site outage
on June 28.
The automated
Category:Pages with broken file links
now includes broken file links inserted inside the

tag (
bug #50119
).
[78]
The
Nearby
feature is now enabled on Commons and shows images in a user's area.
[79]
There is now a special page listing disambiguation pages for wikis that use the
Disambiguator
extension (
bug #44040
).
[80]
The old version of the
Article feedback
tool (version 4) was removed from wikis that still used it.
[81]
VisualEditor
news:
Many bugs that caused text to be removed or damaged have been fixed, including one related to copy-paste (
bug #49816
).
VisualEditor now offers a visual interface to
edit references
In preparation for enabling the VisualEditor on a wider scale, new documentation has been created, including a list of
frequently-asked questions
and a
user guide
with many images. Please
help with translations
Several problems related to overlapping of elements with the VisualEditor toolbar have been fixed (
bug #50096
#50159
#50324
).
TemplateData
information is now displayed for templates that are added to a page (
bug #49778
).
Section edit links now show links to both VisualEditor and the
old
source
) editor (
bug #49666
).
Images are now loaded securely when using
HTTPS
bug #43015
).
[82]
Future software changes
VisualEditor will be enabled for all logged-in English Wikipedia users on July 1, and for all users on July 8.
From July 8, it will be possible to upload
WAV
and native
FLAC
files to Commons, and use them directly on wiki pages (
bug #49505
).
[83]
The
Universal Language Selector
will be added to the English Wikipedia on July 2, and to remaining wikis on July 9.
[84]
Erratum
Tech news #26
incorrectly reported that audio transcoding was added to
TimedMediaHandler
; it was actually statistics about audio transcoding that were added.
[85]
Tech news
prepared by
tech ambassadors
and posted by
Global message delivery
Contribute
Translate
Get help
Give feedback
Subscribe or unsubscribe
14:33, 1 July 2013 (UTC)
Universal Language Selector will be enabled on 2013-07-09
edit
On July 9, 2013,
Universal Language Selector
(ULS) will be enabled on this wiki. The ULS provides a flexible way to configure and deliver language settings like interface language, fonts, and input methods (keyboard mappings). Making it available here is the last phase of making ULS available on all Wikimedia wikis.
Please read the announcement on
Meta-Wiki
for more information.
Siebrand
13:04, 4 July 2013 (UTC)
(via
Global message delivery
).
reply
Support
, very useful. --
Ricordi
samoa
06:33, 5 July 2013 (UTC)
reply
Multilanguage works
edit
I just sent this message to wikisource-l:
There's a reasonable need to get a shared, standard set of templates, modules, js scripts for wikisource projects - all projects sharing a common, identical goal and facing with the same, identical issues, and needing the same set of international, standard metadata. Nevertheless it's very difficult to synchronize efforts, while working into different "boiling" projects; and I personally found very frustrating to admit that some painful efforts to solve specific issues turned out to be simply a "rediscovering the wheel". :-(
Oldwikisource, given its "neutral" character, could be IMHO the perfect project to share the best of source projects, and there's a perfect kind of works that could uploaded into oldwikisource and proofreaded using common, shared styles & tools: they are multilanguage works.
Presently, we are going to upload and proofread a three-language (French, German, Italian and some English too) magazine: Histoire des Alpes - Storia delle Alpi - Geschichte der Alpen. It's released under CC-BY-SA-2.0 licence, My idea is, to upload it into oldwikisource, transcluding it by Iwpage into any interested projecy - the proofreading/formatting job being done into oldwikisource, with common tools, common templates, common modules, common "styles". What do you think about?
And you "oldwikisourcians" ... what do you think about? --
Alex brollo
talk
17:47, 5 July 2013 (UTC)
reply
I'm nearly sure we have discussed multilanguage works here some years ago... but I
cannot find
it.
-jkb-
talk
19:18, 5 July 2013 (UTC)
reply
I got an encouraging reply into wikisource-l; if there aren't strong objections, I'm going to try in a few days after some more discussion.... just to see what will happen. Obviously I'll use this opportunity to load here the best of it.source templates and scripts; any of you is strongly encouraged to fix them or replace them with something better, this is the real goal of my test: to discussi, find and share here best solutions for common issues. :-) --
Alex brollo
talk
23:18, 6 July 2013 (UTC)
reply
Common templates are a very good idea, but how are you going to make them work? Currently, there is a lot of (nearly) identical templates here on the oldwikisource copied from different language versions. E.g. for
extra letter-spacing
there are at least {{
LetterSpacing
}} from en-wiki (used in Irish Gaelic texts), {{
Sparrt
}} from nl-wiki (used in Afrikaans texts), {{
SperrSchrift
}} from de-wiki (used in some German texts, I also started to use it for Volapük recently), {{
Razr
}} from ru-wiki (used in Tatar texts), and {{
Rozpinane
}} also from de-wiki, but renamed (used in Upper Sorbian texts). Ideally, they all should just link to the same template, but they don't. Nobody looks after templates in any centralized manner here. Users of German dialects tend to copy templates from de-wiki, users of languages from ex-USSR – from ru-wiki, and so on. --
Shruggy
talk
10:22, 26 August 2013 (UTC)
reply
You are right, but imagine what will happen if multilanguage works (writtein in major languages) would be not only allowed, but encouraged here, best template imported from major projects, then classified for action, discussed, compared and tested. I see that statement that forbids to load here books written in major languages (but some rare exceptions) as the main problem to remove. And another old issue is problems to build an interproject link pointing to oldwikisource - I see bugs open about this problem but I don't understand if the bug has been solved. --
Alex brollo
talk
07:40, 2 September 2013 (UTC)
reply
Tech news: 2013-28
edit
Latest
tech news
from the Wikimedia technical community. Please inform other users about these changes.
Translations
are available.
Recent software changes
(Not all changes will affect you.)
VisualEditor
news:
VisualEditor deployment
has been delayed
by a week. It is now planned to enable the editor for logged–in editors on chosen Wikipedias on July 22, and on all Wikipedias on July 29.
A bug
that made it impossible to save VisualEditor edits that triggered a CAPTCHA has been fixed.
[86]
Several bugs that occurred on right–to–left wikis have been fixed last week (
bug #49416
bug #49613
bug #50543
).
Uploading files has been restricted on Meta Wiki to administrators and the newly created
uploader
group. An
exemption doctrine policy
is being developed (
bug #50287
).
[87]
Emergency priority
CentralNotice
banners will always be shown unless users have hidden them, ignoring cookies set for lower priority banners.
[88]
Future software changes
MediaWiki will allow choosing a specific page of a PDF document or a thumbnail of a video file to show up inside the
tag (
bug #8480
).
[89]
It will now be possible to create empty
MediaWiki:
messages, for instance in order to disable them (
bug #50124
).
[90]
The Nearby feature will soon be enabled on Wikivoyage wikis again.
[91]
The
Notifications
extension messages will now include a direct link to diffs on wiki as well as in notification e-mails (
bug #48183
).
[92]
Table of contents will now use the HTML