Wikisource talk:ProofreadPage - Wikisource

Wikisource talk:ProofreadPage - Wikisource
Jump to content
From Wikisource
Latest comment:
3 years ago
by Pspviwki in topic
Transcluded page not showing as expected
Features requests
edit
Q : Do we want another pagequality level for pages that are incomplete
edit
incomplete = text not completely transcribed
I think it would be useful. --
Zyephyrus
14:42, 10 May 2009 (UTC)
Reply
Incomplete or incompletely proofed? Or either/both? In any case, I'd use it. --
Spangineer
23:22, 12 May 2009 (UTC)
Reply
It might mean both, either one or the other: it would mean that the page requires an action from the user whatever the action. --
Zyephyrus
06:03, 13 May 2009 (UTC)
Reply
Incomplete
means that the text is only partially transcribed. It seems to me that something such as
incompletely proofed
would do more harm than good, because it is useless for other users to know that you have incompletely proofed a page, if they do not know which part it is.
ThomasV
08:33, 13 May 2009 (UTC)
Reply
Ok. In the long run, a part of the page might be colored as
not proofread
and another part as
proofread
, so the page would be incomplete too; but I understand that it is not a feature for now. Sorry if I have distorted what you meant. --
Zyephyrus
09:16, 13 May 2009 (UTC)
Reply
I want this feature and think it would provide a great deal of guidance for new transcribers as to where they can quickly begin improving a page.
Aharonium
talk
21:20, 16 June 2014 (UTC)
Reply
"Without text"
edit
I've been playing around with bulk validation of blank pages these last few days. The idea is that you don't need to read a blank page to validate it; in most cases it suffices to glance at a small thumb of the page image to determine that, yes, it really is blank. So I wrote a script to make me a gallery of images of unvalidated allegedly blank pages.
One thing I have learned from this is that there are
a lot
of allegedly blank pages that are in fact not blank. The most common cause is pages with a picture but no text—since there is no text to extract from the djvu, the djvutext.py bots mark those pages as blank. It is also not uncommon for our bots to mark text pages as blank, because the OCR failed for that page. And I found one case where every page of an entire book is tagged as blank, because a bot tried to upload OCR text from a djvu that had no text layer.
My conclusion is that allegedly blank pages do need to go through a validation process just like every other page. It worries me a little that the new proofreading system shunts blank pages off into a separate class, making it impossible to distinguish between allegedly blank pages and definitely blank pages. Could we think a little more about this change before we go live with it?
Hesperian
01:31, 28 May 2009 (UTC)
Reply
Robots are not supposed to modify the status of a page.
the 'without text' status will have to be set manually, and the corresponding button will be accessible from any other state.
if robots becomes a problem, I might block robot edits that attempt to modify page status.
ThomasV
23:05, 29 May 2009 (UTC)
Reply
I think you are saying that "Without text" will like "Validated as blank". That is okay.
Hesperian
03:55, 3 June 2009 (UTC)
Reply
Sorting out pages that I can validate per project
edit
I have been working on the enWS
project of the month
doing lots of the first proof, and some of the validation. From the proofread status
en:s:Index:Omnibuses and Cabs.djvu
, I am finding it hard to determine which I can validate, and which I proofread. It would be nice to have a means where I could highlight those that I can go and validate. At the moment, the only way that I can determine is to enter the Page: namespace and see whether the option to validate exists.
Even to expand that thought a little. It would be nice to have a means to monitor work on a Index: namespace project. To be able to see what is happening to subpages of a project, to be able to see at a glance how many pages are validated for a work, how many need to be done, etc. This would give us a reasonable means to have a completion schedule. I have some good underlying thoughts on what would be useful, but am unsure of what is technically feasible, and especially easily and quickly feasible. Thx.
--
Billinghurst
00:39, 18 June 2009 (UTC)
(PS. ThomasV. Your extension is bloody marvellous!)
Reply
these are interesting ideas.
I agree, it would be very useful to visualize which pages were proofed by oneself. This is not possible currently, because the identity of the proofreader is not stored in the database, but only in the text of the pages. In the future I plan to have this stored in the database, and what you describe will be possible. This modification, however, will require a schema change (a modification of the database), and it is not likely to happen soon. In the meantime, I can only suggest to proceed in reading order, in order to remember which pages you proofed :-) [ThomasV, 05:37, 18 June 2009 (UTC)]
Boo, you are no fun whatsoever! Order smorder :-P [Billinghurst 11:58, 18 June 2009 (UTC)]
concerning your second suggestion, Zephyrus added a 'rc' link to some indexes, where you can visualize the modifications of the pages. However, it requires a complicated template, that has to be built manually. I was also planning to create a 'special' page, where index pages are listed with detailed page counts. This too will require a schema change, though.
ThomasV
05:37, 18 June 2009 (UTC)
Reply
Even a page where there was a count of the total number of pages in a work, and a summary of their status
Work's name
Total pages
Count of Validated
Count of Proofread
Count of Problematic
Count of Blank
then a list of works (all or some). It wouldn't need to be a dynamic list, it may be something that is updated daily by a cron if there are changes to a total. [Billinghurst 11:58, 18 June 2009 (UTC)]
The rc link is in all the last PotM :
Look here
on the right, higher than the Contents box. Does this answer your needs? --
Zyephyrus
09:37, 18 June 2009 (UTC)
Reply
Better than nothing, and I think that I scrambled through them. --
Billinghurst
11:58, 18 June 2009 (UTC)
Reply
Billinghurst, do you mean a thing like
this one
made by Kipmaster on fr.ws? --
Zyephyrus
12:27, 19 June 2009 (UTC)
Reply
Yes, Zeph. Something along those lines. However, I was thinking automated rather than manual.--
Billinghurst
15:40, 19 June 2009 (UTC)
Reply
assorted wishes
edit
From bawolff:
Off the top of my head - handle namespaces sanely, It should work out of the box (no hidden steps like importing userland js or setting up namespaces), some of the page status stuff should be in either the page_prop table or somewhere else in the db so its queryable, most of the js needs a thourogh review for security
(That's from my vauge memory of looking at the extension once about a year ago, so things could have changed)
Preview in Third Column
edit
To aid with "Show Preview" before saving the page, it would be helpful to editors to see the formatted, unsaved text as a third column near the scanned text. Currently, I see the preview above the ProofreadPage gadget before saving. There are many times when I may miss a format error that is only clear after the save and the formatted version appears next to the scanned image.
Given the number of wide-screen monitors in use, this should be tenable and a nice way to use all of those extra pixels "in the gutter". Add a gadget option to allow seeing the edit pane, scan pane and an new preview pane side-by-side-by-side. The content need only be updated after pressing the "show preview", not in real-time. Is there a way to get the same result with CSS and div tags without needing to change the code of ProofreadPage (if the above is difficult to do inside the code)? -
DutchTreat
talk
12:08, 1 August 2014 (UTC)
Reply
Sorting wheat and chaff
edit
Is there a ready means to find out which pages have been proofread and validated, though not transcluded into the main namespace. Here I am thinking of a means of checking by work that all pages have been transcluded, or at least a means to have a sanity check that pages not transcluded are not by accidental omission.
I would see that this would be looked at in two ways.
From a work's Index page where we are working upon the work, and want to have a check of the transclusion to the main namespace. Especially relevant for those pulling a work together.
From the perspective of random pages that have been proofed or validated and should be transcluded. Often the case that works are seen to be casually checked from Recent Changes, and one can never be certain of the status.I am wondering whether this could be a report via Special:IndexPages or as a subset/drill down from that page. There are a number of ways that I can think of interrogating things when generally having the janitorial hat on one's head.
--
Billinghurst
07:39, 19 October 2009 (UTC)
Reply
there's currently no way to do this on the wiki; you could get this information from the toolserver, though
ThomasV
09:03, 19 October 2009 (UTC)
Reply
Bug reports
edit
HTML comments ruin Index: page layout
edit
In normal wiki code, you can insert HTML comments within a table. On Index: pages, however, such comments ruin the table layout. I guess the problem is being caused by the "!" in "\nText...
. Thank you. --
Crower
13:20, 20 March 2011 (UTC)
Reply
Yes, we have also noticed a similar problem at french wikisource. Using any no-effect string, like the
nop
template from en.ws, or , or a html comment, is a temporary solution. The problem comes from the code mentioned by Crower, it'll have to be fixed.
Zaran
20:01, 26 September 2011 (UTC)
Reply
When I reported this on
bug #26028
(after
this discussion
) it was closed as a duplicate of
bug #12130
. You can
vote for it
if you also find this to be annoying.
Helder
11:03, 27 September 2011 (UTC)
Transclusion of images
edit
Latest comment:
14 years ago
4 comments
3 people in discussion
I have noticed that there is an issue with transclusions that contain images. It seems to me that often, images are included in books, "where they look nice", for example on the middle of a page, with an equal amount of text above and below it, irrelevant of where paragraphs begin and end. So long as the text is presented on printed pages, that is acceptable. However, when we tranclude text, so that what is presented as multiple pages in a book, becomes a single text on screen, a problem occurs. And that problem is that where a picture is inserted (in code), it creates a break, and what seemingly is a new paragraph, sometimes mid-sentence.
Take for example
en:s:CORSETS: An Analysis
. This article has several illustrations. If we look at the picture that is on page 8, you will see that the insertion of the picture has created a line break, so it looks like one paragraph ends with the words "the body against" (and not full stop) and the next paragraph begins "the downward pull" (without capitalisation). These are, however, both part of the same sentence. Is there a way to avoid this problem in a text that has illustrastions? Where there is a new paragraph on the same page as the illustration, the code for that picture could be moved to between the paragraphs. However, on some pages, he image is so large, or the paragraphs so long, that there are no new paraprahs starting on the same page as the image. What to do in these cases?
V85
07:46, 5 September 2011 (UTC)
Reply
[8]
talk about this trouble, see comment 6, the problem come from that image are included in