There is a lot of potential in Wikisource, but it depends
heavily on the ProofreadPage extension and it has several
bugs that are reported but don't get fixed.
ThomasV is the main developer and perhaps he is the only
maintainer? It would be in the interest of the Wikimedia
Foundation to assign a salaried developer or two into
developing a more robust framework for Wikisource, either
by improving the existing extension or by integrating
some or all of its functionality into MediaWiki proper.
People everywhere have a need to make some PDF (or Djvu)
document available on a website, page by page, with the
ability to add categories and talk pages. This ability
is what the ProofreadPage extension adds to MediaWiki.
In my mind, it is as essential as the support for uploading
JPEG images and automatically generating thumbnails.
Adding multipage documents to a wiki should be a far more
common need than adding mathematical equations.
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
I added to Common.css this code:
div.indent {}
.indent p {
*margin-top*: 0em
*margin-bottom*: 0em
*margin-left*: 2.5em;
*text-indent*: -2.5em;
}
suggested by css trick to manage poem tag.
This code inverts indentation into all <p> inside a div class="indent", very
useful in some special lists of particular pages. All runs very well but...
I can't manage in a simple way the case of a paragraph splitted in two parts
in two pages. I'd like to avoid the possible solution (that is, doubling the
second part of the broken paragraph into the fisrt page inside includeonly
tags, and use noinclude tags for the same text into the following page).
See http://it.wikisource.org/wiki/Pagina:Canti_di_Castelvecchio.djvu/241 di
Castelvecchio.djvu/240 and the following one; the pages are transcluded into
http://it.wikisource.org/wiki/Canti_di_Castelvecchio/Note_alla_seconda_ediz….
--
Alex
Hi everyone,
The next strategic planning office hours are:
Wednesday, 04:00-05:00 UTC, which is:
-Tuesday (8-9pm PST)
-Tuesday (11pm-12am EST)
There has been a lot of tremendous work on the strategy wiki the past
few months, and Task Forces are finishing up their work.
Office hours will be a great opportunity to discuss the work that's
happened as well as the work to come.
As always, you can access the chat by going to
https://webchat.freenode.net and filling in a username and the channel
name (#wikimedia-strategy). You may be prompted to click through a
security warning. It's fine. More details at:
http://strategy.wikimedia.org/wiki/IRC_office_hours
Thanks! Hope to see many of you there.
____________________
Philippe Beaudette
Facilitator, Strategy Project
Wikimedia Foundation
philippe(a)wikimedia.org
mobile: 918 200-WIKI (9454)
Imagine a world in which every human being can freely share in
the sum of all knowledge. Help us make it a reality!
http://wikimediafoundation.org/wiki/Donate
I'm proofreading a book, a biographic dictionary, which lists
information about 7500 people on 810 pages. Each person has
3-4 lines of text.
During proofreading, a page is a page, simple enough,
e.g. http://sv.wikisource.org/wiki/Sida:Östgötars_minne.djvu/207
But how should such a work be transcluded into the main
namespace? Should each entry be its own chapter? It would
be convenient to be able to link directly to each person,
especially since they are numbered and sometimes referred
to by these numbers. But it would make for many tiny chapters
and a table of content that is almost as large as the book.
On the other hand, the printed table of content presents
three main chapters (A, B, C) of which chapter B covers
680 pages. The transclusion code <pages from=75 to=754/>
would generate one very long page.
How has this problem been dealt with before?
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se