Hi all,
After a talk with Brad Jorsch during the Hackathon (thanks again Brad for
your patience), it became clear to me that Lua modules can be localized
either by using system messages or by getting the project language code
(mw.getContentLanguage().getCode()) and then switching the message. This
second option is less integrated with the translation system, but can serve
as intermediate step to get things running.
For Wikisource it would be nice to have a central repository (sitting on
wikisource.org) of localized Lua modules and associated templates. The
documentation could be translated using Extension:Translate. These modules,
templates and associated documentation would be then synchronized with all
the language wikisources that subscribe to an opt-in list. Users would be
then advised to modify the central module, thus all language versions would
benefit of the improvements. This could be the first experiment of having a
centralized repository of modules.
What do you think of this? Would be anyone available to mentor an Outreach
Program for Women project?
Thanks,
David Cuenca --Micru
Hello Everyone,
I am Aarti K. Dwivedi, and have been accepted into the Google Summer
of Code 2013 for the project 'Refactoring of Proofread Page
Extension'. You can find the accepted proposal here
http://www.mediawiki.org/wiki/User:Rtdwivedi#GSoC_2013_Proposal . I am a 2nd
year undergraduate at Indian Institute of Technology Roorkee.
We will be doing some improvements in Proofread Page extension and
will try to integrate it with Visual Editor. If you find any problems with
the extension please file a bug on bugzilla and assign it to me. I am
looking forward to your suggestions and feedback.
Cheers,
Aarti K. Dwivedi
Hi, don't how many of you are interested in this,
but there is some work being done related to the "jailbreaking of the PDF".
The best resource to follow it (IMHO) is
http://blogs.ch.cam.ac.uk/pmr/
This kind of project is more related to Open Access movement than
Wikisource itself, at the present time, but I sense it will be more
imnportant in the future.
After all, Wikisources will have to discuss what they want to do with "born
digital documents", and decide if they want to stick with transcribing old
books or they agree in opening the library to other kinds of documents.
My personal opinion is that the more important (added) values of Wikisource
is integration with other projects and hypertextuality (possibility of
connecting texts to each other, and quotes to the original source, and
cited authors to their books).
So being able to import CC-BY licensed scientific documents is something
worth a study/discussion.
So we maybe want to explore this stuff.
Aubrey
It should be possible, in any language of Wikisource, to
check all existing text against a known dictionary valid
for that year, and to find words that are outside the
dictionary. These words could be proofread in some tool
similar to a CAPTCHA. They might be uncommon place names
that are correctly OCRed but not in the dictionary, or
they could be OCR errors, or both.
Has anybody tried this?
Such finds are not necessarily the only OCR errors.
Some OCR errors result in correctly spelled words, that
are found in the dictionary, e.g. burn -> bum.
So full manual proofreading and validation will still be
needed. But a statistics based approach could fill gaps
and quickly improve full text searchability.
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
Project Runeberg - free Nordic literature - http://runeberg.org/
Hi all,
is there any Wikisource which had Lua deployed?
I'm looking for a book/header templates re-written in Lua to copy and
localize :-)
(so far, I've seen only this one in the Italian Wikipedia
http://it.wikipedia.org/w/index.php?title=Modulo:Tracce&action=edit)
And I'd love to see Book and Creator templates on Commons Lua-style :-)
Aubrey
Dear all,
there is an important Request for Comments on Wikidata.
https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/References_and_…
For those of you who don't know it yet, there is a specific Wikidata Books
task force
http://www.wikidata.org/wiki/Wikidata:Books_task_force
It's really important that the Wikisource community starts engaging
Wikidata issues, especially because it will soon be needed a decision
regarding the relation between Wikidata and Wikisource.
We need to discuss "edition data" on Wikidata, as they represent the 99% of
metadata that are on Wikisource (and obviously Commons).
Aubrey
Yay!!
John Vandenberg.
sent from Galaxy Note
---------- Forwarded message ----------
From: "MZMcBride" <z(a)mzmcbride.com>
Date: Apr 23, 2013 12:28 PM
Subject: [Wikitech-l] Bug 189: "Add a music wikimodule" resolved/fixed
To: "Wikimedia developers" <wikitech-l(a)lists.wikimedia.org>
Cc:
Hi.
https://bugzilla.wikimedia.org/show_bug.cgi?id=189
Congrats to all involved in getting bug 189 resolved! :-)
Bug 189 was one of the oldest unresolved and one of the better known bugs
in Bugzilla involving a request to add a music module to Wikimedia wikis.
Quick stats about the bug:
* Opened: 2004-08-22
* Votes: 48
* Comments: 123
The bug filer is still around and left a nice note on the bug
(<https://bugzilla.wikimedia.org/show_bug.cgi?id=189#c123>):
---
Congratulations to all !
It makes my dream comes true today !
Thanks million times!
---
<https://en.wikipedia.org/wiki/Note> seemed like an easy target for
demoing the newly deployed Score extension
(<https://www.mediawiki.org/wiki/Extension:Score>) on a production site,
if anyone's interested. I tried looking around for a point and click
lilypond or ABC code generation tool (preferably Web-based), but a lot of
these tools quickly went over my head.
MZMcBride
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l