Опитування побажань спільноти (2015)/Вікіджерела

This page is a translated version of the page Community Wishlist Survey 2015/Wikisource and the translation is 100% complete.

Дозволити копіювати сторінки

Як користувач Вікіпідручника, я б хотів бачити поряд з функцією перейменування сторінок функцію «копіювати цю сторінку» (джерело, ціль). Це було б чудово для звичайного користувача, який розширює книгу без втручання в оригінал.

Приклад: Скажімо, Ви хочете вдосконалити книгу про мову програмування «Java». Книга описує версію 6, тоді як Ви хочете почати нову книгу про версію 8. Якщо варто мати обидві книги, то я не бачу способу зберегти оригінальну книгу, і при цьому відредагувати її текст, зберігши його оригінальне авторство.

Приклад: Скажімо, два дописувачі мають різні, однак принципові погляди на майбутнє книги. Це зазвичай призводить до конфліктів, після яких один із користувачів може покинути спільноту. Функція копіювання сторінок могла б стати хорошим технічним рішенням для врегулювання конфлікту. -- Qwertz84 (talk) 23:17, 9 November 2015 (UTC)[]

Голосування

  1.   Oppose per Wikipedia:Content forking. Also looks like a duplicate of 2015 Community Wishlist Survey/Miscellaneous#Support for version branching for pages. MER-C (talk) 10:46, 1 December 2015 (UTC)[]
  2.   Support Would ease the work to be done when we have to work on different editions of a same book. --Ernest-Mtl (talk) 14:53, 1 December 2015 (UTC)[]
  3.   Support, this sounds like a good way to deal with s:Annotations#Clean texts Beleg Tâl (talk) 15:16, 1 December 2015 (UTC)[]
  4.   Support. We sometimes have different versions of the same text on he.wikisource (I assume similar usefulness on other languages as well), and a copy function will definitely be useful in duplicating existing text to edit each page according to specific edition.--Nahum (talk) 19:27, 1 December 2015 (UTC)[]
    Nahum, could you explain an example on he.wikisource? John Vandenberg (talk) 08:34, 2 December 2015 (UTC)[]
    Nahum may have a different example in mind, but an obvious one to me is the text of the Hebrew Bible ("Old Testament"), which is available on HEWS with and without diacritics, and with and without cantillation marks. Ijon (talk) 09:54, 14 December 2015 (UTC)[]
  5.   Support --Usien6 (talk) 21:12, 1 December 2015 (UTC) // For Wikibooks only !![]
  6.   Support--Manlleus (talk) 15:57, 2 December 2015 (UTC)[]
  7.   Support --Le ciel est par dessus le toit (talk) 10:38, 3 December 2015 (UTC)[]
  8.   Support --Kasyap (talk) 15:40, 7 December 2015 (UTC)[]
  9.   Support ----Nrgullapalli (talk) 09:51, 8 December 2015 (UTC)[]

Краща підтримка для файлів djvu

Файли djvu — це досить цікавий відкритий формат для повного оцифрування книг, однак MediaWiki використовує їх лише як «інструменти для рецензування». Навпаки, вони могли б стати цікавим способом виводу праць, що містяться на Вікіджерелах, працюючи над скрупульозним редагуванням текстового шару та повним використанням метаданих твору. Навіть якщо вони використовуються лише як «інструменти рецензування», чимало роботи може бути виконано, застосовуючи деталі мапування текстового шару, оскільки він містить цікаву інформацію про форматування (вирівнювання тексту та відступи, розмір тексту, параграфи, блоки...), яка зараз взагалі ніде не використовується.

Ось список ідей:

  1. переміститися на непрямий режим структури djvu (тим самим уможливлюючи швидший доступ до окремих сторінок за допомогою браузерного розширення для читання djvu-файлів);
  2. додати набір API-запитів, як інтерфейс до всіх завдань DjvuLibre, доступних лише для читання;
  3. додати ще якийсь API для редагування текстового шару через djvuxmlparser;
  4. дозволити незначні зміни файлів djvu (тобто редагування окремих слів у текстовому шарі) без потреби повторно вантажити весь файл djvu (історія текстових редагувань могла б зберігатися за допомогою чогось на кшталт історії перевірок).

--Alex brollo (talk) 14:07, 10 November 2015 (UTC)[]

Голосування

  1.   Support Goldzahn (talk) 12:53, 30 November 2015 (UTC)[]
  2.   Support--Alexmar983 (talk) 16:42, 30 November 2015 (UTC)[]
  3.   Support --YodinT 17:34, 30 November 2015 (UTC)[]
  4.   Support John Vandenberg (talk) 01:29, 1 December 2015 (UTC)[]
  5.   Support Risker (talk) 04:15, 1 December 2015 (UTC)[]
  6.   Support--Kippelboy (talk) 05:41, 1 December 2015 (UTC)[]
  7.    Support--Candalua (talk) 08:57, 1 December 2015 (UTC)[]
  8.   Support --Accurimbono (talk) 09:05, 1 December 2015 (UTC)[]
  9.   Support--Shizhao (talk) 09:27, 1 December 2015 (UTC)[]
  10.    Support --Anika (talk) 09:35, 1 December 2015 (UTC)[]
  11.   Support --Xavier121 (talk) 09:42, 1 December 2015 (UTC)[]
  12.   Support--C.R. (talk) 12:02, 1 December 2015 (UTC)[]
  13.   Support--Jayantanth (talk) 14:33, 1 December 2015 (UTC)[]
  14.   Support--David Saroyan (talk) 14:46, 1 December 2015 (UTC)[]
  15.   Support --Arnd (talk) 15:00, 1 December 2015 (UTC)[]
  16.   Support--KRLS (talk) 15:07, 1 December 2015 (UTC)[]
  17.   Support Anubhab91 (talk) 15:54, 1 December 2015 (UTC)[]
  18.   Support--Arxivist (talk) 20:08, 1 December 2015 (UTC)[]
  19.   SupportGeorge Orwell III (talk) 23:27, 1 December 2015 (UTC)[]
  20.   Support--Yodaspirine (talk) 12:59, 2 December 2015 (UTC)[]
  21.   SupportNickK (talk) 16:04, 2 December 2015 (UTC)[]
  22.   Support --AlessioMela (talk) 20:06, 2 December 2015 (UTC)[]
  23.   Support --Pymouss Tchatcher - 20:13, 4 December 2015 (UTC)[]
  24.   Support - Bcharles (talk) 22:16, 8 December 2015 (UTC)[]
  25.   Support --Davidpar (talk) 14:20, 14 December 2015 (UTC)[]

Впровадити службу оцифрування на кшталт Інтернет-архіву

Як і багато інших користувачів Вікіджерел, я дуже ціную службу оцифрування Інтернет-архіву, і я використовую її настільки широко, як тільки можу (файли djvu є лише одним з багатьох прикладів використання з того багатого набору файлів, які туди можна вантажити: надзвичайно цікавими є колекції зображень jp2 у високій роздільній здатності, а також файлів abbyy xml).

Я б хотів, щоб у MediaWiki впровадили схоже середовище оцифрування, однак зі своїм вікі-підходом, та філософією, орієнтованою на вікіджерела, аби був спільний доступ до найкращих наявних застосунків для опрацювання зображень сторінок книг перед тим як запускати їх на ОРС (оптичне розпізнавання символів), а саме — для розділення їх, обертання, обрізання, розгортання... інакше кажучи, для «сканошиття» сторінок, — це забезпечить збереження зображень сторінок без будь-яких втрат завдяки такій попередній обробці; Після цього має виконуватися найкраща можлива робота з оптичного розпізнавання символів, використовуючи рушій ABBYY OCR чи подібну програму, завдяки чому збережуться як текст, так і детальний xml з ОРС. Далі такі чудові зображення та максимально якісний текст, добутий через ОРС, треба використати для створення бездоганних файлів pdf чи djvu, із можливістю пошуку в них. І врешті — і цей крок має бути справді типовим лише для вікі — вбудований текст має рецензуватися через звичайний процес перевірки, виконуваний користувачами на Вікіджерелах.

Це — зухвала мрія; менш зухвалою ідеєю є отримання повного доступу до найкращих, важких файлів Інтернет-архіву (jp2.zip та abbyy xml) та створення інструментів для якомога повнішого використання цих файлів. --Alex brollo (talk) 07:08, 11 November 2015 (UTC)[]

Голосування

  1.   Support --YodinT 17:35, 30 November 2015 (UTC)[]
  2.   Support--Accurimbono (talk) 09:07, 1 December 2015 (UTC)[]
  3.   Oppose since I believe it is out of scope of the current process, there are solutions for this outside of Wikisource, although I acknowledge this is something useful. Alleycat80 (talk) 09:08, 1 December 2015 (UTC)[]
      Comment A surprising statement. Are you a busy user of wikisource proofreading? --Alex brollo (talk) 17:30, 1 December 2015 (UTC)[]
  4.   Support--Shizhao (talk) 09:28, 1 December 2015 (UTC)[]
  5.   Support --Xavier121 (talk) 09:42, 1 December 2015 (UTC)[]
  6.   Support --Jayantanth (talk) 14:52, 1 December 2015 (UTC)[]
  7.   Support --Natkeeran (talk) 14:54, 1 December 2015 (UTC)[]
  8.   Support--KRLS (talk) 15:07, 1 December 2015 (UTC)[]
  9.   Support --Artem.komisarenko (talk) 19:28, 1 December 2015 (UTC)[]
  10.   Support--Barcelona (talk) 12:08, 2 December 2015 (UTC)[]
  11.   Support--Manlleus (talk) 15:57, 2 December 2015 (UTC)[]
  12.   SupportNickK (talk) 16:03, 2 December 2015 (UTC)[]
  13.   Support --AlessioMela (talk) 20:08, 2 December 2015 (UTC)[]
  14.   Support--Alexmar983 (talk) 23:23, 2 December 2015 (UTC)[]
  15.   Support - Wieralee (talk) 17:13, 4 December 2015 (UTC)[]
  16.   Support Lionel Scheepmans Contact French native speaker, désolé pour ma dysorthographie 23:09, 4 December 2015 (UTC)[]
  17.   Support --Yeza (talk) 10:45, 7 December 2015 (UTC)[]
  18.   Support --Kasyap (talk) 15:40, 7 December 2015 (UTC)[]
  19.   Support --Davidpar (talk) 14:20, 14 December 2015 (UTC)[]
  20.   Support --Rahmanuddin (talk) 15:11, 14 December 2015 (UTC)[]

Інструмент для завантаження файлів із Пенджабської електронної бібліотеки

Пенджабська електронна бібліотека має 1791 манускрипт та 8996 книг на своєму веб-сайті. Всі манускрипти, а також чимало книжок, перебувають у суспільному надбанні. Багато манускриптів та книг написані пенджабською мовою, однак деякі з них написані англійською, перською та мовою хінді. Бібліотека оцифрувала все та завантажила у формі зображень, в яких неможливо проводити пошук за словами. Вони вивантажили зображення на сайт у такій формі, що їх досить складно завантажувати. Я думаю, що варто створити інструмент, здатний завантажити усі манускрипти та книги, що перебувають у суспільному надбанні. Це дозволить розвинути Вікіджерела мовою пенджабі, так само як і контент пенджабської тематики на інших Вікіджерелах. А це, в свою чергу, допоможе вдосконалити й інші проекти. --Satdeep Gill (talk) 07:31, 13 November 2015 (UTC)[]

Голосування

  1.   Oppose One off task that does not result in long-lasting improvement to editor productivity, impact is limited to a small number of wikis. MER-C (talk) 10:03, 30 November 2015 (UTC)[]
  2.   Oppose per MER-C. We have bot tools to do one-off tasks like this. It may not be easy to find someone able and willing to do it. Sounds like a good Hackathon project. John Vandenberg (talk) 01:33, 1 December 2015 (UTC)[]
  3.   Neutral, could be implemented at https://tools.wmflabs.org/bub/index . Jayantanth (talk) 14:45, 1 December 2015 (UTC)[]
    BUB is collapsed since August.--KRLS (talk) 15:07, 1 December 2015 (UTC)[]
      Comment: By the way, BUB SHALL be fixed ASAP. It is a tool very useful for all Wikisources. --Accurimbono (talk) 08:17, 2 December 2015 (UTC)[]
  4.   Comment: this is a perriennial proposal at grants; we need to get a Swartz interested enough to migrate texts to internet archive. good global south project. Slowking4 (talk) 02:41, 3 December 2015 (UTC)[]


Інструмент для використання ОРС від Google на Вікіджерелах індоарійськими мовами

Протягом тривалого часу проекти Вікіджерел індоарійськими мовами були цілковито залежними від «ручного» вичитування користувачами, на що витрачалося не лише багато часу, а й багато енергії. Нещодавно компанія Google випустила програму для оптичного розпізнавання символів (ОРС) для більш ніж 20 індоарійських мов. Ця програма є значно кращою та точнішою за попередні системи ОРС. Однак вона має чимало обмежень. Завантаження одного й того ж великого файлу двічі (один раз — у Google OCR, інший — на Вікісховище) — непросте рішення для більшості дописувачів, оскільки інтернет-з'єднання є дуже повільним в Індії. Тож я пропоную розробити інструмент, який може «надсилати» завантажені файли pdf або djvu із Вікісховища безпосередньо в програму ОРС від Google, завдяки чому можна буде уникнути необхідності завантажувати такі файли двічі. -- Bodhisattwa (talk) 13:50, 10 November 2015 (UTC)[]

Голосування

  1.   Support --Tobias1984 (talk) 11:35, 30 November 2015 (UTC)[]
  2.   Comment This sounds like it relies on an OCR service hosted by Google, similar to Yandex (see SaaSS). Which Google service is this? Has the legality of using the service been checked? John Vandenberg (talk) 01:37, 1 December 2015 (UTC)[]
  3.   Oppose. Yeah, this is SaaSS. Oppose per https://www.gnu.org/philosophy/who-does-that-server-really-serve.html. MER-C (talk) 08:43, 1 December 2015 (UTC)[]
      Comment - There is no such things like free and open source OCR softwares present for Indic languages which is as accurate as Google OCR. There are people, who have tried to build such free OCRs, but no such real luck till now, and we fear, not in near future. Even WMF is not ready to develop free OCRs due to lack of expertise and infrastructure, as stated at the Wikisource Conference 2015 in Vienna recently, even it was acknowledged at the conference that this is one of the highest priority need for Wikisource community. Google OCR is the only successful OCR available for us, so we just cannot ignore it as it is SaaSS. Ravi has explained in detail below. -- Bodhisattwa (talk) 19:54, 1 December 2015 (UTC)[]
  4.   Support --Satdeep Gill (talk) 14:25, 1 December 2015 (UTC)[]
  5.   Support Most needed as of now for Indic Wikisource. We are suffering.Jayantanth (talk) 14:30, 1 December 2015 (UTC)[]
  6.   Support This would come handy for many Wikisourcers. --Subhashish Panigrahi (talk) 14:43, 1 December 2015 (UTC)[]
  7. Conditional support: We need to check with legal first as the OCR service is hosted by a for-profit organisation, if the legal team give the green signal than support otherwise oppose. ~ Nahid Talk 14:44, 1 December 2015 (UTC)[]
      Comment In Commons, there is a Javascript gadget which helps to check whether any uploaded image is present in other website or not using Google Images. The gadget is listed in the preference section of Commons. I dont think, legal team has any problem on that part. The gadget is utilizing the same for-profit organization. Besides, we are talking about semi-automation here, just like the said gadget, nothing more, just trying to make our lives easier. -- Bodhisattwa (talk) 19:25, 1 December 2015 (UTC)[]
  8.   Support, very needed and   Comment for many years, Wikisources are using Tesseract, a free (Apache licenseed) OCR now sponsored by Google, are we talking about Tesseract or a similar software ? Cdlt, VIGNERON * discut. 14:47, 1 December 2015 (UTC)[]
      Comment This is Google OCR in their Google Drive. Not a FOSS software. Can only be used via Google Drive or Services. Not the best situation, but the best practical solution for now. Should be viewed as a transition solution until FOSS OCR solutions become effective. --Natkeeran (talk) 15:00, 1 December 2015 (UTC)[]
    Thank you for this already but could you give more info? For instance: does this software have a name? a license ? what are the « more than 20 Indic languages » ? and did they all have a Wikisource? (no need to answer all my question but I'm curious). Cdlt, VIGNERON * discut. 15:30, 1 December 2015 (UTC)[]
    This is the Google OCR we are talking about. And these are the Wikimedia projects running in 22 Indian languages. As you can see, all of them don't have Wikisource projects, but almost every major old languages is running it and few are also in multilingual Wikisource. But this proposal will not only help Indic language contributors, but also others who face the same problem like us. At the bottom of this link, there is a list of Google OCR supported languages and its plenty. -- Bodhisattwa (talk) 19:31, 1 December 2015 (UTC)[]
    Thank you for explaining this service is part of w:Google Drive. Their terms of service do not allow accessing "using a method other than the interface and the instructions that we provide." There is an official API however it does not allow upload by URL (only direct POST/PUT from the client), so I expect it is against their TOS to integrate Google Drive into any process which automatically transmits a document from Commons to Google Drive, as it is Wikimedia Foundation doing the upload instead of the end user. It may be more legal to upload to Google Drive first, mark it as public and then Wikimedia Commons imports that document with OCR from Google Drive into Commons. John Vandenberg (talk) 07:47, 2 December 2015 (UTC)[]
  9.   Support - This is a common task in many Indian Languages, including Tamil. We are looking for similar tool to upload scanned images via Google OCR into WikiSource. --Natkeeran (talk) 14:55, 1 December 2015 (UTC)[]
  10.   Support --KRLS (talk) 15:07, 1 December 2015 (UTC)[]
  11. Strong support If we can do it , it would be excellent. -- TitoDutta 15:12, 1 December 2015 (UTC)[]
  12.   Neutral Humbly acceptable, but only as a temporary brief solution, while waiting - and actively working - for a free opensource software into an excellent "wikisource OCR service" . --Alex brollo (talk) 17:37, 1 December 2015 (UTC)[]
      Comment I agree that, building an accurate free open-source OCR is the only permanent solution. As discussed at Wikisource Conference 2015 in Vienna recently with WMF staff (community tech+ language engineering), it became clear that WMF is not interested in development of OCR software due to lack of infrastructure and expertise in this field. Besides, other FOSS based available OCRs are far from accurate and practically speaking, they are useless. So, integrating Google OCR is the only practical alternative available to us, which is not only accurate but saves a lot of time and effort. -- Bodhisattwa (talk) 19:25, 1 December 2015 (UTC)[]
    Wikisource Community User Group/Wikisource Conference 2015/Participants doesn't list anyone from mw:Wikimedia Language engineering. Who did you talk with? Nemo 14:28, 3 December 2015 (UTC)[]
    We had long discussion with Frances Hocutt, Software Engineer, WMF about this matter. We also had a Skype session with Amir Aharoni, Software Engineer, Language Engineering team, WMF. Thanks - Bodhisattwa (talk) 14:43, 5 December 2015 (UTC)[]
  13.   Support Anubhab91 (talk) 15:53, 1 December 2015 (UTC)[]
  14.   Support There are Wikimedia projects running in 22 Indian languages. While many of the Wikipedias in these languages have a slow growth owing to our socio economic and political conditions, many Indian languages have a rich sources of books and classics available in public domain dating 1000s of years. Unlike the western world or global north, we do not have Guternberg like projects with an army of volunteers to proofread and transcribe. Hardly 1 in 20 Wikipedians contribute to WikiSource projects and only 1 in a 10 million population become Wikipedians. Stats of the leading Indian language WikiSource projects for Malayalam, Tamil, Telugu and Bengali can be checked. And for the sake of informing the global community better, this is what we mean by Google OCR and here is what we need: Check this example page in Tamil Wikisource where we have proof read extension installed. Now, Google OCR will help us transcribe this page and make our job easy in proof reading. But, we need to upload images page by page to Google OCR. We can't upload more than 10 pages at a time. And then, we are again limited by the storage capacity of one's Google Drive. Our Wikipedian T. Shrinivasan came up with this python script to automate this process. But not everyone are tech savvy enough to run this script. What we need is an OCR solution that is as easy as the proofread extension itself or one that integrates with it. Even 3rd party bookmarklet that interacts with Google should be enough. We have seen enough FOSS based and other industry grade OCR solutions that won't even come near Google OCR's output for the next decade simply because they cannot match Google's resources or approach to solve this issue. It is not a question of whether WMF should do this or if it is within its operating principles of free software. In the past, WMF has redefined global norms if it believes it is in the best interest to serve our mission. This is a matter of immense impact and the question should be how the community can be helped. After all, the output will be available as free content in Wikimedia projects and will also be of great use to add references to Wikipedia. If it is needed, the WMF should talk to Google to get an API or a special agreement that supports WikiSource as even Google only stands to benefit from more content being added to the web. --Ravi (talk) 16:01, 1 December 2015 (UTC)[]
  15.   Oppose - No google in to wikipedia pls Singhalawap (talk) 17:01, 1 December 2015 (UTC)[]
      Comment Can you please elaborate your reason of opposition? As explained above, we are not incorporating Google into Wikipedia!!! For your information, we are using Google OCR practically in all Indic language Wikisource projects everyday. We just want to make the task semi-automated, that's all. -- Bodhisattwa (talk) 18:35, 1 December 2015 (UTC)[]
  16.   Support This will be an investment for the future, especially if it is a free and open source OCR. I see that Tesseract (FOSS OCR software that is developed and sponsored by Google) supports some Indian languages, maybe extend it to WikiSource and improve it? Kenrick95 (talk) 01:48, 2 December 2015 (UTC)[]
  17.   Support --Sayant Mahato (talk) 04:20, 2 December 2015 (UTC)[]
  18.   Support This is very much needed. - Shubha (talk) 04:26, 2 December 2015 (UTC)[]
  19.   Support It's a shame there's no FOSS option, but this sounds like a pretty good way to go for the time being. — Sam Wilson ( TalkContribs ) … 08:53, 2 December 2015 (UTC)[]
  20.   Support But, I also think WMF should try and negotiate a freer fair use agreement with Google (if there are any restrictions). We should also invest in developing an open OCR software for Indian languages after sufficient amounts of training data is available in Wiki projects. -- Sundar (talk) 08:58, 2 December 2015 (UTC)[]
  21.   Support This would not affect non-Indic Wikisources, but it would have an huge impact on Indic ones: I think "language equity" is an important goal for Wikimedia projects, so this is definitely something to do. Aubrey (talk) 09:03, 2 December 2015 (UTC)[]
  22.   Support - I would suggest, if any auto spell-check is available same to be included with option to replace it with suggested words. This would save time of typing the correct word and work of proof reading can get more speed. --Sushant savla (talk) 09:22, 2 December 2015 (UTC)[]
  23.   Support- Reasons are well explained by Ravi (see above)-Nan (talk) 10:38, 2 December 2015 (UTC)[]
  24. Strong   Support --Mathanaharan (talk) 10:41, 2 December 2015 (UTC)[]
  25.   Support-In order to protect the anonymity of contributors, a solution through API aggrement between WMF and Google would be better. --Arjunaraoc (talk) 10:55, 2 December 2015 (UTC)[]
  26.   Support--Balurbala (talk) 12:19, 2 December 2015 (UTC)[]
  27.   Support This would come handy for many Wikisourcers--Kurumban (talk) 13:07, 2 December 2015 (UTC)[]
  28.   Support I am in an openion this will help Tamil (my mother tongue) and other Indic Languages --உமாபதி (talk) 13:20, 2 December 2015 (UTC)[]
  29.   Support --Sivakosaran (talk) 15:14, 2 December 2015 (UTC)[]
  30.   Support--Parvathisri (talk) 17:45, 2 December 2015 (UTC)[]
  31.   Oppose. I do understand frustration of the Indian community that the only good OCR tool is a non-free tool. I am not sure however that we can do anything here unless Google is generous enough to release the source code of their OCR under a free license. In the end this request depends on Google and not on Wikimedia Foundation, as WMF can do nothing without a number of actions by Google, thus it is not a task for Community Tech — NickK (talk) 16:09, 2 December 2015 (UTC)[]
  32.   Support-this is a game changer where wikisource can go where Gutenberg does not. language support in global south. Slowking4 (talk) 02:38, 3 December 2015 (UTC)[]
  33.   Support --Vikassy (talk) 16:51, 3 December 2015 (UTC)[]
  34.   Support -- it will verymuch useful to Indic Languages.--சஞ்சீவி சிவகுமார் (talk) 08:07, 4 December 2015 (UTC)[]
  35.   Support --Pymouss Tchatcher - 20:15, 4 December 2015 (UTC)[]
  36. Strong   Support --ViswaPrabhaവിശ്വപ്രഭtalk 23:51, 4 December 2015 (UTC)[]
  37.   Oppose Google Drive OCR Feature is not even a product with API availability . It is a proprietory product feature within Google drive. I dont know what you mean by Integrating a non existent product to wikisource. The OCR's google open sourced are Tesseract and ocropus . Tesseract is already integrated with Wikisource. I believe the proprietiry feature in Google Drive is more an optimization of these engines. Why dont Wikimedia invest on Community Tech for optimizations and improvments for tesseract and ocropus . The issue with indian languages is absense of financial support for people working on these domains. If wikimedia can address it , we can easily beat it . Integrating non existent proprietory service is always a burden and does not help in solving the OCR problem in long run. -- AniVar (talk) 08:48, 5 December 2015 (UTC)[]
  38.   Support Very Much useful. -தமிழ்க்குரிசில் (talk) 13:06, 5 December 2015 (UTC)[]
  39.   Support -- நி.மாதவன்  ( பேச்சு  )
  40.   Support --Kasyap (talk) 15:39, 7 December 2015 (UTC)[]
  41.   Support This will help decrease many man-hours Yohannvt (talk) 07:23, 8 December 2015 (UTC)[]
  42.   Strong support This is obvious idea that any wiki librarian working on indic language wikisources would get. This will be handy, helpful and boast to indic-wikimedians. So, I support this. --Pavan santhosh.s (talk) 07:59, 8 December 2015 (UTC)[]
  43.   Support -- Mayooranathan (talk) 18:39, 8 December 2015 (UTC)[]
  44.   Support As the Indian language communities have no other good option so it should be implemented. --Jnanaranjan sahu (talk) 18:54, 8 December 2015 (UTC)[]
  45.   Support - If an API solution cannot be negotiated with Google, then something along the lines of user:John_Vandenberg's suggestion under point 8 above. Bcharles (talk) 23:03, 8 December 2015 (UTC)[]


Візуальний редактор, адаптований для Вікіджерел

Tracked in Phabricator:
task T48580

Зараз Вікіджерела використовують старий, але надійний текстовий редактор. Це вимагає від дописувачів Вікіджерел знання багатьох шаблонів, які різняться від однієї мовної версії Вікіджерел до іншої. Якби існувала спеціалізована версія Візуального редактора, адаптована до потреб Вікіджерел, це б посприяло міжмовній взаємодопомозі на Вікіджерелах, і спростило б роботу нових дописувачів у проектах Вікіджерел. Якби в такому адаптованому Візуальному редакторі були відповідні кнопки для введення назв, центрування, розташування тексту з лівого чи правого краю, відстежування ліній тощо, такій редакторській роботі легше було б навчитися, особливо якщо б вигляд такого редактора був похідним від загального вигляду типових текстових редакторів, і це б посприяло залученню нових редакторів до роботи в різних мовних версіях Вікіджерел...

Розміщення заголовка французькою, англійською, іспанською чи хорватською мовами виконувалося б однаковим способом — виділенням тексту та натисканням відповідної кнопки... а не використанням шаблонів з різними назвами, залежно від того, в якій мовній версії Вікіджерел Ви зараз перебуваєте. Чимало людей могли б допомогти з рецензуванням сторінок різними мовами, наприклад, під час глобального тематичного тижня... Я, будучи франкомовним канадцем, — так, я міг би вичитувати тексти французькою, англійською, російською, українською, іспанською мовами, але мені треба було б знати усі такі розмаїті шаблони у всіх цих мовних версіях, і оскільки рівень мого усного мовлення та розуміння цих мов є не таким високим, як у випадку моєї рідної мови, мені іноді буває досить складно знаходити та й узагалі шукати що-небудь в інших проектах Вікіджерел... Однак ніщо не заважає мені надавати свою допомогу в цих проектах, і навіть у відповідних проектах італійською, болгарською чи португальською мовами... Все це — один і той же шрифт... Все, що потрібно від нас для рецензування — це здатність порівнювати оригінальний текст книги із оцифрованим... Але незнання усіх тих шаблонів у різних мовних версіях Вікіджерел не дають мені змоги допомагати іншим спільнотам.

Чарівністю всієї цієї ситуації є те, що нам не треба заново винаходити велосипед! Мені здається, було б легко запустити якусь модифікацію чинного Візуального редактора, який використовується в інших проектах, зосередившись на потребах Вікіджерел у формі стислого списку кнопок для основних цілей, що допоможе вичитати 95%, або й більше наявних сторінок книг... У найгіршому випадку, 5% сторінок, що залишаться, доведеться вичитати старим способом... --Ernest-Mtl (talk) 03:31, 10 November 2015 (UTC) — WMCA[]

Голосування

  1.   Support --Tobias1984 (talk) 11:36, 30 November 2015 (UTC)[]
  2.   Support VE is likely to see a much higher adoption rate on Wikisource than on Wikipedia, and the ability to extract high-fidelity Wikisource content as a DOM using Parsoid will be a very important step forwards. John Vandenberg (talk) 01:42, 1 December 2015 (UTC)[]
  3.   Support Risker (talk) 04:17, 1 December 2015 (UTC)[]
  4.    Support--Kippelboy (talk) 05:41, 1 December 2015 (UTC)[]
  5.    Support --Candalua (talk) 08:57, 1 December 2015 (UTC)[]
  6.   Support --Accurimbono (talk) 09:08, 1 December 2015 (UTC)[]
  7.   Support --Anika (talk) 09:28, 1 December 2015 (UTC)[]
  8.   Support --Rahmanuddin (talk) 15:10, 14 December 2015 (UTC)[]
  9.   Support --Xavier121 (talk) 09:40, 1 December 2015 (UTC)[]
  10.   Support -- Bodhisattwa (talk) 13:27, 1 December 2015 (UTC)[]
  11.   Support --Satdeep Gill (talk) 14:26, 1 December 2015 (UTC)[]
  12.   Support obviously. Cdlt, VIGNERON * discut. 14:35, 1 December 2015 (UTC)[]
  13.   Support --TitoDutta 14:43, 1 December 2015 (UTC)[]
  14.   Support--David Saroyan (talk) 14:46, 1 December 2015 (UTC)[]
  15.   Support --KRLS (talk) 15:07, 1 December 2015 (UTC)[]
  16.   Support -- Wittylama (talk) 15:07, 1 December 2015 (UTC)[]
  17.   Support In order to start to make Wikisource proofreading workflow what it should be: an easy task doable by everyone. Tpt (talk) 15:15, 1 December 2015 (UTC)[]
  18.   Support Beleg Tâl (talk) 15:18, 1 December 2015 (UTC)[]
  19.   Support Sadads (talk) 16:18, 1 December 2015 (UTC)[]
  20.   Support --Wesalius (talk) 19:17, 1 December 2015 (UTC)[]
  21.   Support--Arxivist (talk) 20:10, 1 December 2015 (UTC)[]
  22.   Support -- Daniel Mietchen (talk) 20:46, 1 December 2015 (UTC)[]
  23.   Support  Trizek from FR 22:17, 1 December 2015 (UTC)[]
  24.   Support --Aristoi (talk) 22:55, 1 December 2015 (UTC)[]
  25.   SupportGeorge Orwell III (talk) 23:28, 1 December 2015 (UTC)[]
  26.   Support but please, ensure an immediate switch between VE edit and traditional edit while editing, without the need of saving/re-edit the page. If this feature already exists, I apologyze for this inappropriate comment. If this feature is impossible to get, please allow simple, fast and persistent disabling of VE as an user preference. --Alex brollo (talk) 00:00, 2 December 2015 (UTC)[]
  27.   Support Of course, we are talking about VE in the Proofread page, right? Aubrey (talk) 09:06, 2 December 2015 (UTC)[]
  28.   Support --Barcelona (talk) 12:09, 2 December 2015 (UTC)[]
  29.   Support--Yodaspirine (talk) 13:02, 2 December 2015 (UTC)[]
  30.   Support --Le ciel est par dessus le toit (talk) 13:56, 2 December 2015 (UTC)[]
  31.   Support, one of the few cases where VisualEditor will really make life simpler for experienced users — NickK (talk) 16:05, 2 December 2015 (UTC)[]
  32.   Support Pyb (talk) 01:10, 3 December 2015 (UTC)[]
  33.   Support this is a hard ask, but it is a game changer. even incremental progress would be appreciated. Slowking4 (talk) 02:42, 3 December 2015 (UTC)[]
  34.   Support - Wieralee (talk) 17:14, 4 December 2015 (UTC)[]
  35.   Support --Pymouss Tchatcher - 20:12, 4 December 2015 (UTC)[]
  36.   Support Halibutt (talk) 00:24, 5 December 2015 (UTC)[]
  37.   Support --Yeza (talk) 10:47, 7 December 2015 (UTC)[]
  38.   Support --Kasyap (talk) 15:41, 7 December 2015 (UTC)[]
  39.   Support Abyssal (talk) 16:50, 10 December 2015 (UTC)[]
  40.   Support --ESM (talk) 16:41, 13 December 2015 (UTC)[]
  41.   Support --Davidpar (talk) 14:21, 14 December 2015 (UTC)[]