Scripto is an alternative to the ProofreadPage extension used
by Wikisource. It is based on Mediawiki but also on OpenLayers,
the software used to zoom and pan in OpenStreetMap.
The only website I have seen that uses Scripto is the U.K.
War Department papers, and in many ways it is more clumsy
than ProofreadPage. But there might be a few ideas that could
be worth picking up. Take a look.
The software is described at http://scripto.org/
As for reference installations, they mention
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
I've made in september changes in the management of page numbers in order to allow the use of not-arabic page numbers. I wasn't sure if this change doesn't make collateral bugs in some other parts of the software. This patch is on Wikisource since a month and I've not any feedbacks of bugs about that. So I think all works correctly.
"Federico Leva (Nemo)" <nemowiki(a)gmail.com> a écrit :
Thomas PT, 08/09/2012 19:21:
> You can now try these changes on labs: http://XX.wikisource.beta.wmflabs.org
> You should try translation of page number, there may be some issues with
> specific languages.
So is everything working correctly?
Wikisource-l mailing list
For people that doesn't know me, I contribute to the French Wikisource and I try to improve the Proofread Page extension.
Here is a description of some modification into Proofread Page that will be deployed sooner, I think next week.
1 I have made a patch in order to add support of not-arabic page number in the "page" namespace for languages that doesn't use arabic numerals: new pages of multi-pages books will now have a name with number in their own language. Existing pages can keep their names with arabic numerals or be renamed by hand or with a bot in order to use not-arabic numbers.
The pagelist tag will links to pages with a localized number but, if the localized page doesn't exist and a page with an arabic number exist, pagelist will link to this page. The pages tag and the navigation inside of the page namespace will use the same system.
So, with this system, nothing, I hope, will be broken in wikis.
2 I have added support of wiki links to proofreadpage_page_status message.
3 I have written a change that create prp-pagequality-[1-4] HTML classes and add them to all links to Page namespace. These classes are done in order to allow people to color all links to page namespace. The old quality[1-4] classes can of course be ever used in order to color these links only inside of Index namespace.
So I hope that these improvments will increase ProofreadPage quality.
Sorry for my poor English,
Two big modifications have been merged into ProofreadPage trunk last week.
They will be deployed next week, Wednesday, October 31 with Mediawiki 1.21-wmf3 and are already live on beta server: http://en.wikisource.beta.wmflabs.org
The first one is the rewriting of the edition form of the index pages in PHP in order to decrease loading time and add new features like an help system. A description have be made in OldWikisource: https://wikisource.org/wiki/Wikisource:ProofreadPage/Improve_index_pages#Im… .
In oder to add these new features (default value, help message...), this rewriting introduce a new configuration message for index pages based on one JSON array located in Mediawiki:Proofreadpage_index_data_config . JSON format have chosen because it's very extensible in order to add easily new features in the future. This message regroup Mediawiki:proofreadpage_index_attributes and Mediawiki:proofreadpage_js_attributes .
The use of this new configuration way is not required in order to have time to improve the configuration system in the future if there are any problem and to allow a smooth migration. Small wikis are invited to keep using the old configuration way.
This format is also described on oldWikisource: https://wikisource.org/wiki/Wikisource:ProofreadPage/Improve_index_pages#Im…
A migration tool have been written in order to migrate easily: https://toolserver.org/~tpt/upgrade/config.php
The second change, more small, change the way of configuration of Index and Page namespaces: the configuration will not be done in Mediawiki:Proofreadpage_namespace and Mediawiki:Proofreadpage_index_namespace but directly in PHP configuration. The support of the new configuration system have already been added to Wikimedia's websites configuration so their might be no problem.
Description of the new configuration system: https://www.mediawiki.org/wiki/Extension:Proofread_Page#Namespaces
If you find bugs please report them in Bugzilla: https://bugzilla.wikimedia.org/enter_bug.cgi?component=ProofreadPage&produc…
Thomas ( User:Tpt )
I wanted to ask you if there is a way to "suggest" User:tpb,
the Internet Archive's bot who crawls in Google Books and upload them in IA,
which books it should import.
And if there is a way to import smoothly from IA to Commons.
I would think a tool like this would be *very*
useful for us in Wikisource, given that:
* we use Djvu from IA most of the time
* it is a good idea to import a book from GB to IA, because sometimes books
in GB disappear.