Talk:Reading/Web/PDF Functionality/2018/03

About giving feedback

Please read Reading/Web/PDF Functionality and comment on the plans we lay out there, to tell us what you need from the PDF service. We're especially interested in what you need in the future that doesn't exist in the plans laid out there – if there's a bug with something that should work right now (e.g. you get an error message when you try to create a PDF), we need to fix it, of course, but that would have been on the agenda.

Updates: (24 February 2018)

- Kerning and spacing issues (https://phabricator.wikimedia.org/T178665): there has been a few reports on spacing issues within PDF rendering. The readers web team is currently looking into a solution. We will first be updating the fonts for PDFs (https://phabricator.wikimedia.org/T181200) over the week of November 27. This will resolve some but not all of the spacing issues. We'll be looking further into the remaining issues after the initial fix.

- Update on the book creator. We're still in the process of performance testing the new renderer (https://phabricator.wikimedia.org/T178278). Once this stage is complete, we will be able to provide more details on its capacity to render books.

HTML output

The old OCG could output in a variety of formats. Is it correct to assume that headless Chrome must first have all the wikitext pages, copyright small print, etc. pre-processed into HTML+CSS before rendering? If so, is it possible to intercept the intermediate HTML/CSS format and offer an HTML download option? That might be say CHTM or ePub or just a raw zip. Or if the book is assembled in the DOM or whatever, could that be persuaded to spit out the HTML? This would then allow client-side conversion to other formats, which is next to impossible from PDF. Steelpillow (talk) 05:53, 5 March 2018 (UTC)

Yes, any format that can be parsed and post-process would be a great support for generating derived products as w:Open Educational Resources. Spencer Kelly is currently doing a great job in developing wtf_wikipedia.js further. It allows the generation of JSON for MediaWiki-article (see demo https://niebert.github.io/Wiki2Reveal/wtf_wiki2html.html ) conversion to plain text and may be other formats will follow. The conversion can be done on client side even in a browser just by contacting the MediaWiki-API, download the Wiki source of the article and parse it into whatever is content product is needed. Nevertheless the PDF generation is great and very much appreciated. Bert Niehaus (talk) 08:21, 5 March 2018 (UTC)

Update Link to Wiki2Reavel https://niebert.github.io/Wiki2Reveal/

Possible application for learning and capacity building e.g. lectures at universities see https://en.wikiversity.org/wiki/PanDocElectron/Presentation

https://github.com/spencermountain/wtf_wikipedia/wiki Bert Niehaus (talk) 03:01, 14 July 2018 (UTC)

Wikipedia permite culturizar al mundo

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Wikipedia permite culturizar al mundo, desde la tierna infancia, hacia el más alto nivel intelectual. Korriskoso-vnt (talk) 02:18, 20 March 2018 (UTC)

Gracias. Johan (WMF) (talk) 20:00, 26 March 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

What happened to my post???

Why is [1] and [2] not shown anymore??? And what happened to the phabricator link https://phabricator.wikimedia.org/T29574 that I included in the first post (within the now empty brackets)??? Debenben (talk) 17:39, 22 March 2018 (UTC)

There is an occasional caching bug that the devs are looking at (phab:T190429). I posted a reply to that thread, which fixed this instance.

Re: the incorrect display of the diff, I've filed phab:T190466. Thanks for the bug-report. :) Quiddity (WMF) (talk) 22:01, 22 March 2018 (UTC)