From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Printing from WindowXP version of emacs Date: Wed, 21 Dec 2005 06:42:25 +0200 Message-ID: References: <1134660719.186074.250590@z14g2000cwz.googlegroups.com> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1135140201 27885 80.91.229.2 (21 Dec 2005 04:43:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 21 Dec 2005 04:43:21 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 21 05:43:20 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EovoH-00086b-Tj for geh-help-gnu-emacs@m.gmane.org; Wed, 21 Dec 2005 05:42:42 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EovpD-0003KS-6p for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Dec 2005 23:43:39 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Eovov-0003JZ-En for help-gnu-emacs@gnu.org; Tue, 20 Dec 2005 23:43:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Eovot-0003J7-OE for help-gnu-emacs@gnu.org; Tue, 20 Dec 2005 23:43:21 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Eovot-0003J4-Jv for help-gnu-emacs@gnu.org; Tue, 20 Dec 2005 23:43:19 -0500 Original-Received: from [192.114.186.17] (helo=gandalf.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Eovs8-0001we-5I for help-gnu-emacs@gnu.org; Tue, 20 Dec 2005 23:46:40 -0500 Original-Received: from nitzan.inter.net.il (nitzan.inter.net.il [192.114.186.20]) by gandalf.inter.net.il (MOS 3.7.1-GA) with ESMTP id HIC45774; Wed, 21 Dec 2005 06:42:18 +0200 (IST) Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-12-229.inter.net.il [80.230.12.229]) by nitzan.inter.net.il (MOS 3.7.2-GA) with ESMTP id CGJ96283 (AUTH halo1); Wed, 21 Dec 2005 06:42:17 +0200 (IST) Original-To: help-gnu-emacs@gnu.org In-reply-to: (message from Ilya Zakharevich on Tue, 20 Dec 2005 22:40:55 +0000 (UTC)) 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:32126 Archived-At: > From: Ilya Zakharevich > Date: Tue, 20 Dec 2005 22:40:55 +0000 (UTC) > Bcc: ilya@gnu.org > Originator: ilya@powdermilk.math.berkeley.edu > > > > 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. Yes. If it's encoding you were asking about, then I don't know how this works in general for non-ASCII files on Windows. I guess it's similar to the way Windows uses the codepage that depends on the current language environment, but that's a guess. In any case, I don't think encoding is the issue in this thread, which is about how to print from Emacs. People who say it doesn't work for them cannot print even simple ASCII text, where encoding is not an issue. > > > 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? Because an application that prints doesn't care about these intimate details of the printer. It's the system software that actually processes the printed material (see the URL I posted here earlier) that needs to know that. > > 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.... Translated initially from plain text in whatever encoding we sent it, but the intermediate formats is something I don;t really know about, and neither should any application care. The system processes involved in the translation should know that. > > 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. Well, you are wrong, because you assume that LPT1 goes directly to the printer, but it's not. > > 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 figures, because I never printed Unicode. So I'm entitled to not knowing.