attachment-0001
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">That's probably appropriate; Ira, let's normalize the PCL and PostScript descriptions to match the format of the current registrations:<div><br></div><div><pre style="word-wrap: break-word; white-space: pre-wrap; "> langPCL(3), -- PCL. Starting with PCL version 5,
-- HP-GL/2 is included as part of the
-- PCL language.
-- PCL and HP-GL/2 are registered
-- trademarks of Hewlett-Packard
-- Company.
</pre><div><span class="Apple-style-span" style="font-family: monospace; white-space: pre-wrap; "> langPS(6), -- PostScript (tm) Language</span></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre-wrap;"><span class="Apple-style-span" style="font-family: Geneva; white-space: normal; "><pre style="word-wrap: break-word; white-space: pre-wrap; "> -- Postscript - a trademark of Adobe
-- Systems Incorporated which may be
-- registered in certain jurisdictions
</pre><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre-wrap;">Looks like the existing langPDF and the new langPDF* definitions are already using the same conventions, so just the new PCL and PS descriptions need updating.</span></font></div><div><font class="Apple-style-span" face="monospace"><span class="Apple-style-span" style="white-space: pre-wrap;"><br></span></font></div></span></span></font></div><div><div>On May 3, 2010, at 1:49 PM, George Liu wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
<!-- Converted from text/plain format --><p><font size="2">> I think we are stuck treating these as languages/language families.<br>
<br>
I'd like to suggest change the description for langPCL3, langPCL3GUI, langPCL5e, langPCL5c. Rename "HP Printer Command Language xxx" to "Printer Command Language xxx"<br>
<br>
George<br>
<br>
-----Original Message-----<br>
From: Michael Sweet [<a href="mailto:msweet@apple.com">mailto:msweet@apple.com</a>]<br>
Sent: Mon 5/3/2010 11:15 AM<br>
To: George Liu<br>
Cc: Ira McDonald; <a href="mailto:pwg-announce@pwg.org">pwg-announce@pwg.org</a><br>
Subject: Re: [Pwg-Announce] Call for Review of langPDF/PS/PCL variants for IANAPrinter MIB (30 April 2010)<br>
<br>
On May 3, 2010, at 11:10 AM, George Liu wrote:<br>
> Has PCL-XL been left out intentionally?<br>
<br>
Yes, because it is already registered in RFC 3805:<br>
<br>
langPCLXL(47), -- Not in RFC 1759<br>
-- Printer Control Language. Extended<br>
-- language features for printing, and<br>
-- printer control.<br>
-- Tammy Ferguson (HP)<br>
-- and Binnur Al-Kazily (HP)<br>
-- Technical reference manual: None<br>
-- Hewlett-Packard Co.<br>
<br>
><br>
> There're PCL-XL 1.1, 2.0, 3.0, etc. Microsoft GPD based mini drivers is<br>
> able to generate PCL-XL.<br>
><br>
> George<br>
><br>
> -----Original Message-----<br>
> From: Ira McDonald [<a href="mailto:blueroofmusic@gmail.com">mailto:blueroofmusic@gmail.com</a>]<br>
> Sent: Monday, May 03, 2010 10:47 AM<br>
> To: George Liu; Ira McDonald<br>
> Cc: <a href="mailto:pwg-announce@pwg.org">pwg-announce@pwg.org</a>; Michael R Sweet<br>
> Subject: Re: [Pwg-Announce] Call for Review of langPDF/PS/PCL variants<br>
> for IANAPrinter MIB (30 April 2010)<br>
><br>
> Hi George,<br>
><br>
> Right - we're only talking about the graphics drawing aspect<br>
> of these printer languages.<br>
><br>
> The IEEE 1284 Device ID format only supports a list of<br>
> printer languages - it cannot be extended (interoperably)<br>
> for these other device-specific aspects.<br>
><br>
> The PWG cannot actually extend the capabilities keywords<br>
> or their syntax in the base IEEE 1284 spec.<br>
><br>
> So the scope of comments we're requesting is only to identify<br>
> any other common variants of PCL (for example) that should<br>
> be registered with IANA.<br>
><br>
> All of these are enumerated values in the single Printer MIB<br>
> integer object prtInterpreterLangFamily. Other objects such<br>
> as prtInterpreterLangLevel and prtInterpreterDescription can<br>
> be used by vendors to distinguish vendor-unique features.<br>
><br>
> Cheers,<br>
> - Ira<br>
><br>
> Ira McDonald (Musician / Software Architect)<br>
> Chair - Linux Foundation Open Printing WG<br>
> Co-Chair - TCG Hardcopy WG<br>
> IETF Designated Expert - IPP & Printer MIB<br>
> Blue Roof Music/High North Inc<br>
> <a href="http://sites.google.com/site/blueroofmusic">http://sites.google.com/site/blueroofmusic</a><br>
> <a href="http://sites.google.com/site/highnorthinc">http://sites.google.com/site/highnorthinc</a><br>
> <a href="mailto:blueroofmusic@gmail.com">mailto:blueroofmusic@gmail.com</a><br>
> winter:<br>
> 579 Park Place Saline, MI 48176<br>
> 734-944-0094<br>
> summer:<br>
> PO Box 221 Grand Marais, MI 49839<br>
> 906-494-2434<br>
><br>
><br>
><br>
> On Mon, May 3, 2010 at 12:50 PM, George Liu <<a href="mailto:george.liu@ricoh-tech.com">george.liu@ricoh-tech.com</a>><br>
> wrote:<br>
>> Unlike PDF, which is a document format, Postscript and PCL/PCL-XL are<br>
> PDL, which means printer-device specific.<br>
>><br>
>> A Tray-1 PCL command for HP printer means Bypass Tray, but means the<br>
> first tray under the printer engine for Ricoh printer.<br>
>> Also, in Postscript, there are many vendor specific Postscript<br>
> setpagedevice commands.<br>
>><br>
>> How will the new command set definition handles this case?<br>
>><br>
>> Are we only taking about the graphics drawing part not the device<br>
> control part?<br>
>> Or are we making "langPCL5e" only for a specific vender?<br>
>><br>
>> George<br>
>><br>
>><br>
<br>
________________________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
<br>
<br>
<br>
<br>
<br>
</font>
</p>
</div>
</blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div><div><br></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>