Hi All,
I have checked for Bengali Images, its works fine with 100% accuracy. Any
how can it be implemented in Proofread extension?
Regards,
Jayanta
---------- Forwarded message ----------
From: Subhashish Panigrahi <subhashish(a)cis-india.org>
Date: Sat, Aug 29, 2015 at 3:22 PM
Subject: [Wikimediaindia-l] Google's Optical Character Recognition software
now works with all South Asian languages
To: wikimediaindia-l(a)lists.wikimedia.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Google's OCR which apparently is most accurate OCR
we have seen so far, works really good for all the major South Asian
scripts:
http://globalvoicesonline.org/2015/08/29/googles-optical-character-recog
nition-software-now-works-with-all-south-asian-languages
Here are test cases of many Indian scripts: https://goo.gl/3X75iR.
Except Gurmukhi most scripts are working really good.
This could be really useful for Indian language Wikimedians and will
come handy for digitization of printed and scanned text. Here is an
animated tutorial for Wikimedians to use this tool for
Wikisource/Wikipedia:
https://commons.wikimedia.org/wiki/File:Tutorial_to_use_Google_Optical_C
haracter_Recognition.gif
Please write to me if anyone wants to localize this tutorial in your
language.
- --
Best!
Subhashish Panigrahi
Programme Officer, Access To Knowledge
Centre for Internet and Society
@subhapa / https://cis-india.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJV4YD0AAoJEHThehXZGxGO9ywP/RcJOXB3tFHJNF03X23x1jkY
vffu+1Iob6kLMZt/JD3nTmpXasXDlme6pbGzaT7/YZsC0VouN+4NE9HoEmZAksJF
3nn7HoEive4mDalXH5qyATOilezqIEYOG2c32LVYHnX6Co+fXPVa5WqsHn5js957
OionIc5t0V9zlGB6e5RLOacPWXsAhXyVunaeY6Ma33cOWHFdVnu1XpUGphJ+miVj
EWszTzjDOPlFiMsSsVonjWHvuz7hYPKXxvVXViXY1QAsoOT7wztvOepzM/hAPmYM
kGiODSaN8fU/e/2l4xdnMRymAt8hsz61hdye2UYx7xRjlda/23BKNZz0hiuWiqgO
FBntHycaHyqR8+fUK5EPE0vnqLp/7XdtRtQkRficuEDYlHz4PlMW8oiVEGhSZOaG
fdpgg02sojU1iMOGOs3h/ODWxkRrE3qpG+eT8n1mWJp6Tq7ZLEaQGxW1P6ytlPFF
qOz8JKl94D/MI7ybAtp+IsuUQk160H9wUPmaLxgemDRom7220xV6BysbmaMEWwww
hgO4fBNG6dPUMp825pTSxx18rY/Kw53sgHmUasixCL6Zv6xnM3rRuTxjZh8j77TR
gq2sKgoU+JkYt9eBpVRjrFO90xS5MxPrvL/lGH6P1smAODPull3o0tR681+NGKRp
C8vU5vJOlmL+HlNXBSh9
=lwbI
-----END PGP SIGNATURE-----
_______________________________________________
Wikimediaindia-l mailing list
Wikimediaindia-l(a)lists.wikimedia.org
To unsubscribe from the list / change mailing preferences visit
https://lists.wikimedia.org/mailman/listinfo/wikimediaindia-l
Dear all,
thanks to Wikimedia Österreich we are organizing the first international
Wikisource Conference, which will be held in Wien, Austria, from November
20 till 22, this year.
We are finalizing the application for a WMF grant, and would like to
receive some feedbacks:
https://meta.wikimedia.org/wiki/Grants:PEG/WCUG/Wikisource_Conference_2015
Hopefully, everything will go for the better and we will receive the money.
>From there, a lot of work have to be done!
Here there is the page for the conference on Meta:
https://meta.wikimedia.org/wiki/Wikisource_Community_User_Group/Wikisource_…
It's up to *you* to come up with a program for the conference :-)
Seriously: it's important that this will be a community event, and
community curated too.
We will have many things to discuss, and we hope it will be great event.
And yes: if everything goes as expected, there will be scholarships, but
it's crucial that we involve our Chapters.
More on this soon.
Spend some time in the weekend to give us some honest feedback!
I hope you are excited about this as we are.
Thanks
Andrea, David, Claudia
Projet Québec/Canada, a french GLAM project presented on the French
Wikisource in collaboration with WMCA and BAnQ (Bibliothèque et Archives
nationales du Québec) bears fruit.
With the enthusiastic collaboration of the Collection nationale (National
Collection), in the last year, over 35 historic documents and books were
rendered in digital format on Wikisource for the public and many more are
on their way to be completed.
Seeing the potential of this great collaboration between contributors and
BAnQ's mission to preserve and desseminate our published heritage, BAnQ
decided to link Wikisource directly from their official website's main page!
This new window on the national archives of Québec website will bring, I'm
sure, great visibility for Wikisource and many interested people who will
want to contribute!
Ernest Boucher, Wikimédia Canada (ca.wikimedia.org)
Wikisource: Projet Québec Canada (jecontribue.ca)
---------- Forwarded message ---------
From: Emmanuel Engelhart <kelson(a)kiwix.org>
Date: Sat, 29 Aug 2015 22:48
Subject: [WikimediaMobile] [RELEASE] Kiwix for iOS v1.0
To: Using Wikimedia projects and MediaWiki offline <
offline-l(a)lists.wikimedia.org>, mobile-l <mobile-l(a)lists.wikimedia.org>,
Mailing list for Wikimedia CH <wikimediach-l(a)lists.wikimedia.org>
Cc: kiwix-testing(a)lists.sourceforge.net <kiwix-testing(a)lists.sourceforge.net>,
kiwix-developer(a)lists.sourceforge.net <kiwix-developer(a)lists.sourceforge.net
>
Hi
This was a long standing feature request and not the easiest one to
implement, that's why the Kiwix development team is pretty proud to
announce the release of Kiwix for iOS v1.0.
With Kiwix for iOS you can easily download/read recent snapshots (with
or without pictures) of all Wikimedia projects with your iPhone/iPad.
This first version of the app provides basic functionalities like:
* ZIM reader
* Navigation through articles
* Search based on article title
* Content library/downloader
* Bookmarks
* Browse history
* iTunes sync (already in beta testing for v1.1)
The app has been developed for the last 18 months by Chris, a New-York
based developer. He was (a bit) mentored by an older member of the Kiwix
dev team and the project was supported by WikimediaCH for the
administrative work with Apple and the coverage of mandatory hardware costs.
With this last stone, Kiwix which is already available for Windows, OSX,
Linux and Android, has reached a milestone. 10 years after the project
creation, Kiwix is a a cutting-edge solution to access Wikipedia (and a
lot more) offline - with most of the computers - whatever the platform.
Download Kiwix for iOS on Itunes:
https://itunes.apple.com/us/app/kiwix/id997079563
Have a look to the source code:
https://github.com/kiwix/iOS
Regards
Emmanuel
--
Kiwix - Wikipedia Offline & more
* Web: http://www.kiwix.org
* Twitter: https://twitter.com/KiwixOffline
* more: http://www.kiwix.org/wiki/Communication
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
> I only know this stat.
> http://wsexport.wmflabs.org/tool/stat.php
I don't know any other tool than grok.se where we need to select the
filenames manually but just FYI, don't forget, if you want accurate stats
for book downloads with the URL you gave, to consult the new wsexport as
well:
http://tools.wmflabs.org/wsexport/tool/stat.php
On the French Wikisource, we already have migrated almost all links to the
new wsexport that allows to make PDFs as well (I'll write Tpt for him to
add the PDF column in the stats on wmflabs...)
Ernest Boucher, Wikimédia Canada (ca.wikimedia.org)
Wikisource: Projet Québec Canada (jecontribue.ca)
Hi,
Are there any option to know the top 25 EPUB downloaded using WSexoport?
I only know this stat.
http://wsexport.wmflabs.org/tool/stat.php
If we knew the most books downloaded, we would decide where we have to do
efforts.
Regards,
Carles
Following work by WMDE at Wikidata, there will now be the ability to
tag/badge works at Wikidata as to their proofread status. The badges have
been kept simple, and should reflect the colour that is used for a work's
page status.
I recommended an implementation of three
* incomplete (be it not be proofread, or problematic)
* proofread once
* proofread twice = validated
This will mean that we should be looking to an agreed approach to its use.
I suggest that this have some onwiki work, with a discussion to follow at
Wikisource Wien Workabout (WWW)
Regards, Billinghurst
The detail ...
Add default badges for Wikisource
With site css, each Wikisource community can override
these defaults.
The defaults are coloured circles. To start with, these match
what we have for Wikibase Repo (e.g. Wikidata), except not (yet?)
have one for 'not proofread'.
* problematic / incomplete
* proofread
* validated
Bug: T97014
Change-Id: I5ad5270866a0a5b8fbc7a19b194f800c2b0e9a8a
---
A resources/images/badge-notproofread.png
A resources/images/badge-notproofread.svg
A resources/images/badge-problematic.png
A resources/images/badge-problematic.svg
A resources/images/badge-proofread.png
A resources/images/badge-proofread.svg
A resources/images/badge-validated.png
A resources/images/badge-validated.svg
M resources/skins/cologneblue/wikimedia-badges.css
M resources/skins/modern/wikimedia-badges.css
M resources/skins/monobook/wikimedia-badges.css
M resources/skins/vector/wikimedia-badges.css
12 files changed, 86 insertions(+), 1 deletion(-)
To view the specific changes, visit https://gerrit.wikimedia.org/r/229199
When editing my common.css to test style of p tag - I need to activate:
.tiInherit p {
text-indent:inherit;
}
I see that my style is uploaded, but is overwritten by another general css.
I suspect that this could come from ResourceLoader and related timing of
css files loading. Am I true? If so, how the issue can be avoided?
Alex
Hum... why should these "button validations" count less, so that four or five of them are needed to change the page status? Certainly not because "the code is not being checked", since the code stays unchecked no matter how many "button validations" are done.
Possibly it would be better if the button(s) opened a flyout telling users what to do: create an account if they do not have one yet, then click edit, [correct what's wrong,] change the page status and save. I think it is better that new users begin to take part in the main editing workflow rather than operating on a separate one that is designed for them.
Whether to make the _next_ page appear after saving is entirely another question, and one to which I would answer "yes". This cannot be done for the very last page of an index, of course.
Erasmo
> Date: Fri, 14 Aug 2015 15:46:31 +0200
> From: Andrea Zanni <zanni.andrea84(a)gmail.com>
> To: "discussion list for Wikisource, the free library"
> <wikisource-l(a)lists.wikimedia.org>
> Subject: Re: [Wikisource-l] Better way to validate pages
> Message-ID:
> <CAC=VxyZZG0vNpOhkqN52bqYS-48U0PVopax9PuPoWpqRd_8-0g(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Fri, Aug 14, 2015 at 2:06 PM, zdzislaw <zdzislaw.wiki(a)gmail.com> wrote:
>
> > In the view mode of the yellow Pages (sic! :-)), we can add the "Thin (but
> > long) Green Button" (TGB) described: "I read and carefully compared the
> > contents with the scan - there's no mistakes." :) Users who "DO read our
> > books" (and they do not want / do not have time / skills... to edit) click
> > on this button and simply go to the view mode of the next page. Such a
> > click would be counted (extra field in the mw database), but did not cause
> > an immediate change of the Page status. If for a given page will be counted
> > three??, four?? such clicks (this amount would have to have the ability to
> > configure for each WS - community could determine their "quality threshold"
> > - for "one click" it will became into BGB), then the Page status would
> > change automatically from "yellow" to "green". Of course, it would be also
> > configurable, to whom show TGB (ip, registered, autopotrolled ...).
> > Such a solution would have be implemented directly in the proofread
> > extension.
> > "TGB" would allow adjustment of the level of "quality" and would be
> > acceptable by most the community. If it is true that " a lot of users DO
> > read our books," even for 5-4 "clicks" the status would change quickly.
> >
> >
> I do like this approach, and I'd love to see some tests.
> I really believe that is good to do tests and experiments, as we are
> sometimes convinced by things that are not really proven.
>
> A 3 step validation passage as you suggest could maybe be easy enough for
> new users and casual readers, and we could gain some validations we could
> not have had otherwise.
>
>
> I also would like to repeat my question about the Visual Editor: are we
> close tho that or nobody is working on it?
>
> Aubrey