<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Křištof Želechovski schreef:
<blockquote cite="mid:001001c7d14f$e4faed20$4d01010a@IBM42F76C011DF"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<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>
<div class="Section1">
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">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 color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">How about </span></font></p>
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US"><form </span></font></p>
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">action="print://host_name/printer_name/?</span></font></p>
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">href=&quo;<a class="moz-txt-link-freetext" href="http://www.whatwg.org/specs/web-apps/current-work/&quo;&">http://www.whatwg.org/specs/web-apps/current-work/&quo;&</a>;</span></font></p>
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">palette=mono&</span></font></p>
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">copies=3&</span></font></p>
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">mode=draft,booklet&</span></font></p>
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">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>
</div>
</blockquote>
<font face="Helvetica, Arial, sans-serif" size="-1">The idea was not to
dictate from HTML how the printer should behave (number of copies,
color, etc.). This should be up to the visitor, who can manage that in
the print prompt. The request was about an alternative to
<a class="moz-txt-link-freetext" href="javascript:print()">javascript:print()</a> where there would be no need for client-side
scripting.<br>
I probably gave this discussion a wrong turn by saying that a
print-pseudo-protocol would perhaps be a good solution. I guess i
should not have done so as my knowledge about such things is minimal.</font><br>
<br>
<blockquote cite="mid:001001c7d14f$e4faed20$4d01010a@IBM42F76C011DF"
type="cite">
<div class="Section1">
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">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>
</div>
</blockquote>
<font face="Helvetica, Arial, sans-serif" size="-1">I wasn't talking
about an anchor, but about an id, which can be any kind of element,
with any kind of content. This is how bookmarks work nowadays and it is
quite similar to CSS id-selectors. As this "fragment printing" would be
new I don't see any backwards compatibility issues.</font><br>
<br>
<blockquote cite="mid:001001c7d14f$e4faed20$4d01010a@IBM42F76C011DF"
type="cite">
<div class="Section1">
<p class="MsoNormal"><font color="black" face="Times New Roman"
size="3"><span style="font-size: 12pt;" lang="EN-US">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>
</div>
</blockquote>
<font face="Helvetica, Arial, sans-serif" size="-1">It would be the
same as it is now. Even with unobtrusive JavaScript I can not check
whether a printer is installed and connected.<br>
<br>
cheers,<br>
Sander</font><br>
</body>
</html>