Wikimedia Meta-Wiki

Encuesta sobre los deseos de la comunidad 2015/Wikisource

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

Permitir copias de páginas

Como usuario de Wikilibros, me gustaría una función que permita «Copiar esta página» (origen, destino) junto a la opción de trasladar páginas. Sería genial para usuarios normales extendiendo un libro sin tocar el original.

Ejemplo: Digamos que te gustaría mejorar un libro sobre el lenguaje de programación Java. El libro describe la versión 6 y te gustaría iniciar uno nuevo sobre la versión 8. Es relevante tener ambos libros y no veo forma de preservar el libro original y editar el texto con respeto a los editores originales.

Ejemplo: Digamos que dos colaboradores tienen opiniones diferentes pero muy definidas sobre el futuro de un libro. Esto típicamente tiende a crear conflictos, donde alguno de los usuarios abandona la comunidad. La función de copiar la página proporcionaría una buena solución técnica para resolver el conflicto. -- Qwertz84 (talk) 23:17, 9 November 2015 (UTC)[reply]

Earlier discussion and endorsements
@Qwertz84 and Ernest-Mtl: There is an Extension to duplicate pages (with their edit history): mw:Extension:Duplicator. It works fine. -- Reise Reise (talk) 17:21, 14 November 2015 (UTC)[reply]

Votos

  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)[reply]
  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)[reply]
  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)[reply]
  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)[reply]
    Nahum, could you explain an example on he.wikisource? John Vandenberg (talk) 08:34, 2 December 2015 (UTC)[reply]
    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)[reply]
  5.   Support --Usien6 (talk) 21:12, 1 December 2015 (UTC) // For Wikibooks only !![reply]
  6.   Support--Manlleus (talk) 15:57, 2 December 2015 (UTC)[reply]
  7.   Support --Le ciel est par dessus le toit (talk) 10:38, 3 December 2015 (UTC)[reply]
  8.   Support --Kasyap (talk) 15:40, 7 December 2015 (UTC)[reply]
  9.   Support ----Nrgullapalli (talk) 09:51, 8 December 2015 (UTC)[reply]

Mejorar el soporte para archivos djvu

Los archivos djvu son un formato libre interesante para la digitalización de libros completos, pero MediaWiki los usa únicamente como «herramientas para correcciones». Por el contrario, serían un producto interesante del trabajo de Wikisource, trabajando detalladamente en la edición de la capa de texto y usando completamente sus metadatos. Incluso si se usan únicamente como «herramientas para correcciones», se puede hacer mucho trabajo usando los detalles de las asignaciones de la capa de texto, ya que contienen sugerencias interesantes sobre la estructura (alineación del texto y sangrado, tamaño del texto, párrafos, bloques, ...) que actualmente no se están usando.

Esta es una lista de ideas:

  1. Cambiar al modo indirecto de la estructura de djvu (para permitir acceso más rápido a las páginas individuales con una extensión del navegador para leer archivos djvu).
  2. Agregar funciones al API, como una interfaz de solo lectura a las rutinas DjvuLibre.
  3. Agregar también algunas funciones al API para editar la capa de texto usando djvuxmlparser.
  4. Permitir cambios menores a los archivos djvu (por ejemplo algunas palabras en la capa de texto) sin necesidad de subir de nuevo el archivo completo (la historia de las ediciones al texto se podría salvar con algo como la historia de revisiones).

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

Earlier discussion and endorsements
  Endorsed really really useful in wikisource context. --AlessioMela (talk) 14:12, 10 November 2015 (UTC)[reply]

Votos

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

Implementar un sistema de digitalización parecido al del Internet Archive

Al igual que muchos otros editores de Wikisource, aprecio mucho el servicio de digitalización del Internet Archive y lo uso tanto como puedo (los archivos djvu son solo uno de los muchos usos del extenso conjunto de archivos que es posible descargar: colecciones de imágenes en formato jp2 de alta resolución y abbyy xml son muy muy interesantes).

Me gustaría que MediaWiki implementara un ambiente de digitalización similar pero en formato wiki y con una filosofía similar a Wikisource para compartir las mejores herramientas posibles para realizar trabajos pre-OCR en imágenes de páginas de libros (dividir, rotar, recortar, desempacar..., en resumen, ajustar las imágenes digitalizadas), archivando excelentes imágenes sin compresión a partir del trabajo pre-OCR; a partir de eso se podría hacer el mejor trabajo de OCR posible, con ABBYY OCR o algún sistema similar si existe, archivando tanto el texto como el xml de OCR con todos los detalles; entonces las imágenes excelentes y el mejor texto OCR posible se pueden usar para crear excelentes archivos pdf y djvu con capacidad de búsqueda; finalmente (este paso sería realmente wiki) el texto integrado podría ser arreglado con revisiones manuales hechas en Wikisource.

Esto es un sueño audaz; una idea menos audaz es obtener acceso completo a archivos IA (jp2.zip y abbyy xml) y crear herramientas para usarlos tan extensamente como sea posible. --Alex brollo (talk) 07:08, 11 November 2015 (UTC)[reply]

Earlier discussion and endorsements
  Endorsed. Jayantanth (talk) 17:42, 11 November 2015 (UTC)[reply]
  Endorsed --Yann (talk) 14:06, 17 November 2015 (UTC)[reply]

Votos

  1.   Support --YodinT 17:35, 30 November 2015 (UTC)[reply]
  2.   Support--Accurimbono (talk) 09:07, 1 December 2015 (UTC)[reply]
  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)[reply]
      Comment A surprising statement. Are you a busy user of wikisource proofreading? --Alex brollo (talk) 17:30, 1 December 2015 (UTC)[reply]
  4.   Support--Shizhao (talk) 09:28, 1 December 2015 (UTC)[reply]
  5.   Support --Xavier121 (talk) 09:42, 1 December 2015 (UTC)[reply]
  6.   Support --Jayantanth (talk) 14:52, 1 December 2015 (UTC)[reply]
  7.   Support --Natkeeran (talk) 14:54, 1 December 2015 (UTC)[reply]
  8.   Support--KRLS (talk) 15:07, 1 December 2015 (UTC)[reply]
  9.   Support --Artem.komisarenko (talk) 19:28, 1 December 2015 (UTC)[reply]
  10.   Support--Barcelona (talk) 12:08, 2 December 2015 (UTC)[reply]
  11.   Support--Manlleus (talk) 15:57, 2 December 2015 (UTC)[reply]
  12.   Support — NickK (talk) 16:03, 2 December 2015 (UTC)[reply]
  13.   Support --AlessioMela (talk) 20:08, 2 December 2015 (UTC)[reply]
  14.   Support--Alexmar983 (talk) 23:23, 2 December 2015 (UTC)[reply]
  15.   Support - Wieralee (talk) 17:13, 4 December 2015 (UTC)[reply]
  16.   Support Lionel Scheepmans ✉ Contact French native speaker, désolé pour ma dysorthographie 23:09, 4 December 2015 (UTC)[reply]
  17.   Support --Yeza (talk) 10:45, 7 December 2015 (UTC)[reply]
  18.   Support --Kasyap (talk) 15:40, 7 December 2015 (UTC)[reply]
  19.   Support --Davidpar (talk) 14:20, 14 December 2015 (UTC)[reply]
  20.   Support --Rahmanuddin (talk) 15:11, 14 December 2015 (UTC)[reply]

Herramienta para cargar archivos desde la Biblioteca Digital de Panjab

La Biblioteca digital Panjab tiene 1791 manuscritos y 8996 libros en su sitio web. Todos los manuscritos y libros están en lenguaje Punjabi pero algunos están también en inglés, hindú y persa. Ellos han digitalizado todo en forma de imágenes y no es buscable. Han subido imágenes en una forma tal que es muy difícil bajarlas. Creo que deberíamos crear una herramienta que bajara los documentos y libros que son de dominio público. Esto ayudará a desarrollar el Wikisource en Punjabi así como otros contenidos relacionados en Punjabi en otras Wikisources.Esto ayudará a mejorar otros proyectos también. --Satdeep Gill (talk) 07:31, 13 November 2015 (UTC)[reply]

Earlier discussion and endorsements
  Endorsed. We definitely need these sources to be made available in multiple formats and multiple sources as government sites always go missing all of a sudden. An another reason to upload these sources to wikimedia project is to get away from technical difficulties in finding and researching further on the material through collaboration. Omshivaprakash (talk) 10:34, 14 November 2015 (UTC)[reply]
  Endorsed the idea of fixing the BUB or DLI Downloader. --Subhashish Panigrahi (talk) 12:31, 14 November 2015 (UTC)[reply]
  Endorsed--Charan Gill (talk) 15:14, 14 November 2015 (UTC)[reply]
  Endorsed--Hundalsu(talk)
  Endorsed--Dineshkumar Ponnusamy (talk) 08:43, 17 November 2015 (UTC) 08:42, 17 November 2015 (UTC)[reply]

Votos

  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)[reply]
  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)[reply]
  3.   Neutral, could be implemented at https://tools.wmflabs.org/bub/index . Jayantanth (talk) 14:45, 1 December 2015 (UTC)[reply]
    BUB is collapsed since August.--KRLS (talk) 15:07, 1 December 2015 (UTC)[reply]
      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)[reply]
  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)[reply]


Herramienta para usar Google OCR en Wikisource en Indi

Por mucho tiempo los proyectos Wikisource de lenguajes índicos dependían totalmente de corrección manual, lo cual no solo era una pérdida de mucho tiempo, sino también de mucha energía. Recientemente Google liberó un software de OCR para más de 20 lenguajes índicos. Este software es mucho mejor y más preciso que los OCRs previos, pero tiene muchas limitaciones. Subir un mismo archivo grande dos veces (una vez a Google y otro a Commons) no es una solución fácil para la mayoría de los cooperadores, ya que la conexión a Internet en India suele ser lenta. Lo que sugiero es desarrollar una herramienta que pueda alimentar el archivo subido pdf o djvu de Commons directamente al OCR de Google, con lo que se evita la doble carga del archivo. -- Bodhisattwa (talk) 13:50, 10 November 2015 (UTC)[reply]

Earlier discussion and endorsements

Votos

  1.   Support --Tobias1984 (talk) 11:35, 30 November 2015 (UTC)[reply]
  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)[reply]
  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)[reply]
      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)[reply]
  4.   Support --Satdeep Gill (talk) 14:25, 1 December 2015 (UTC)[reply]
  5.   Support Most needed as of now for Indic Wikisource. We are suffering.Jayantanth (talk) 14:30, 1 December 2015 (UTC)[reply]
  6.   Support This would come handy for many Wikisourcers. --Subhashish Panigrahi (talk) 14:43, 1 December 2015 (UTC)[reply]
  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)[reply]
      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)[reply]
  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)[reply]
      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)[reply]
    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)[reply]
    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)[reply]
    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)[reply]
  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)[reply]
  10.   Support --KRLS (talk) 15:07, 1 December 2015 (UTC)[reply]
  11. Strong support If we can do it , it would be excellent. -- Tito☸Dutta 15:12, 1 December 2015 (UTC)[reply]
  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)[reply]
      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)[reply]
    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)[reply]
    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)[reply]
  13.   Support Anubhab91 (talk) 15:53, 1 December 2015 (UTC)[reply]
  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)[reply]
  15.   Oppose - No google in to wikipedia pls Singhalawap (talk) 17:01, 1 December 2015 (UTC)[reply]
      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)[reply]
  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)[reply]
  17.   Support --Sayant Mahato (talk) 04:20, 2 December 2015 (UTC)[reply]
  18.   Support This is very much needed. - Shubha (talk) 04:26, 2 December 2015 (UTC)[reply]
  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 ( Talk • Contribs ) … 08:53, 2 December 2015 (UTC)[reply]
  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)[reply]
  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)[reply]
  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)[reply]
  23.   Support- Reasons are well explained by Ravi (see above)-Nan (talk) 10:38, 2 December 2015 (UTC)[reply]
  24. Strong   Support --Mathanaharan (talk) 10:41, 2 December 2015 (UTC)[reply]
  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)[reply]
  26.   Support--Balurbala (talk) 12:19, 2 December 2015 (UTC)[reply]
  27.   Support This would come handy for many Wikisourcers--Kurumban (talk) 13:07, 2 December 2015 (UTC)[reply]
  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)[reply]
  29.   Support --Sivakosaran (talk) 15:14, 2 December 2015 (UTC)[reply]
  30.   Support--Parvathisri (talk) 17:45, 2 December 2015 (UTC)[reply]
  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)[reply]
  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)[reply]
  33.   Support --Vikassy (talk) 16:51, 3 December 2015 (UTC)[reply]
  34.   Support -- it will verymuch useful to Indic Languages.--சஞ்சீவி சிவகுமார் (talk) 08:07, 4 December 2015 (UTC)[reply]
  35.   Support --Pymouss Tchatcher - 20:15, 4 December 2015 (UTC)[reply]
  36. Strong   Support --ViswaPrabhaവിശ്വപ്രഭtalk 23:51, 4 December 2015 (UTC)[reply]
  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)[reply]
  38.   Support Very Much useful. -தமிழ்க்குரிசில் (talk) 13:06, 5 December 2015 (UTC)[reply]
  39.   Support -- நி.மாதவன்  ( பேச்சு  )
  40.   Support --Kasyap (talk) 15:39, 7 December 2015 (UTC)[reply]
  41.   Support This will help decrease many man-hours Yohannvt (talk) 07:23, 8 December 2015 (UTC)[reply]
  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)[reply]
  43.   Support -- Mayooranathan (talk) 18:39, 8 December 2015 (UTC)[reply]
  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)[reply]
  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)[reply]


Adaptar el editor visual para Wikisource

Tracked in Phabricator:
Task T48580

En este momento Wikisource usa el viejo pero confiable editor de text. Esto implica que los editores de Wikisource deben conocer muchas plantillas que son diferentes en cada idioma del proyecto. Una versión especial del editor visual, adaptada a las necesidades de Wikisource, facilitaría la cooperación entre los idiomas y facilitaría el trabajo de los nuevos colaboradores en los proyectos Wikisource. Tener botones seleccionados en este editor visual adaptado para títulos, centrar, texto en los márgenes izquierdo y derecho, líneas de seguimiento, etc. facilitaría el aprendizaje, especialmente para aquellos acostumbrados a la apariencia habitual de los procesadores de texto, y ayudaría a traer más colaboradores a los diferentes idiomas de Wikisource.

Poner un título en francés, en inglés, español o croata debería ser ahora la misma cosa: seleccionar el tecto y presionar un botón... no usar una plantilla con nombre diferente dependiendo de la Wikisource en la que uno esté. Mucha gente puede ayudar a corregir páginas en diferentes idiomas, por ejemplo, con un proyecto global de la semana... Yo mismo, siendo un canadiense francófono, sí, podría corregir en francés, inglés, ruso, ucraniano, español, pero no necesito saber todas las plantillas diferentes en todos estos idiomas, y como mi nivel de entendimiento de estos idiomas no es tan bueno como en mi idioma nativo, es a veces difícil buscar en otros proyectos Wikisource... pero nada me impediría ayudar en cualquiera de esos o incluso en proyectos especiales en italiano, búlgaro o portugués... estos usan las mismas letras... para la corrección solo se necesita poder comparar el texto original del libro y el texto transcrito... pero no conocer las plantillas en los diferentes wikisources me impide ayudar a otras comunidades...

La magia de todo esto es que no tenemos que reinventar la rueda! Creo que sería fácil aplicar algunos cambios al Editor Visual usando en los otros proyectos para así concentrarse en editar Wikisource con una lista concisa de otones para las necesidades más básicas, lo que permitiría corregir el 95% o más de las páginas de los libros... en el peor caso, el 5% restante podría hacerse de la manera tradicional... --Ernest-Mtl (talk) 03:31, 10 November 2015 (UTC) — WMCA[reply]

Earlier discussion and endorsements
  Endorsed Slowking4 (talk) 04:36, 11 November 2015 (UTC) user interface major impediment to new users - make WSUG happy[reply]
I believe the linked phab task (phab:T48580) is at least one of the prerequisites to this task. Generally speaking, wikisource uses several extensions to mediawiki core, and both Visual Editor and Parsoid need to have code added to support those extensions. cscott (talk) 18:57, 11 November 2015 (UTC)[reply]
  Endorsed - VE for Wikisource would greatly lower the barriers to entry on what (IMHO) is the sister project with the greatest potential for rapid growth if a little bit of resources were allocated to it. Wittylama (talk) 12:21, 23 November 2015 (UTC)[reply]

Votos

  1.   Support --Tobias1984 (talk) 11:36, 30 November 2015 (UTC)[reply]
  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)[reply]
  3.   Support Risker (talk) 04:17, 1 December 2015 (UTC)[reply]
  4.    Support--Kippelboy (talk) 05:41, 1 December 2015 (UTC)[reply]
  5.    Support --Candalua (talk) 08:57, 1 December 2015 (UTC)[reply]
  6.   Support --Accurimbono (talk) 09:08, 1 December 2015 (UTC)[reply]
  7.   Support --Anika (talk) 09:28, 1 December 2015 (UTC)[reply]
  8.   Support --Rahmanuddin (talk) 15:10, 14 December 2015 (UTC)[reply]
  9.   Support --Xavier121 (talk) 09:40, 1 December 2015 (UTC)[reply]
  10.   Support -- Bodhisattwa (talk) 13:27, 1 December 2015 (UTC)[reply]
  11.   Support --Satdeep Gill (talk) 14:26, 1 December 2015 (UTC)[reply]
  12.   Support obviously. Cdlt, VIGNERON * discut. 14:35, 1 December 2015 (UTC)[reply]
  13.   Support --Tito☸Dutta 14:43, 1 December 2015 (UTC)[reply]
  14.   Support--David Saroyan (talk) 14:46, 1 December 2015 (UTC)[reply]
  15.   Support --KRLS (talk) 15:07, 1 December 2015 (UTC)[reply]
  16.   Support -- Wittylama (talk) 15:07, 1 December 2015 (UTC)[reply]
  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)[reply]
  18.   Support Beleg Tâl (talk) 15:18, 1 December 2015 (UTC)[reply]
  19.   Support Sadads (talk) 16:18, 1 December 2015 (UTC)[reply]
  20.   Support --Wesalius (talk) 19:17, 1 December 2015 (UTC)[reply]
  21.   Support--Arxivist (talk) 20:10, 1 December 2015 (UTC)[reply]
  22.   Support -- Daniel Mietchen (talk) 20:46, 1 December 2015 (UTC)[reply]
  23.   Support  Trizek from FR 22:17, 1 December 2015 (UTC)[reply]
  24.   Support --Aristoi (talk) 22:55, 1 December 2015 (UTC)[reply]
  25.   Support — George Orwell III (talk) 23:28, 1 December 2015 (UTC)[reply]
  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)[reply]
  27.   Support Of course, we are talking about VE in the Proofread page, right? Aubrey (talk) 09:06, 2 December 2015 (UTC)[reply]
  28.   Support --Barcelona (talk) 12:09, 2 December 2015 (UTC)[reply]
  29.   Support--Yodaspirine (talk) 13:02, 2 December 2015 (UTC)[reply]
  30.   Support --Le ciel est par dessus le toit (talk) 13:56, 2 December 2015 (UTC)[reply]
  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)[reply]
  32.   Support Pyb (talk) 01:10, 3 December 2015 (UTC)[reply]
  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)[reply]
  34.   Support - Wieralee (talk) 17:14, 4 December 2015 (UTC)[reply]
  35.   Support --Pymouss Tchatcher - 20:12, 4 December 2015 (UTC)[reply]
  36.   Support Halibutt (talk) 00:24, 5 December 2015 (UTC)[reply]
  37.   Support --Yeza (talk) 10:47, 7 December 2015 (UTC)[reply]
  38.   Support --Kasyap (talk) 15:41, 7 December 2015 (UTC)[reply]
  39.   Support Abyssal (talk) 16:50, 10 December 2015 (UTC)[reply]
  40.   Support --ESM (talk) 16:41, 13 December 2015 (UTC)[reply]
  41.   Support --Davidpar (talk) 14:21, 14 December 2015 (UTC)[reply]
Retrieved from "https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey_2015/Wikisource/es&oldid=25201316"