Repeating something I tried to explain earlier,
we could try to distinguish "markup=layout" from "text".
But it's very difficult, and I stand with Vigneron saying that we should aim to a 99,9% accuracy instead of total perfection, becaus the *cost* of finding that 0,01% is really, really high.

Sometimes we have perfectly readable 75% books, and users can already read them and enjoy them.
Even if a book has a typo every few pages, is still good to read. If it's not "perfectly isomorphic" to the original book (if some linebreaks are different, or symbols, or formatting) it can be still a perfectly readable and functional book.

My point is:
with our tiny communities, we should not reach for the stars, or absolute perfection.
We should aim to serve our users (we are wikilibrarians!) the best as we can, but IMHO this means also trying to harness from our readers and let them collaborate with us, even if it is just correction a typo in one page.
"Given enough eyes, all typos are shallow" should be the Wikisource version of the Linus law [1].
My wish is that we could, as a community, find a way to find those "enough eyes", expand our communities, even if it means just harnessing casual readers.

Aubrey

[1] https://en.wikipedia.org/wiki/Linus%27s_Law



On Tue, Aug 11, 2015 at 2:59 PM, Nicolas VIGNERON <vigneron.nicolas@gmail.com> wrote:


2015-08-11 14:35 GMT+02:00 zdzislaw <zdzislaw.wiki@gmail.com>:
2015-08-11 12:34 GMT+01:00 Nicolas VIGNERON <vigneron.nicolas at gmail.com>:
> 2015-08-11 13:18 GMT+02:00 zdzislaw <zdzislaw.wiki@gmail.com>:
>>  I'll write it again ... that is not safe to validate a page without reviewing its wikicode.
> Are I'm puzzled: why?
> Strange... Are you against VisualEditor too?

For example, when someone validate a page in preview mode it is impossible to check the line breaks, the use of templates...
The single line breaks (text broken into different lines -> common from scanned text) will be seen "normally" on preview mode (parser convers if into #0A), but it shoud be removed, if not... try to "Download (it) as PDF" - all the text will be broken.
VisualEditor - here you can see everything at a glance (!), missed line breaks can be seen as an arrow, if you want to check whether the correct template is used, just simply "move" the mouse on it...
VE <> view mode

Z.

If a template is mispelled or misused, you'll see right away that something is wrong, no ? Where is the need to go to edit mode? (except for <center> vs. <div align="center"> cases but it's not really relevant for validation).

I don't understand your single line breaks problem, and the problem seems to be on PDF generator not on the page itself (it shouldn't block the validation).
"Download (it) as PDF" do you talk about the special page on the right Tools bar or about the wsexport tools? I just tested the two tools and they worked just fine with pages with single line breaks.

You're mixing a little bit « validation » and « perfection ». For example, if a page contains « wo­rd » or « wоrd » instead of « word », it's not perfect but it's valid as it invisible for 90% of readers and tools (plus, there is other tools to detect this specific errors).

Cdlt, ~nicolas

_______________________________________________
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l