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: Fri, 30 Dec 2005 00:38:07 +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 1135903233 30133 80.91.229.2 (30 Dec 2005 00:40:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 30 Dec 2005 00:40:33 +0000 (UTC) Bcc: ilya Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Dec 30 01:40:30 2005 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Es8Jn-00044v-NQ for geh-help-gnu-emacs@m.gmane.org; Fri, 30 Dec 2005 01:40:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Es8LA-0005I4-EJ for geh-help-gnu-emacs@m.gmane.org; Thu, 29 Dec 2005 19:41:52 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!agate.berkeley.edu!ilya Original-Newsgroups: gnu.emacs.help Original-Lines: 59 Original-NNTP-Posting-Host: powdermilk.math.berkeley.edu Original-X-Trace: agate.berkeley.edu 1135903087 22666 169.229.140.13 (30 Dec 2005 00:38:07 GMT) Original-X-Complaints-To: usenet@agate.berkeley.edu Original-NNTP-Posting-Date: Fri, 30 Dec 2005 00:38:07 +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:136681 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:32300 Archived-At: [A complimentary Cc of this posting was sent to Eli Zaretskii ], who wrote in article : > > > > > > 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. > > > > ??? IIRC, now we are discussing not the printer, but the pipe... > > Anyway, consider these questions as concerning a pipe. > > If you send text to the pipe (using COPY or file I/O, like Emacs > does), you don't need to be bothered by these details (with the > exception of the EOLs, which I think must be CRLF). They are taken > care of by the machinery that takes over once the text winds up in the > pipe. Nonsense. I'm discussing the input format of this pipe, not the input format of the printer. > > (Yet another question is how to *force* a sequence of bytes to be > > recognized as TEXT [as opposed to MetaFile or > > RAW_PRINTER_COMMANDS].) > I think the COPY method cannot send RAW commands or EMF. I think to > send RAW and EMF one needs to use suitable functions of the Windows > API, not simple file I/O. I believe you are mistaken. > > According to the MS links you posted, I'm right; this pipes accepts > > RAW_PRINTER_COMMANDS. How it distinguishes it from "plain text" > > (which it supports "too", whatever it means) is not documented... > > I think it distinguishes given the API calls you use to send the > stuff. What we are discussing is a pipe. You use whatever API there is to write to file (do not know the names of Win* entry points). > > Only if you print ASCII only you can forget about encodings > I think this is also true if you use the encoding native to the > current locale, since the printer most probably supports that by > default. There is no "current locale". You probably mean "current codepage"; one needs to know the output the examples I posted (with chcp). Hope this helps, Ilya