Reading/Web/PDF Functionality/es

Update on books, August 8 2018


We have been working with PediaPress on generating and styling the new books. They have provided us with a sample of the current output, which will be very similar to the final version. We discussed points of improvement with the PediaPress team, which they are addressing currently. If you have any feedback or other comments on these samples, please let us know on the talk page.

Update on books, April 2018
Books functionality will be returning via PediaPress. After investigating the new renderer in depth, we realized that core features of the original book creator (such as page numbers and table of contents) would be very difficult to implement using the new renderer. In addition, we had significant issues with our concatenation code. Thus, we had to look for alternatives in terms of bringing back the PDF books functionality on Wikimedia projects. We reached out to PediaPress, who were the original patrons of books on Wikipedia to see if they would be interested in taking up PDF rendering for books once again. They have agreed and we are currently working on the details and schedule. They will start by working on a temporary solution based on an older technology that has previously been used to create PDF. This might have some drawbacks when it comes to graphical elements, such as maps, but will mean a faster working solution. They then plan to work on a new HTML-to-PDF renderer afterwards, based on feedback on the first implementation.

Actualización de Enero 2018
Actualmente estamos preparando pruebas de rendimiento de la función PDF a libro. Deberíamos saber más a principios de febrero.

We're currently preparing performance tests of the PDF to book function. We should know more in early February.

Actualización de septiembre de 2017
Nuestro servicio de renderización de PDF actual, el offline content generator (OCG) ya no será mantenido. En pocas palabras, dejará de funcionar. El equipo de lectura de la Fundación Wikimedia ha estado trabajando durante meses para reemplazarlo. OCG —creado originamente por un tercero— ha estado funcionando con un código desactualizado que podría contener vulnerabilidades de seguridad y otros problemas mayores en el futuro. Durante los últimos tres meses hemos puesto banners en la página de creación de PDF solicitando comentarios sobre el prototipo de nuestro nuevo renderizador. El nuevo renderizador tendrá funcionalidades mejoradas de OCG —podrá imprimir tablas y fichas y contendrá estilo centrado en una mejor legibilidad. Hemos reunido una gran cantidad de comentarios positivos sobre el prototipo y estamos trabajando en hacer las actualizaciones requeridas a nuestros nuevos PDF.

Adición posterior: Desactivación del procesamiento de libros en PDF a corto plazo
Desafortunadamente, problemas importantes con nuestro anterior renderizador (OCG) nos obligarán a prescindir de este antes de completar las actualizaciones necesarias para la elaboración de libros. Es más pronto de lo que queríamos. Para cuando desactivemos OCG, el trabajo de renderizado de artículos individuales estará completo. Sin embargo, el renderizado de libros se detendrá mientras evaluamos y completamos los trabajos necesarios. Nuestra elección inicial para sustituirlo, el servicio de renderizado Electron, no es capaz de soportar archivos PDF de gran tamaño y falla cuando intenta renderizar un libro con muchos artículos. Buscaremos un nuevo sistema para crear libros que pueda soportar el tamaño de los archivos y cumpla nuestros requisitos. No era así como nos lo planteamos y nunca quisimos desactivar temporalmente la funcionalidad de libros en PDF.

Cronología


 * Puesta en marcha de un renderizador completo para artículos individuales (imprimir en PDF) - 1 de octubre de 2017
 * Pausa del renderizado de libros en PDF - 1 de octubre de 2017
 * Desactivación del renderizador OCG - 1 de octubre de 2017
 * Activación de un renderizador de libros completo - Noviembre - diciembre de 2017 (basado tentativamente en las pruebas de sistemas alternativos)

Funcionalidad:

Para un lista completa de funcionalidades actuales y futuras, vea abajo.

Además de las actulizaciones en esta página, esto se comunicará en una pancarta en la página de creación de PDF, en Tech News y en algunas de las listas de correo de Wikimedia.

Introducción
Nuestro servicio actual de renderización, offline content generator, dejará de recibir mantenimiento. Sencillamente, dejará de existir. Creado originalmente por terceros, actualmente funciona con un código obsoleto que podría introducir vulnerabilidades de seguridad y otro tipo de problemas en un futuro. Si vamos a conservar la función de creación de PDF, debemos reemplazarlo, o nos veremos en la situación de desactivarlo sin tener una alternativa.

Además, no soporta diversos requerimientos de renderización de la comunidad, esencialmente la capacidad de renderizar tablas. Hemos elegido un nuevo servicio, el servicio de renderizado Electron, como sustituto adecuado. Nuestro siguiente paso será duplicar la función ofrecida por OCG usando Electron. Más abajo describiremos las partes principales de las funciones que identificamos como necesarias. Nos gustaría invitarle a conversar sobre qué falta o es superfluo en la lista que se ofrece. También desearíamos destacar nuestros futuros planes para renderizar PDF y así recoger propuestas iniciales.

Userbase
The following table shows a sample of traffic to the Electron "Download as PDF" service for over a 6 hour period. The traffic is broken down by operating system (OS), browser, and the browser major version (e.g. Windows 7, Chrome v61.*).

Note well that the majority of our traffic appears to come from Windows based machines.

Requisitos de funcionalidad actuales
La siguiente es una lista de los actuales requisitos de renderizado de PDF a PDF's para artículos y libros. Los requisitos diferentes a los de la implementación actual están mostrados en negrita

History

 * Rendering PDF articles and books from Wikipedia pages is handled by a service called OCG. When rendering "books" through the book creator, it uses OCG as embedded within the Collection extension. OCG has multiple issues, especially with tables.


 * Multiple issues with OCG are identified, including complaints from the community around OCG's inability to render tables.
 * Rendering of tables ranks as number 9 on the German-speaking Community Technical Wishlist.
 * Wikimedia Deutschland begins on working on a solution for rendering tables in PDF's, and introduces Electron. They do this planning to run it alongside OCG, not to replace it.
 * At the same time as Wikimedia Deutschland is working on the Electron service, the responsible maintainers of the OCG service at the Wikimedia Foundation come to the conclusion that OCG has to be replaced.
 * The WMF Reading Team takes over the responsibility for the long term maintenance of PDF rendering begins plans on implementing table rendering across all projects.
 * The Reading team launches a community consultation for gathering feedback on Electron.
 * The Reading Infrastructure and Web teams begin scoping the working necessary to port OCG functionality over to the Electron service.

Update After Consultation
We launched a consultation on the current implementation of the PDF renderer in early June, 2017. After reviewing the consultation responses, we have made the following observations:


 * A larger number of users preferred the single-column format over the double column format
 * Users which prefered the double-column format highlighted that their preference was based in the styling and look and feel of double columns. Some users also expressed concerns with font size and wasting paper when printing PDF's in the single-column option
 * The following feature requests were made:
 * Functional hyperlinks
 * Date and url, 'this page downloaded [date] from [URL]'
 * Customizable css for layout, title, TOC
 * Option for 2 column format
 * Include/exclude images versions
 * Modifiable margins
 * print by section - allows you to remove references, paragraphs you don’t want, index, etc
 * Dejando configurable medida de texto

Based on the feedback, we have incorporated the following into our new print styles:


 * hyperlinks
 * article information
 * smaller font and book-like styling

The remainder of the requests above will be postponed until the second iteration of the PDF renderer, in which we plan to build a settings mode that will allow for customization of the available options.

Proposal
The following is a proposal for the scope of functionality necessary for PDF rendering:


 * Individual articles will be rendered to PDF using the "Download as PDF" link in the sidebar
 * Multiple articles will be rendered to PDF using the Book Creator tool
 * All articles will contain attribution for text and images
 * All PDFs rendered will be able to print tables
 * Users will be able to customize the layout of their PDF (optional)

Design
The new PDF styles will be designed for increased readability. Based on community feedback and qualitative or quantitative testing, support for a 2-column layout may be built for the book creator and/or for individual PDFs.

Development and Deployment Roadmap
The following is a rough outline of the development and deployment roadmap. It is subject to change.


 * 1) April – May 2017:
 * 2) The Reading team builds back-end support for functionality identified above
 * 3) Communities are consulted on expanding or shrinking proposed functionality
 * 4) Qualitative test performed for styling
 * 5) June – July 2017:
 * 6) New styles implemented
 * 7) First iteration is launched along with OCG on all projects and performance is compared
 * 8) Iterations based on consultations and identified edge cases
 * 9) August 2017 – September 2017
 * 10) Additional changes made if necessary
 * 11) October 2017
 * 12) Second iteration launched without OCG on all projects

Single Articles

 * A PDF for a single article will be created by selecting the "Download as PDF" link
 * Upon selecting "Download as PDF", the PDF file will be generated. To download the file, users will select the "Download the file link"
 * Each PDF file will contain the following:
 * Article title and text
 * Infobox (if any)
 * Tables (if any)
 * Single-column layout
 * Page number
 * All article images and captions
 * Links to pages linked from the article (blue links and external links)
 * Text and image sources, contributors, and licenses

Phabricator Tracking
All PDF-related changes including sunsetting OCG, replacing the Electron PDF renderer, and any updates to books or the collections extension are tracked under the phabricator project Proton. The project page will display any recent updates for all tasks related to PDFs.

Functionality available in October, 2017
Note: no changes will be made to the current book creator workflow at this time


 * User will launch the books creator by selecting "Create a book"
 * This will navigate to the current book creation page
 * To download a book, users will select the "download" link from the books page
 * Users may only download books in PDF format
 * Books will contain all elements from single article format as well as:
 * Book title page
 * The references for each article from the book will appear at the end of the article
 * Each article will begin on a new page
 * A single section for text and image sources, contributors, and licenses, that contains the collected contributions from all articles

Functionality available in November - December, 2017
Styles for books will be updated for improved readability
 * Books will contain a table of contents with page numbers
 * Selecting a section from the table of contents will navigate the user to the corresponding section within the book

Alternative
There is an alternative way of exporting MediaWiki to LaTeX, PDF, ODT and EPUB:

http://mediawiki2latex.wmflabs.org/

The computational resources on the server are limited.

If you run Ubuntu Linux and want results faster, you can install the m2l-pyqt or mediawiki2latex packages.

__INDEX__