From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ilya Zakharevich Newsgroups: gmane.emacs.help Subject: Re: Printing from WindowXP version of emacs Date: Tue, 20 Dec 2005 22:40:55 +0000 (UTC) Organization: U.C. Berkeley Math. Department. Message-ID: References: <1134660719.186074.250590@z14g2000cwz.googlegroups.com> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1135118894 5119 80.91.229.2 (20 Dec 2005 22:48:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 20 Dec 2005 22:48:14 +0000 (UTC) Bcc: ilya Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Dec 20 23:48:13 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EoqDe-0005Ay-Jk for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Dec 2005 23:44:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EoqEZ-0003D9-8X for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Dec 2005 17:45:27 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!newsfeed.news.ucla.edu!newsfeed.berkeley.edu!ucberkeley!agate.berkeley.edu!ilya Original-Newsgroups: gnu.emacs.help Original-Lines: 67 Original-NNTP-Posting-Host: powdermilk.math.berkeley.edu Original-X-Trace: agate.berkeley.edu 1135118455 18090 169.229.140.13 (20 Dec 2005 22:40:55 GMT) Original-X-Complaints-To: usenet@agate.berkeley.edu Original-NNTP-Posting-Date: Tue, 20 Dec 2005 22:40:55 +0000 (UTC) User-Agent: trn [how to get a version via %-escapes???] with a custom header X-How-To-Reach-Me: The From: address is valid X-How-To-Disable-Cc: Put in the headers the line: Mail-Copies-To: never Originator: ilya@powdermilk.math.berkeley.edu Original-Xref: shelby.stanford.edu gnu.emacs.help:136502 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:32121 Archived-At: [A complimentary Cc of this posting was sent to Eli Zaretskii ], who wrote in article : > > In what encoding is this 'a' printed? > > I don't understand the question: the printer is a display device, so > it produces a glyph, not an encoding. Given different encodings, the same sequence of bytes should produce different sequence of glyphs. > > Are long lines wrapped or lost? What is the page size in lines of > > input? Should line be terminated by CRLF, CR, or LF? > > Can't say, it depends on the printer's setup, its driver software, and > any other software that sits in between the application that sent the > text and the wire. I'm puzzled again: if you can't say, how can you claim you know how to print? > Then we were talking about two different things. The ``named pipes'' > which Windows users are advised to use in conjunction with Emacs > printing are not direct ways to talk to the printer via the wire, the > traffic to those ``pipes'' is intercepted by spooling software, > translated any number of times as the printer requires The key question is: translated from *what format*, and you seem to avoid this question again and again.... > > and contemporary printers do not have "DOS compatibility" > > mode, when you can dump arbitrary ASCII text to them, and they will > > print in Courier. > > That's true. But I wasn't talking about such a mode. On a modern > Windows system, when you write text to LPT1, the text is captured by > system software and processed as appropriate (which indeed converts it > into commands, but that's something an application is not aware of). My expectation is that you are wrong. I expect that the following is true on "modern Win* systems" too: you can print an arbitrary stuff "to a file" (as opposed "to a printer"); then sending this file (with printer commands, or MetaFile info - I do not know) to LPT1 will produce not the text representation of bytes in the file, but the initial (graphical) print job. > I don't have experience with Unicode printing, so I can only > speculate. I would think that Unicode printing requires to tell the > printer to select an appropriate font, like with terminals. See above. One *must* know this before one is able to print. > > > That funny pipe you invented is normally a symbolic name whose I/O > > > is intercepted by such an interface software and converted into > > > signals that run on the wire; then the issue of uni- vs > > > bi-directional communications is relevant. > > > > True; but you need a way to configure this interface software. At > > least a way to switch it to Unicode input. > > Ideally, the OS would do this itself, when it sees UTF-8, but I don't > know if this is how it works. There is no way to reliably distinguish UTF-8 from any other byte stream. Hope this helps, Ilya