Page MenuHomePhabricator

Support tables in PDF rendering (tracking)
Closed, ResolvedPublic

Assigned To
None
Authored By
Nemo_bis
Oct 8 2014, 4:26 PM
Referenced Files
None
Tokens
"The World Burns" token, awarded by Liuxinyu970226."The World Burns" token, awarded by Semperor."The World Burns" token, awarded by Man77."Manufacturing Defect?" token, awarded by YMS."Like" token, awarded by OldUser02."The World Burns" token, awarded by Thgoiter.

Description

18.21 < cscott> hm, i guess you might as well make a tracking bug

Support for tables, currently completely skipped. Most notable example: infoboxes.

For some issues in mwlib PDF rendering, see https://www.mediawiki.org/wiki/Thread:Talk:PDF_rendering/Tables


Version: unspecified
Severity: normal

This card tracks a proposal from the 2015 Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey

This proposal received 23 support votes, and was ranked #39 out of 107 proposals. https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Templates#Inserting_templates_.28tables.29_in_PDF_and_Books

This was also on the German Community Wishlist 2015: https://de.wikipedia.org/wiki/Wikipedia:Umfragen/Technische_W%C3%BCnsche_2015/PDF_und_Drucken#Tabellen_in_PDFs

Details

Reference
bz71808

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

I *think* OCG is not currently developed, so it will stay at a lower service level than the predecessor for a while (probably years, if I have to bet).

The Parsoid team is responsible for OCG. @ssastry has committed that crashers will be treated with high priority (to at least achieve graceful recovery). Table support is not scheduled yet and likely a few months out.

The Parsoid team is responsible for OCG. @ssastry has committed that crashers will be treated with high priority (to at least achieve graceful recovery). Table support is not scheduled yet and likely a few months out.

As in, they will fix OCG failing to render lots of articles? As a high priority for the next quarter? info-en@wm.o has received a lot of complaints from readers about those, but it's seemed to me so far that the relevant person on the Parsoid team does not have time available to fix it.

Pollopalko raised the priority of this task from Medium to Unbreak Now!.Aug 1 2015, 2:16 PM
Sjoerddebruin lowered the priority of this task from Unbreak Now! to Medium.Aug 1 2015, 2:17 PM

You can't decide that.

IMPORTANT: If you are a community developer interested in working on this task: The Wikimedia Hackathon 2016 (Jerusalem, March 31 - April 3) focuses on #Community-Wishlist-Survey projects. There is some budget for sponsoring volunteer developers. THE DEADLINE TO REQUEST TRAVEL SPONSORSHIP IS TODAY, JANUARY 21. Exceptions can be made for developers focusing on Community Wishlist projects until the end of Sunday 24, but not beyond. If you or someone you know is interested, please REGISTER NOW.

WMDEs WMDE-TechWish is going to investigate the issue of tables not rendering in pdfs. Currently we don't know yet how far we will get. Just to have a clearer idea what is currently on our todo-list, we opened a new ticket in https://phabricator.wikimedia.org/T135643
If suitable, we will later pull tasks from here to our workboard.

@Lea_WMDE, we have recently looked into alternative rendering strategies with support for tables and other HTML features. See T134205: Options for browser-based server-side PDF generation for a summary of options. We have a basic labs service running a browser-based render service, which you can use to try out the rendering. Examples: Berlin, San Francisco

I had reported that some portion of a wikipedia page is not coming into pdf rendering tool. The report had been merged with a project called T73808 Support tables in PDF rendering (tracking) . Thanks for it, but later-on I discovered, it was not a typical "table", but it was a "gallery" , when I saw the wikicodes in source-editor

Notes from a conversation & prototyping work at Wikimania are available at:

https://docs.google.com/a/wikimedia.org/document/d/13nTL-MHHvMHNQBAvOli5D-e01pslqXecsFQLqWgThwc

Please download and upload to Commons; this URL is not even viewable on my browser due to unspecified cookie requirements.

Notes from a conversation & prototyping work at Wikimania are available at:
https://docs.google.com/a/wikimedia.org/document/d/13nTL-MHHvMHNQBAvOli5D-e01pslqXecsFQLqWgThwc

Please download and upload to Commons; this URL is not even viewable on my browser due to unspecified cookie requirements.

Copied to P3864

As already announced in Tech News, OfflineContentGenerator (OCG) will not be used anymore after October 1st, 2017 on Wikimedia sites. OCG will be replaced by Electron. You can read more on mediawiki.org.

This is fixed on Wikimedia servers nowadays:
General table support for MediaWiki pages exported as PDF was implemented a while ago by removing OCG-PDFRenderer/OfflineContentGenerator and replacing it with Proton and Electron-PDFs as the new PDF rendering stack on Wikimedia servers.

Declining this task as it is explicitly tagged with OfflineContentGenerator which has been dead for years and has been superseded by Proton and Electron-PDFs on Wikimedia servers.

If you run into specific issues with tables in the currently available PDF export on Wikimedia servers, then please file a new ticket with updated information and steps to reproduce. Thanks!

Aklapper changed the task status from Declined to Resolved.Mar 2 2021, 11:22 PM
Aklapper edited projects, added Proton, Epic; removed Tracking-Neverending.

...or well, in terms of Wikimedia (as this was on several wishlists) it probably makes more sense if I add the Proton tag and close it as resolved instead, I guess. :)