There are reasons for editing and there are also reasons for not editing.
One big reason *for* editing is if at any time data from new sources are
being imported.
We in Librarianship/Information Sciences makes decisions on how the data
will be available to our users/customers. Eg an author name.
Just found this thread while browsing my email archives (I'm/was inactive
on Wikimedia for at least 2 years)
IMHO will be very helpfull if a central place hosting metadata from
digitized works will be created.
In my past experience, I've found lots of PD-old books from languages like
french, span
Thanks Thomas but I can't write php, just a little of python and
javascript.
But more or less I can read it (if statements are simple) , thanks for link.
Alex
2013/12/6 Thomas Tanon
> The trim final routine is done automatically by the Wikitext content
> representation. So, it have been ve
Hi all,
I am from ml.wikisource.org and I am having a doubt regarding Mediawiki API
and PDF files. I want to know if I can use Pywikipedia to grab the text
layer of a pdf file (in the file namespace, obviously) . Is the mediawiki
API handling any such functionality? Thanks in advance.
Regards,
Bal
The trim final routine is done automatically by the Wikitext content
representation. So, it have been very easy to implement. If you are interested,
here is the internal representation of a Page: page:
https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FProofreadPage.git/8435e3855decbebc8092
>
> Hi!
> No, there isn’t any doc about it. The Proofread Page doc is very messy and
> work on documentation is something really needed (it’s something that any
> advanced editor of Wikisource can do).
> # yes the bottom of nsPage body is trimmed (it’s normal normalisation of
> wikitext content). I
Hi Jayanta,
I would also suggest that you make a list of books you would like to be
uploaded to Commons.
If the PDF is not easily available on the Internet, you can upload it to
Commons, then I will make a DJVU.
BTW, I checked another OCR software (Caminova Document Express 7.5
Enterprise, with As
On Fri, Dec 6, 2013 at 12:27 PM, Thomas Tanon wrote:
> * It isn’t possible anymore to zoom in with a mouse. A fix is on
> test2.wikipedia.org and will be deployed next Tuesday. Sample:
> https://test2.wikipedia.org/w/index.php?title=Page:The_book_of_try_and_learn.djvu/1&action=edit
>
Would it be
Hi everyone!
A new set of corrections have been deployed to Wikisource. Thanks a lot to Phe
and Aarti Dwivedi for their help.
Here is a list of the fixed issues:
* The Page: pages edit summary contained twice the proofreading level change
tag. Now the level change tag isn’t visible during the
Hi!
Thanks a lot for your help proposition.
I'm currently writing unit tests where it’s possible as part of the refactoring
of the ProofreadPage extension that have been begun by a GSoC project last
summer [1]. But as I’ve no special knowledge in this domain I’m not sure do do
it well.
I woul
Hi!
No, there isn’t any doc about it. The Proofread Page doc is very messy and work
on documentation is something really needed (it’s something that any advanced
editor of Wikisource can do).
# yes the bottom of nsPage body is trimmed (it’s normal normalisation of
wikitext content). If it breaks
I'm facing with new setting of nsPage editing; I'd like to study in detail
news about the end of body text and footer. I'ìm a little confused from
some it.source settings and main server/main javascript settings. Are
present end-of-page text conventions/settings documented in detail
somewhere?
#
12 matches
Mail list logo
