<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-2">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
color:black;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.stylwiadomociemail17
{font-family:Arial;
color:navy;}
span.stylwiadomociemail18
{font-family:Arial;
color:navy;}
span.StylWiadomociEmail19
{font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body bgcolor=white lang=PL link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>href="print://www.whatwg.org/specs/web-apps/current-work/"
is no good; it asks the browser to find the resource using the print protocol.
But the print protocol is for printing, not for finding resources; I imagine it
could be used for finding out some printer configuration parameters (similar to
the way printers with a network interface only can be configured) and to submit
documents for printing, nothing more.</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>How about </span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'><form </span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>action="print://host_name/printer_name/?</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>href=&quo;http://www.whatwg.org/specs/web-apps/current-work/&quo;&</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>palette=mono&</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>copies=3&</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>mode=draft,booklet&</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>stapled=top" method="post" ><input
type="submit" value="Print me"></form >? It feels
better to me. Of course, the arguments would be interpreted by the browser,
not by the printer, contrary to what the syntax suggests, but I think this
problem is much smaller and I can swallow it in spite of being a purist.</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>The idea that a fragment can address a
block element is quite interesting; in the old days a reference to #name would
usually correspond to an anchor with the same name—and you cannot embrace
a block-level element with an anchor. I think it is still common practice to
put the named anchor around the section header and not around the whole section,
which would require a division, not an anchor.</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>I did not want to say that printing is
obsolete; I wanted to say that asking the customer to print is obsolete. Sorry
for the misunderstanding. Your site should not lose functionality because your
customer does not have a printer.</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>Cheers</span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt'>Chris</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=2 color=black
face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:Tahoma;
color:windowtext'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Sander [mailto:html5@zoid.nl]
<br>
<b><span style='font-weight:bold'>Sent:</span></b> Saturday, July 28, 2007 7:43
PM<br>
<b><span style='font-weight:bold'>To:</span></b> Křištof Želechovs</span></font><font
size=2 color=black face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
color:windowtext'>ki; whatwg@whatwg.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [Whatwg] Request for
HTML-only print link</span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'>Křištof Želechovski
schreef: </span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy'>The acronym URL expands to "Uniform Resource *<b><span
style='font-weight:bold'>Locator</span></b>*”. The string
“print:#” does not match this spec: it is not a locator, it is a
processing instruction. BTW, the full form of the local URL
“#” can be viewed as “html:#” (whether it is allowed by
the URL standard or not) which means that you need a URL to access the resource
you want to print; prefixing it with “print:” would result in a
double URL scheme, which is unacceptable. Therefore it is better to use a
special target, if any.</span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'>Would
href="print://www.whatwg.org/specs/web-apps/current-work/" have been
better then?<br>
<br>
<br>
</span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy'>Moreover, as has already been noted, the http URL scheme does not
allow specifying document fragments except in CGI arguments, which is an
absolutely server-side unspecified thing.</span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'>Well, you can of course
link to a specified id within a document (<a
href="http://www.whatwg.org/specs/web-apps/current-work/#media12">http://www.whatwg.org/specs/web-apps/current-work/#media12</a>).
Isn't that a fragment, as in CSS (#media12 { })?<br>
<br>
<br>
</span></font></p>
<p class=MsoNormal style='margin-left:35.4pt'><font size=2 color=navy
face=Arial><span lang=EN-US style='font-size:10.0pt;font-family:Arial;
color:navy'>And the details like paper sort, size, texture and stationery,
print mode and quality, the order of pages and many other things I do not know
about, if they are essential, still have to be explained verbally to the
viewer, so the gain is minimal. And if you tell me such things are never
essential, I shall respond that printing is an obsolete practice that is
harmful to the environment and should be deprecated and not recommended, except
for the cases were a written signature is needed, which is hopefully becoming
obsolete as well.</span></font></p>
<p class=MsoNormal style='margin-right:0cm;margin-bottom:12.0pt;margin-left:
35.4pt'><font size=3 color=black face="Times New Roman"><span style='font-size:
12.0pt'>These are essential for printing and should be handled the way it is
handled now: through a print prompt. In a <a href="mailto:-link">mailto:-link</a>
you don't provide from which address to send it from, HTML-mail, plain text or
both either.<br>
<br>
My request was for a way to have in-page print links that don't require
client-side scripting, an HTML-alternative to <a href="javascript:print()">javascript:print()</a>;<br>
<br>
I don't agree with you that printing is an obsolete practice. Not yet at least,
as people not all have mobile access to the internet or in cases like the
example you came up with yourself.<br>
<br>
cheers,<br>
Sander<br>
<br>
</span></font></p>
</div>
</body>
</html>