This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11962 - Add HTML tag support for generation of PDF documents or Post Scripts
Summary: Add HTML tag support for generation of PDF documents or Post Scripts
Status: CLOSED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-02 15:50 UTC by Manjunath Baddi
Modified: 2013-02-02 15:29 UTC (History)
6 users (show)

See Also:

Attachments

Description Manjunath Baddi 2011-02-02 15:50:56 UTC 
I think now is the right time for HTML5 to introduce new tags for generation of PDF documents/Post Scripts...!! Today most of the developers have to deal with this issue of providing PDF document/post scripts support for their website contents[blogs,wikis, etc]. And to achieve this, web developer is restricted with only one option, that is generating PDF document/Post Scripts at server-side using one of the Server-Side language, which ultimately increases unnecessary-heavy-load on web server. If HTML5 introduces new tag support for generation of PDF documents/ Post Scripts and subsequently web browsers implement this feature, then I think we can avoid unnecessary load on web server and utilize the processing power at client-side.
Comment 1 Ian 'Hixie' Hickson 2011-02-28 22:41:37 UTC 
You can already do this as far as I can tell. For example, with Safari on Mac, you would press Command-P then click "Preview", and this generates a PDF for you from the open HTML page.
Comment 2 Robin Berjon 2013-01-21 15:59:42 UTC 
Mass move to "HTML WG"
Comment 3 Robin Berjon 2013-01-21 16:02:27 UTC 
Mass move to "HTML WG"
Comment 4 Erika Doyle Navara 2013-02-01 00:29:57 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:


   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: (None.)
Rationale: 
This seems out of scope for inclusion in the HTML language itself. It has potential use considering that HTML is an application platform and not simply a document language. As such, it could make sense to convert other HTML (e.g., iframe content) into a PDF, but it doesn't make sense to convert yourself (the code actually running the application) into PDF.

This might work too:
http://cutepdf.com/Products/CutePDF/writer.asp