Please refer to the errata for this document, which may include some normative corrections.
This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip'd TAR archive.
See also translations.
Copyright © 2006 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
XHTML-Print is member of the family of XHTML languages defined by the Modularization of XHTML [XHTMLMOD]. It is designed to be appropriate for printing from mobile devices to low-cost printers that might not have a full-page buffer and that generally print from top-to-bottom and left-to-right with the paper in a portrait orientation. XHTML-Print is also targeted at printing in environments where it is not feasible or desirable to install a printer-specific driver and where some variability in the formatting of the output is acceptable.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
All sections of this document are normative unless noted as informative.
This document contains the XHTML™-Print W3C Recommendation of 20 September 2006, which has incorporated the disposition of Proposed Recommendation feedback .
This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
This document incorporates minor suggestions made during the XHTML-Print Proposed Recommendation of 31 January 2006 and also removes any requirement for CSS support; please see the public disposition of comments for details. Evidence of interoperability between two implementations of this specification is documented in the Implementation Report.
This document has been produced by the W3C HTML Working Group (Members only) as part of the W3C HTML Activity. The goals of the HTML Working Group are discussed in the HTML Working Group charter.
This document was produced by a group operating under the 24 January 2002 CPP as amended by the W3C Patent Policy Transition Procedure. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
Please report errors in this document to www-html-editor@w3.org (archive).
All sections of this document are normative unless noted as informative.
This section is informative.
This document specifies a simple XHTML based data stream suitable for printing as well as display. It is based on XHTML Basic [XHTMLBASIC]. Its targeted usage is for printing in environments where it is not feasible or desirable to install a printer-specific driver and where some variability in the formatting of the output is acceptable. Throughout this document this data stream is called "XHTML-Print."
XHTML-Print is designed to be appropriate for low-cost printers that might not have a full-page buffer and that generally print from top-to-bottom and left-to-right with the paper in a portrait orientation. For other printers (i.e., those that print in another direction or orientation) a full-page buffer could be needed.
XHTML-Print is not appropriate when strict layout consistency and repeatability across printers are needed. The design objective of XHTML-Print is to provide a relatively simple, broadly supportable page description format where content preservation and reproduction are the goal, i.e. "Content is King." Traditional printer page description formats such as PostScript or PCL are more suitable when strict layout control is needed. XHTML-Print does not utilize bi-directional communications with the printer either for capabilities or status inquiries.
This document creates a set of conformance criteria for XHTML-Print. It provides a strong basis for consistent printing results without a detailed understanding of each individual printer's characteristics.
The document type definition for XHTML-Print is implemented based on the XHTML modules defined in Modularization of XHTML [XHTMLMOD].
The keywords "MUST", "SHALL", "MUST NOT", "SHALL NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" when used in this document are to be interpreted as described in RFC 2119 [RFC2119]. However, for readability, these words might not appear in all uppercase letters in this specification.
This section explains why certain HTML features are not part of XHTML-Print and any special circumstances concerning a module and printing.
Scripts, as programs that are executed in conjunction with a document, are not relevant to the printed page. However, documents can provide information as an alternative to a script. Therefore,
the script module is part of XHTML-Print. Scripts MUST NOT be executed and their results MUST NOT be printed. If a noscript
element is present, it contains alternate content that MUST be printed in
place of the content of the script
element.
Events are not applicable to static, printed versions of a document. Therefore, the Intrinsic Events module is not part of XHTML-Print.
Many simple printers cannot print a wider variety of fonts than generic serif, sans serif and monospace. It is RECOMMENDED that style sheets be used to create a presentation that is appropriate for a particular category of printer. How printers are categorized, what those categories are, how a printer identifies itself as a member of a category, and how style sheets are selectively applied based on category, is outside the scope of this document.
The Presentation module ([XHTMLMOD], section 5.4.1) is supported to provide simple control over basic font variants and rules.
Basic XHTML forms ([XHTMLMOD], section 5.5.1) are supported. Content developers SHOULD keep in mind that users might not be able to input many characters from some devices (e.g. from a mobile phone). Furthermore, developers are cautioned that a printer prints a static version of a form, and the visual appearance of a form depends heavily on the implementation.
Basic XHTML tables ([XHTMLMOD], section 5.6.1) are supported, but tables can be difficult to format on very low resource devices. Furthermore, content developers are cautioned that in the Basic Tables Module, nesting of tables is prohibited.
Frames are not supported. Frames depend on a screen interface and therefore are not applicable to printers.
XHTML-Print is a member of the family of XHTML languages defined by Modularization of XHTML [XHTMLMOD]. Therefore, the elements and attributes in the modules that make up XHTML-Print are all valid constructs of the language. However, not all the attributes are applicable to a rendering of an XHTML-Print document in printed media, especially those that are integral to a dynamic display of the document in a browser and the submission of a form. Furthermore, special attention is given to simple printers and some attributes are deemed too complex for a such a printer to render. These attributes are treated as discretionary in that a conforming printer is not REQUIRED to support them, but if a printer wishes to provide that support, there are requirements stated for consistency in the implementation of extensions.
The W3C architectural specification Character Model for the World Wide Web 1.0 [CHARMOD] gives the RECOMMENDED representation of characters in XHTML-Print. Authors of XHTML-Print producing applications should be aware that low cost printers might be limited in both processing power and memory and therefore, that normalized utf-8 encoded documents could print more quickly than documents in other forms and encodings.
A conforming XHTML-Print document is a document that requires only the facilities described as mandatory in this specification. Such a document SHALL meet all of the following criteria:
html
.http://www.w3.org/1999/xhtml
.The MIME type used to refer to a conforming XHTML-Print document SHALL be "application/xhtml+xml" with an OPTIONAL "profile" parameter of 'http://www.w3.org/Markup/Profile/Print'. An OPTIONAL "charset" parameter MAY be provided with the MIME type. Invalid values MUST be ignored and the result be as if the value were "utf-8". Usage of the OPTIONAL "charset" parameter is as described in Section 3.2 of RFC3023 - XML Media Types [RFC3023]. Usage of the OPTIONAL "profile" parameter is as described in Section 8 of RFC3236 - The 'application/xhtml+xml' Media Type RFC3236].
A printer user agent MUST conform to the XHTML Family User Agent Conformance section of the Modularization of XHTML specification ([XHTMLMOD], section 3.5) with the following exceptions and additions:
height
and width
attributes and
MAY optionally draw a box around this space of the size specified for the image.height
and width
attributes are not provided, the printer MUST attempt
to print the image at its intrinsic size. If the image data contain no size information, this specification does not define the size at which the image will be rendered.xml:lang
attribute are not REQUIRED to adhere to the rules for language specific white
space handling.The XHTML-Print document type is defined as a set of XHTML modules. All XHTML modules are defined in the Modularization of XHTML specification [XHTMLMOD].
XHTML-Print consists of the following XHTML modules:
body, head, html, title
abbr, acronym, address, blockquote, br, cite, code, dfn, div, em, h1, h2, h3, h4, h5, h6, kbd, p, pre, q, samp, span, strong, var
a
dl, dt, dd, ol, ul, li
b, big, hr, i, small, sub, sup, tt
form, input, label, select, option, textarea
caption, table, td, th, tr
img
object, param
meta
noscript
, script
style
style
attributelink
base
(*) = This module is a REQUIRED XHTML
Host Language module.
(**) = These modules are not a part of XHTML Basic but are REQUIRED for XHTML-Print.
An XML 1.0 DTD is available in Appendix C.
Some of the attributes defined in the Modularization of XHTML [XHTMLMOD] are not applicable to the printed page or are not relevant due to the exclusion of their module from XHTML-Print. Other attributes are not REQUIRED but if supported by a printer, support SHOULD be provided in the RECOMMENDED manner.
Each attribute in the following sections is annotated with one of the following keywords indicating support options for a conforming printer:
Key | Description |
---|---|
MUST | Support is mandatory; a conforming printer MUST implement this attribute. (However, the inability of a printer to implement part of this specification due to the limitations of a particular device does not imply non-conformance. E.g., the fact that a monochrome printer user agent cannot render colors does not preclude its conformance to this specification.) |
SHOULD | Support for the attribute is RECOMMENDED, but not REQUIRED. |
MAY | The attribute's functionality is entirely OPTIONAL. |
N/A | The attribute does Not Apply to the printed page; a conforming printer MAY ignore this attribute for one of the following reasons, but MUST NOT treat it as an error:
|
The Modularization of XHTML ([XHTMLMOD], section 5.1) contains a set of attribute collections for ease of presentation. This specification continues this practice with the same conditions, that is, that the collections below are informative and their contents normative.
Collection Name | Attributes in Collection | REQUIRED Processing |
---|---|---|
Core | class (NMTOKENS† ) | MUST |
Core | id (ID† ) | MUST |
Core | title (CDATA† ) | N/A |
I18N | xml:lang (NMTOKEN† ) | MAY |
Style | style (CDATA† ) | MUST |
Common | Core + I18N + Style | See Collections |
Table Note:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
Note that the title
attribute of the Core collection is not applicable to the printed page since there is no place to display such supplementary information.
A printer MAY support special processing based on the natural language of the document, such as the use of guillemets for quotation marks
in French text. If a printer implements processing based on the natural language of the document, that processing SHALL be controlled by the
xml:lang
attribute.
A printer SHOULD support CSS style sheets, as noted in section 1.3.2 Presentation, within the limits of its capabilities.
Elements | Attributes | REQUIRED Processing |
---|---|---|
body | Common | See Collection |
head | I18N, | See Collection |
head | profile (URI† ) | MAY |
html | I18N, | See Collection |
html | version (CDATA† ), | N/A |
html | xmlns (URI† = "http://www.w3.org/1999/xhtml") | MUST |
title | I18N | See Collection |
Table Note:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
If a printer implements support for meta data then it MUST support the profile
attribute of the head
element.
The version
attribute is not applicable for printing since it was deprecated in the HTML 4.01 Specification [HTML4] in favor of version
information within the DTD.
A printer MAY ignore the content of the title
element since it is not part of the document's body.
Elements | Attributes | REQUIRED Processing |
---|---|---|
abbr, acronym, address | Common | See Collection |
blockquote | Common, | See Collection |
blockquote | cite (URI† ) | N/A |
br | Core | See Collection |
cite, code, dfn, div, em, h1, h2, h3, h4, h5, h6, kbd, p | Common | See Collection |
pre | Common, | See Collection |
pre | xml:space="preserve" | MUST |
q | Common, | See Collection |
q | cite (URI† ) | N/A |
samp, span, strong, var | Common | See Collection |
Table Note:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
Element | Attributes | REQUIRED Processing |
---|---|---|
a | Common, | See Collection |
a | accesskey (Character† ), | N/A |
a | charset (Charset† ), | N/A |
a | href (URI† ), | N/A |
a | hreflang (LanguageCode† ), | N/A |
a | rel (LinkTypes† ), | N/A |
a | rev (LinkTypes† ), | N/A |
a | tabindex (Number† ), | N/A |
a | type (ContentType† ) | N/A |
Table Note:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
Elements | Attributes | REQUIRED Processing |
---|---|---|
dl, dt, dd, ol, ul, li | Common | See Collection |
Elements | Attributes | REQUIRED Processing |
---|---|---|
b, big, hr, i, small, sub, sup, tt | Common | See Collection |
Elements | Attributes | REQUIRED Processing |
---|---|---|
form | Common, | See Collection |
form | action* (URI† ), | N/A |
form | method ("get"** | "post"), | N/A |
form | enctype (ContentType† ) | N/A |
input | Common, | See Collection |
input | accesskey (Character† ), | N/A |
input | checked ("checked"), | MUST |
input | maxlength (Number† ), | N/A |
input | name (CDATA† ), | N/A |
input | size (Number† ), | MUST |
input | src (URI† ), | N/A |
input | tabindex (Number† ), | N/A |
input | type("text"** ) | MUST |
input | type("password" ) | MUST |
input | type("checkbox" ) | MUST |
input | type("radio" ) | MUST |
input | type("submit") | MUST |
input | type("reset" ) | MUST |
input | type("hidden" ) | MUST |
input | value (CDATA† ) | MUST |
label | Common, | See Collection |
label | accesskey (Character† ), | N/A |
label | for (IDREF† ) | N/A |
select | Common, | See Collection |
select | multiple ("multiple"), | N/A |
select | name (CDATA† ), | N/A |
select | size (Number† ), | MUST |
select | tabindex (Number† ) | N/A |
option | Common, | See Collection |
option | selected ("selected"), | MUST |
option | value (CDATA† ) | N/A |
textarea | Common, | See Collection |
textarea | accesskey (Character† ), | N/A |
textarea | cols* (Number† ), | MUST |
textarea | name (CDATA† ), | N/A |
textarea | rows* (Number† ), | MUST |
textarea | tabindex (Number† ) | N/A |
Table Notes:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
* The attribute MUST be present.
** The value is the default.
The src
attribute of the input
element is not supported since the image
type is not part of basic forms.
The hidden
type for the input
element MUST be supported even though nothing is printed, so that a printer can
correctly recognize and ignore the element.
Elements | Attributes | REQUIRED Processing |
---|---|---|
caption | Common | See Collection |
table | Common, | See Collection |
table | summary ( Text† ) | N/A |
td, th | Common, | See Collection |
td, th | abbr (Text† ), | MAY |
td, th | align ("left" | "center" | "right"), | MUST |
td, th | axis (CDATA† ), | N/A |
td, th | colspan (Number† ), | MUST |
td, th | headers (IDREFS† ), | N/A |
td, th | rowspan (Number† ), | MUST |
td, th | scope ("row" | "col"), | N/A |
td, th | valign ("top" | "middle" | "bottom") | MUST |
tr | Common, | See Collection |
tr | align ("left" | "center" | "right"), | MUST |
tr | valign ("top" | "middle" | "bottom") | MUST |
Table Note:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
If a printer implements a feature to truncate the contents of a cell because of space constraints, it MUST support the abbr
attribute and print the value of the abbr
attribute (if present) instead of the cell's content.
A printer MUST support the values left
, right
, and center
for the align
attribute of
the td
, th
, and tr
elements; other values are OPTIONAL. If the align
attribute is
missing or has an unsupported value, a printer MUST act as if the align
attribute has the value left
for the
td
and tr
elements, and as if the align
attribute has the value center
for the th
element.
A printer MUST support the values top
, middle
, and bottom
for the valign
attribute of
the td
, th
, and tr
elements, other values are OPTIONAL. If the valign
attribute is
missing or has unrecognized value, a printer SHOULD act as if the valign
attribute has the value middle
. Vertical
alignment is undefined across page boundaries.
Elements | Attributes | REQUIRED Processing |
---|---|---|
img | Common, | See Collection |
img | alt* (Text† ), | MUST |
img | height (Length† ), | MUST |
img | longdesc (URI† ), | N/A |
img | src* (URI† ), | MUST |
img | width (Length† ) | MUST |
Table Notes:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
* The attribute MUST be present.
Printers MUST support the http [RFC2616] URI scheme [RFC3986]. Support for other schemes is OPTIONAL. Printers MUST support the JPEG image format as defined in Appendix A.
Conforming documents SHOULD specify the width and height of the image using the width
and height
attributes or
equivalent styling instructions. (See 2.3.1 Formatting/Rendering Rules).
Elements | Attributes | REQUIRED Processing |
---|---|---|
object | Common, | See Collections |
object | archive (URIs† ), | N/A |
object | classid (URI† ), | N/A |
object | codebase (URI† ), | MUST |
object | codetype (ContentType† ), | N/A |
object | data (URI† ), | MUST |
object | declare ("declare"), | MAY |
object | height (Length† ), | MUST |
object | name (CDATA† ), | N/A |
object | standby (Text† ), | N/A |
object | tabindex (Number† ), | N/A |
object | type ("image/jpeg"), | MUST |
object | width (Length† ) | MUST |
param | id (ID† ), | N/A |
param | name* (CDATA† ), | N/A |
param | type (ContentType† ), | N/A |
param | value (CDATA† ), | N/A |
param | valuetype ("data"** | "ref" | "object") | N/A |
Table Notes:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
* The attribute MUST be present.
** The value is the default.
Printers MUST support the http [RFC2616] URI scheme [RFC3986]. Support for other schemes is OPTIONAL.
A printer MUST support resources of type "image/jpeg." A printer MAY support
other types of image formats and therefore other values of the type
attribute. A printer MUST process the content of the
object
element when it does not recognize or support the object type referenced by the value of the type
attribute.
Conforming documents SHOULD specify the width and height of the image using the width
and height
attributes or
equivalent styling instructions. (See 2.3.1 Formatting/Rendering Rules).
The param
element's purpose is to pass data to an application specified in the enclosing object
element. The param
element MAY be completely ignored.
Elements | Attributes | REQUIRED Processing |
---|---|---|
meta | I18N, | See Collection |
meta | content* (CDATA† ), | N/A |
meta | http-equiv (NMTOKEN† ), | N/A |
meta | name (NMTOKEN† ), | N/A |
meta | scheme (CDATA† ) | N/A |
Table Notes:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
* The attribute MUST be present.
A printer MAY implement support for this element and provide implementation specific processing of the meta-information. However, guidelines and/or recommendations for processing a document's meta-information are beyond the scope of this document.
Elements | Attributes | REQUIRED Processing |
---|---|---|
noscript | Common, | See Collections |
script | charset (Charset), | N/A |
script | defer ("defer"), | N/A |
script | src(URI), | N/A |
script | type (ContentType), | N/A |
script | scheme (CDATA) | N/A |
Scripts, as programs that are executed in conjunction with a document, are not relevant to the printed page and MUST NOT be executed
or printed. The noscript
element contains alternate content that MUST be printed in place of the content of the
script
element when present.
Elements | Attributes | REQUIRED Processing |
---|---|---|
style | I18N, | See Collection |
style | media (MediaDesc† ), | SHOULD |
style | title (Text† ), | N/A |
style | type*, | MUST |
style | xml:space="preserve" | SHOULD |
Table Notes:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
* The attribute MUST be present.
A printer MUST read and process the content of style
elements where the media
attribute has the value
print
or all
. A printer MAY read and process the content of style
elements where the media
attribute has the value projection
. A printer SHOULD ignore the content of style
elements where the
media
attribute has any other value. The absence of the media
attribute MUST be treated as if the media
attribute had the value all
.
A printer SHOULD read and process the content of style
elements where the value of the type
attribute is
"text/css"; a printer MAY read and process the content of style
elements where the value of the type
attribute is
other than "text/css"; all unsupported values for type
MUST cause the content to be ignored. Style elements without a
type
attribute will be treated in an implementation-dependent manner.
This module adds the style attribute to the Common attribute collection (section 3.1).
Elements | Attributes | REQUIRED Processing |
---|---|---|
link | Common, | See Collection |
link | charset (Charset† ), | MUST |
link | href (URI† ), | MUST |
link | hreflang (LanguageCode† ), | MAY |
link | media (MediaDesc† ), | MUST |
link | rel ("stylesheet"), | MUST |
link | rev (LinkTypes† ), | N/A |
link | type | MUST |
Table Note:
† See Modularization of XHTML ( [XHTMLMOD], section 4.3 )
Printers MUST support the http [RFC2616] URI scheme [RFC3986]. Support for other schemes is OPTIONAL.
If the printer implements processing based on the natural language of the document, then the hreflang
attribute MUST be
supported.
A printer SHOULD read and process the content of external style sheets where the media
attribute has the value
print
or all
. A printer MAY read and process the content of external style sheets where the media
attribute
has the value projection
. A printer SHOULD ignore the content of external style sheets where the media
attribute
has any other value. The absence of the media
attribute MUST be treated as if the media
attribute had the value
all
.
A printer SHOULD support the value stylesheet
for the rel
attribute along with the value "text/css" for the
type
attribute; all other values are OPTIONAL.
Elements | Attributes | REQUIRED Processing |
---|---|---|
base | href* (URI† ) | MUST |
Table Notes:
† See Modularization of XHTML( [XHTMLMOD], section 4. 3
* The attribute MUST be present.
Printers MUST support the http [RFC2616] URI scheme [RFC3986]. Support for other schemes is OPTIONAL.
XHTML-Print is in the family of XHTML document types, since it is created by combining XHTML modules. The character entities that are part of XHTML-Print are, therefore, defined in XHTML Character Entities ([XHTMLMOD], Section F.1).
XHTML-Print inherits all the structure, encoding and other basic infrastructure specified by XHTML 1.0 [XHTML1]. The following sections describe and clarify the application and usage restrictions of XHTML-Print.
This document specifies only one mandatory image format: baseline JPEG as defined in JPEG File Interchange Format [JPEG]. See Appendix A for a description of JPEG decoder requirements. Printers are not REQUIRED to support:
within the JFIF (JPEG File Interchange Format) and EXIF (Exchangeable Image File Format) files.
img
and object
ElementsBecause many printers create the page in a serial manner from top to bottom, it is important for the printer to know the size of images before retrieving the image data itself. This information is
then used to create portions of the page layout.
Therefore, the document SHOULD include the height
and width
attributes within the img
or the
object
element (or equivalent styling instructions). These attributes MAY be expressed as pixels or percentages within the
img
or the object
element. Percentages are relative to the parent element and not the page width or printable area.
[Informative]
In traditional Web-based applications of XHTML, image data is contained in a separate file on a Web server that the user agent retrieves.
However, there are circumstances where it is desirable to include the image data along with the rest of the print data. For example, some low cost, resource constrained clients might want to include images in their print output but cannot afford to include an HTTP server. Furthermore, circumstances could require that all the print data be encapsulated in a single file for transportability, avoiding firewall issues, etc. Therefore, conforming XHTML-Print printers MAY optionally support a format that contains both a document and its referenced image data as well as the REQUIRED traditional format that contains only the document.
The format recommended for including image data along with xhtml-print markup is defined by RFC3391 - The MIME Application/Vnd.pwg-multiplexed Content-type. [MIMEMPX].
Including image data as defined in RFC2397 - The data URL scheme [RFC2397] may be appropriate for printers capable of buffering large amounts of data, but
will not achieve the intended results for most cost- and memory-constrained printer UA's. Because this method normally encodes the binary image data using base64 encoding, a significant increase in
the size of the data transmitted will be experienced. This should be avoided over low speed connections. Printers supporting included data can support base64 encoding using the img
or
object
element.
Mechanisms for determining whether or not a printer supports either of the above OPTIONAL document formats is outside the scope of this specification.
Low-cost printers today often have very little memory into which page data can be stored before being printed. As such, they may build and print the page in swaths on the fly from the top of the page to the bottom. To enable the use of XHTML-Print in these low cost printers, some restrictions on the order of images contained in the XHTML-Print data stream must be added.
<img src="http://example.com/example.jpg">
. This allows the printer to get chunks of the
image, as it needs it, as it prints down the page. Interleaved or included image data, as discussed in Section 4.1.2, is discouraged.Conforming XHTML-Print printers SHALL support both in-line and referenced style sheets within the style
element or
link
element in the head
element of a document. Conforming XHTML-Print printers SHALL also support the
style
attribute (i.e. in-line style) when used within other elements as defined by XHTML 1.1[XHTML1.1]. Normal cascading rules apply.
This section is informative.
An HTML form is a dynamic entity when the document is displayed in a browser: data can be entered into text fields, buttons can be pushed, selections made, and options checked. None of this dynamic activity can be rendered on a printed page. However, a printed page can permanently record a particular state of the form. For example, users might wish to print forms that record products ordered or payments made.
The following discussion illustrates the activity involved when interacting with and printing forms. Please refer to Sequence Diagram 1
Sequence Diagram 1. Forms Usage
Steps:
Detailed discussion of Steps:
Here is an example presentation of the above form as the user would see it:
This section is informative.
This specification was prepared by the W3C HTML Working Group. The participants at the time of publication were:
This specification is based in large part on the specification of the same name, XHTML™-Print [XHTMLPRINT], from the Printer Working Group, a program of and through the IEEE Industry Standards and Technology Organization, Inc.; and which was in turn based in large part upon an earlier work with the same name by Fujisawa, Grant, Wright, and Zehler [XHP]. The editors wish to express their gratitude to all who contributed to this and earlier versions.
This appendix describes REQUIRED behaviors for JPEG decoders in XHTML-Print devices. Many of the behaviors described in this document follow directly from language already present in the relevant JPEG standards, but are repeated here to emphasize their importance.
The decoder behaviors described in this document are intended to minimize implementation complexity, while retaining maximum compatibility with existing JPEG files. In particular, these recommendations seek to ensure compatibility with both EXIF (Exchangeable Image File Format) and baseline JFIF (JPEG File Interchange Format); i.e., the subset of JFIF files that use only baseline JPEG processes. Support for JPEG streams using non-baseline processes, such as arithmetic coding or progressive coding, is not mandated for XHTML-Print compliance.
This section describes behaviors of JPEG decoders for XHTML-Print conformant implementations.
A JPEG decoder for an XHTML-Print printer SHALL support all baseline JPEG processes as defined in [CCITT], except for 2- and 4-component images. These processes include grayscale and 3-component images, 8-bit/component sample depth, Huffman entropy coding, 444, 422, 411, and 400 subsampling modes, and sequential (i.e. non-progressive) scan.
Baseline decoders MAY ignore application-specific markers, such as the JFIF APP0 marker and the EXIF APP1/APP2 markers; rotation fields within these markers SHOULD be ignored. (Specifically, conforming printers SHOULD NOT decode the TIFF IFDs embedded in the EXIF APP1 and APP2 markers, as described in Section 2.6.4 of [JEIDA].) This implies images will print in the orientation in which they are stored, unless style markup indicates otherwise. The image size SHOULD be rendered as specified in the JPEG SOF marker, if not overridden by style mark-up. A JPEG decoder for a conforming printer SHALL NOT fail as a consequence of encountering an unsupported APPx marker (i.e. all such markers SHALL be correctly parsed, even if they are ignored).
This section describes a RECOMMENDED color management approach for XHTML-Print printers.
Sample values in a grayscale (single-component) JPEG image MAY be converted to the sRGB color space by setting
Rout= Gout= Bout= Grayin
or by other suitable algorithm specific to the XHTML-Print device.
Sample values in 3-component JPEG images SHALL be interpreted as YCbCr samples, as would be obtained by applying the matrices described in ITU BT.601 [BT601.5] to sRGB input data.
This section contains the pieces of the XHTML-Print DTD that are unique to XHTML-Print. The remaining entities and modules are as specified in reference [XHTMLMOD].
The following SHOULD be used from Modularization of XHTML [XHTMLMOD]:
Available for download at xhtml-print10.dtd.
<!-- ....................................................................... --> <!-- XHTML-Print 1.0 DTD ................................................... --> <!-- file: xhtml-print10.dtd --> <!-- XHTML-Print 1.0 DTD This is XHTML-Print 1.0, a variant of XHTML Basic for printing. Copyright 1998-2003 World Wide Web Consortium (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All Rights Reserved. Permission to use, copy, modify and distribute the XHTML-Print DTD and its accompanying documentation for any purpose and without fee is hereby granted in perpetuity, provided that the above copyright notice and this paragraph appear in all copies. The copyright holders make no representation about the suitability of the DTD for any purpose. It is provided "as is" without expressed or implied warranty. Primary Author: Jun Fujisawa <fujisawa.jun@canon.co.jp> Editors: Jim Bigelow <jim.bigelow@hp.com>, Shane McCarron <shane@aptest.com>, Masayasu Ishikawa <mimasa@w3.org> Revision: $Id: Overview.html,v 1.3 2018/10/09 13:29:20 denis Exp $ --> <!-- This is the driver file for version 1.0 of the XHTML-Print DTD. This DTD is identified by the PUBLIC and SYSTEM identifiers: PUBLIC "-//W3C//DTD XHTML-Print 1.0//EN" SYSTEM "http://www.w3c.org/MarkUp/DTD/xhtml-print10.dtd" --> <!ENTITY % XHTML.version "-//W3C//DTD XHTML-Print 1.0//EN" > <!-- Use this URI to identify the default namespace: "http://www.w3.org/1999/xhtml" --> <!ENTITY % NS.prefixed "IGNORE" > <!ENTITY % XHTML.prefix "" > <!-- Reserved for use with the XLink namespace: --> <!ENTITY % XLINK.xmlns "" > <!ENTITY % XLINK.xmlns.attrib "" > <!-- reserved for future use with document profiles --> <!ENTITY % XHTML.profile "" > <!-- Bidirectional Text features This feature-test entity is used to declare elements and attributes used for bidirectional text support. --> <!ENTITY % XHTML.bidi "IGNORE" > <!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: --> <!ENTITY % xhtml-events.module "IGNORE" > <!ENTITY % xhtml-bdo.module "%XHTML.bidi;" > <!-- Style Attribute Module ............................ --> <!ENTITY % xhtml-inlstyle.module "INCLUDE" > <![%xhtml-inlstyle.module;[ <!ENTITY % xhtml-inlstyle.mod PUBLIC "-//W3C//ENTITIES XHTML Inline Style 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-inlstyle-1.mod" > %xhtml-inlstyle.mod;]]> <!-- Document Model Module ............................. --> <!ENTITY % xhtml-model.mod PUBLIC "-//W3C//ENTITIES XHTML-Print 1.0 Document Model 1.0//EN" "xhtml-print10-model-1.mod" > <!-- Modular Framework Module (required) ............... --> <!ENTITY % xhtml-framework.mod PUBLIC "-//W3C//ENTITIES XHTML Modular Framework 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-framework-1.mod" > %xhtml-framework.mod; <!-- Text Module (required) ............................ --> <!ENTITY % xhtml-text.mod PUBLIC "-//W3C//ELEMENTS XHTML Text 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-text-1.mod" > %xhtml-text.mod; <!-- Hypertext Module (required) ....................... --> <!ENTITY % xhtml-hypertext.mod PUBLIC "-//W3C//ELEMENTS XHTML Hypertext 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-hypertext-1.mod" > %xhtml-hypertext.mod; <!-- Lists Module (required) ........................... --> <!ENTITY % xhtml-list.mod PUBLIC "-//W3C//ELEMENTS XHTML Lists 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-list-1.mod" > %xhtml-list.mod; <!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: --> <!-- Presentation Module ............................... --> <!ENTITY % xhtml-pres.module "INCLUDE" > <![%xhtml-pres.module;[ <!ENTITY % xhtml-pres.mod PUBLIC "-//W3C//ELEMENTS XHTML Presentation 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-pres-1.mod" > %xhtml-pres.mod;]]> <!-- Image Module ...................................... --> <!ENTITY % xhtml-image.module "INCLUDE" > <![%xhtml-image.module;[ <!ENTITY % xhtml-image.mod PUBLIC "-//W3C//ELEMENTS XHTML Images 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-image-1.mod" > %xhtml-image.mod;]]> <!-- Tables Module ..................................... --> <!ENTITY % xhtml-table.module "INCLUDE" > <![%xhtml-table.module;[ <!ENTITY % xhtml-table.mod PUBLIC "-//W3C//ELEMENTS XHTML Basic Tables 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-basic-table-1.mod" > %xhtml-table.mod;]]> <!-- Forms Module ...................................... --> <!ENTITY % xhtml-form.module "INCLUDE" > <![%xhtml-form.module;[ <!ENTITY % xhtml-form.mod PUBLIC "-//W3C//ELEMENTS XHTML Basic Forms 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-basic-form-1.mod" > %xhtml-form.mod;]]> <!-- Scripting Module ................................. --> <!ENTITY % xhtml-script.module "INCLUDE" > <![%xhtml-script.module;[ <!ENTITY % xhtml-script.mod PUBLIC "-//W3C//ELEMENTS XHTML Scripting 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-script-1.mod" > %xhtml-script.mod;]]> <!-- Style Sheet Module ................................ --> <!ENTITY % xhtml-style.module "INCLUDE" > <![%xhtml-style.module;[ <!ENTITY % xhtml-style.mod PUBLIC "-//W3C//ELEMENTS XHTML Style Sheets 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-style-1.mod" > %xhtml-style.mod;]]> <!-- Link Module ....................................... --> <!ENTITY % xhtml-link.module "INCLUDE" > <![%xhtml-link.module;[ <!ENTITY % xhtml-link.mod PUBLIC "-//W3C//ELEMENTS XHTML Link Element 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-link-1.mod" > %xhtml-link.mod;]]> <!-- Metainformation Module ............................ --> <!ENTITY % xhtml-meta.module "INCLUDE" > <![%xhtml-meta.module;[ <!ENTITY % xhtml-meta.mod PUBLIC "-//W3C//ELEMENTS XHTML Metainformation 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-meta-1.mod" > %xhtml-meta.mod;]]> <!-- Base Module ....................................... --> <!ENTITY % xhtml-base.module "INCLUDE" > <![%xhtml-base.module;[ <!ENTITY % xhtml-base.mod PUBLIC "-//W3C//ELEMENTS XHTML Base Element 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-base-1.mod" > %xhtml-base.mod;]]> <!-- Param Module ...................................... --> <!ENTITY % xhtml-param.module "INCLUDE" > <![%xhtml-param.module;[ <!ENTITY % xhtml-param.mod PUBLIC "-//W3C//ELEMENTS XHTML Param Element 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-param-1.mod" > %xhtml-param.mod;]]> <!-- Object Module ..................................... --> <!ENTITY % xhtml-object.module "INCLUDE" > <![%xhtml-object.module;[ <!ENTITY % xhtml-object.mod PUBLIC "-//W3C//ELEMENTS XHTML Embedded Object 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-object-1.mod" > %xhtml-object.mod;]]> <!-- Structure Module (required) ....................... --> <!ENTITY % xhtml-struct.mod PUBLIC "-//W3C//ELEMENTS XHTML Document Structure 1.0//EN" "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-struct-1.mod" > %xhtml-struct.mod; <!-- end of XHTML-Print 1.0 DTD ............................................ --> <!-- ....................................................................... -->
Available for download at xhtml-print10-model-1.mod.
<!-- ....................................................................... --> <!-- XHTML-Print 1.0 Document Model Module ................................. --> <!-- file: xhtml-print10-model-1.mod This is XHTML-Print 1.0, a variant of XHTML Basic for printing. Copyright 1998-2003 W3C (MIT, ERCIM, Keio), All Rights Reserved. Revision: $Id: Overview.html,v 1.3 2018/10/09 13:29:20 denis Exp $ This DTD module is identified by the PUBLIC and SYSTEM identifiers: PUBLIC "-//W3C//ENTITIES XHTML-Print 1.0 Document Model 1.0//EN" SYSTEM "http://www.w3c.org/MarkUp/DTD/xhtml-print10-model-1.mod ....................................................................... --> <!-- XHTML-Print 1.0 Document Model This module describes the groupings of elements that make up common content models for XHTML-Print elements. --> <!-- Optional Elements in head ......................... --> <!ENTITY % HeadOpts.mix "( %script.qname; | %style.qname; | %meta.qname; | %link.qname; | %object.qname; )*" > <!-- Miscellaneous Elements ............................ --> <!ENTITY % Script.class "| %script.qname; | %noscript.qname;" > <!ENTITY % Misc.extra "" > <!ENTITY % Misc.class "%Script.class; %Misc.extra;" > <!-- Inline Elements ................................... --> <!ENTITY % InlStruct.class "%br.qname; | %span.qname;" > <!ENTITY % InlPhras.class "| %em.qname; | %strong.qname; | %dfn.qname; | %code.qname; | %samp.qname; | %kbd.qname; | %var.qname; | %cite.qname; | %abbr.qname; | %acronym.qname; | %q.qname;" > <!ENTITY % InlPres.class "| %tt.qname; | %i.qname; | %b.qname; | %big.qname; | %small.qname; | %sub.qname; | %sup.qname; " > <!ENTITY % I18n.class "" > <!ENTITY % Anchor.class "| %a.qname;" > <!ENTITY % InlSpecial.class "| %img.qname; | %object.qname;" > <!ENTITY % InlForm.class "| %input.qname; | %select.qname; | %textarea.qname; | %label.qname;" > <!ENTITY % Inline.extra "" > <!ENTITY % Inline.class "%InlStruct.class; %InlPhras.class; %InlPres.class; %Anchor.class; %InlSpecial.class; %InlForm.class; %Inline.extra;" > <!ENTITY % InlNoAnchor.class "%InlStruct.class; %InlPhras.class; %InlPres.class; %InlSpecial.class; %InlForm.class; %Inline.extra;" > <!ENTITY % InlNoAnchor.mix "%InlNoAnchor.class; %Misc.class;" > <!ENTITY % Inline.mix "%Inline.class; %Misc.class;" > <!-- Block Elements .................................... --> <!ENTITY % Heading.class "%h1.qname; | %h2.qname; | %h3.qname; | %h4.qname; | %h5.qname; | %h6.qname;" > <!ENTITY % List.class "%ul.qname; | %ol.qname; | %dl.qname;" > <!ENTITY % Table.class "| %table.qname;" > <!ENTITY % Form.class "| %form.qname;" > <!ENTITY % BlkStruct.class "%p.qname; | %div.qname;" > <!ENTITY % BlkPhras.class "| %pre.qname; | %blockquote.qname; | %address.qname;" > <!ENTITY % BlkPres.class "| %hr.qname;" > <!ENTITY % BlkSpecial.class "%Table.class; %Form.class;" > <!ENTITY % Block.extra "" > <!ENTITY % Block.class "%BlkStruct.class; %BlkPhras.class; %BlkPres.class; %BlkSpecial.class; %Block.extra;" > <!ENTITY % Block.mix "%Heading.class; | %List.class; | %Block.class; %Misc.class;" > <!-- All Content Elements .............................. --> <!ENTITY % FlowNoTable.mix "%Heading.class; | %List.class; | %BlkStruct.class; %BlkPhras.class; %BlkPres.class; %Form.class; %Block.extra; | %Inline.class; %Misc.class;" > <!ENTITY % Flow.mix "%Heading.class; | %List.class; | %Block.class; | %Inline.class; %Misc.class;" > <!-- end of xhtml-print10-model-1.mod -->