On Wed, Jun 12, 2013 at 4:47 PM, Aarti K. Dwivedi ellydwivedi2...@gmail.com
wrote:
If I am not wrong, as of today, most books that were born digital, are
still under copyright. Of course, they are available freely on the
internet. But we can't use the pirated copies. How would we go about the
On Wed, Jun 12, 2013 at 1:32 PM, billinghurst billinghu...@gmail.comwrote:
If you are talking about how we represent digitally prepared text with the
validation process. I would have no issue with the text being ripped and
having a bot run through and taking it straight to level 4 (green), and
On Wed, Jun 12, 2013 at 2:32 PM, Thibaut Horel thibaut.ho...@gmail.comwrote:
3. The current system with 4 quality levels to represent the proofreading
state of a page is not sufficient to represent the diversity of
proofreading scenarios. Indeed, there is a distinction to make between the
I think everything is doable, the problem is how to do it without
cluttering the interface and keeping things simple.
Some levels might be redundant and we could take the chance to think if
they are really necessary.
Some proposed changes:
- Proofread page levels: Unused, Proofread, Proofread
If I am not wrong, as of today, most books that were born digital, are
still under copyright. Of course, they are available freely on the
internet. But we can't use the pirated copies. How would we go about the
procurement of these books?
If we procure these copyrighted books, then the only we
When we tried to convert into wiki code (a needed step to add links and to
convert files into a wiki hypertext) a pdf file, that's a opaque, closed
format, such a work turned off in a nightmare. If we simply load free pdf
books as they are, I don't see any advantage, but feed wikisource
outputs automatically metadata and navigation from the index page
TOC (but it allows also to override data).
Tpt
Date: Tue, 11 Jun 2013 01:33:39 +0200
From: alex.bro...@gmail.com
To: wikisource-l@lists.wikimedia.org
Subject: Re: [Wikisource-l] About texts without supporting files and
Index: pages
: alex.bro...@gmail.com
To: wikisource-l@lists.wikimedia.org
Subject: Re: [Wikisource-l] About texts without supporting files and
Index: pages
I'm going to test what you are telling in a real Lua script; as you know,
Lua can read the code of any page with one expensive server function
only, so
On Tue, Jun 11, 2013 at 8:41 AM, Thomas PT thoma...@hotmail.fr wrote:
Sorry if my answer is off-topic but if metadata are stored in WIkidata, is
it really needed to create index pages to store the same data as Wikidata?
As I see the things, we'll have bibliographical metadata on Wikidata
You're right Aubrey nevertheless while promoving a user friendly interface
the result is that data and wiki code is extremely difficult to use as a
clean data base. Think only to wiki markup and the simple trick to mark
bold and italic text with apostophes very user friendly, but something
On Tue, 11 Jun 2013 12:16:54 +0530, Aarti K. Dwivedi
ellydwivedi2...@gmail.com wrote:
A slighly off-topic question: Even if we modify the extension to
proofread
books which do not have scans( I am assuming books that were born
digital
), against what
will these books be proofread?
I am not
With the deployment of Wikidata it is a good moment to re-examine what
Index pages are and what should be their function.
The most direct transition to a Wikidata-supported Wikisource could be
something like this:
https://sites.google.com/site/dacuetu/BookData.pdf
That would allow:
- to share
@Alex: but what do you think of storing the source information in Index:
pages for all works stored in Wikisource, even if they don't have a
supporting scan?
That was the original question :)
About your proposed library, it would be more useful if it could modify
data in Wikidata, not only
Simply there is no need to store data twice or more, if they are
dinamically imported from wikidata. Such data would be simply generated by
a normal template. Something similar to Commons media sharing: most
wikipedians but beginners know that when you want to edit a shared media
file, you must do
No, it won't be stored in Wikisource, but still there is the need to
present the information in a consistent manner.
If you want to display the information on ns0, you will end up needing the
same fields that the Index: page is using now.
So why not to have the same solution for both?
It could
I'm going to test what you are telling in a real Lua script; as you know,
Lua can read the code of any page with one expensive server function
only, so that a simple {{header|index name}} ns0 template call could read
all the wiki code from index page, parse it, extract all its data content,
and
16 matches
Mail list logo
