From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.help Subject: Re: Printing from WindowXP version of emacs Date: Thu, 22 Dec 2005 09:02:28 +0100 Message-ID: <43AA5D94.8000602@student.lu.se> References: <1134660719.186074.250590@z14g2000cwz.googlegroups.com> <43A8842E.5090204@student.lu.se> <43A908F9.1070304@student.lu.se> <43A9B6D5.9010205@student.lu.se> <43A9DBB8.3010204@student.lu.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1135238642 25927 80.91.229.2 (22 Dec 2005 08:04:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 22 Dec 2005 08:04:02 +0000 (UTC) Cc: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Dec 22 09:04:00 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 1EpLQY-0000UB-Id for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Dec 2005 09:03:54 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EpLRW-0001qT-HU for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Dec 2005 03:04:54 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EpLQG-0001pI-64 for help-gnu-emacs@gnu.org; Thu, 22 Dec 2005 03:03:36 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EpLQE-0001og-MF for help-gnu-emacs@gnu.org; Thu, 22 Dec 2005 03:03:35 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EpLQE-0001oL-61 for help-gnu-emacs@gnu.org; Thu, 22 Dec 2005 03:03:34 -0500 Original-Received: from [81.228.8.164] (helo=pne-smtpout2-sn2.hy.skanova.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EpLPH-0007AE-IP; Thu, 22 Dec 2005 03:02:35 -0500 Original-Received: from [192.168.123.121] (83.249.218.244) by pne-smtpout2-sn2.hy.skanova.net (7.2.069.1) id 43A92C170004E15A; Thu, 22 Dec 2005 09:02:29 +0100 User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en Original-To: Eli Zaretskii In-Reply-To: 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:32159 Archived-At: Eli Zaretskii wrote: >Well, good luck, then Getting _all_ the information will take an >enormous amount of time. > > Maybe you did misunderstand me? >>> >>> >>No. I mean ASCII. Please look at the description of how the Text type is >>handled. That is the description I gave above where the GDI converts to >>EMF. In this process only ASCII is accepted according to the manuals at MS. >> >> > >No, it accepts 8-bit text. > > Sorry, you are right. I misread that part. It only says "This data type is based on the ANSI standard, and if an application that has another character set creates text data it does not print. This often presents a problem in the extended character range, represented by values above 127.". It does not say that it does not handle the characters above 127 at all - which I believed. > > >>>Here, for example: >>> >>> >>> >>> >>Sorry, I think you did not send that. >> >> > >Oops. > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/graphics/hh/graphics/provider_b941f8a9-ddb3-47ca-afa2-d06c6de2ce74.xml.asp > > Thanks. This is what I have been reading too. I am however not sure that this text means that "copy" for example are handled this way. The text describes two steps where the spooler is used. In the first step the spooler sends the job to GDI for conversion and get it back from GDI. In the second step the spooler sends the data to the printer. Could it not be that "copy" goes directly to the second step? However that partly seems to be unimportant now, when I believe that we agree that there probably is no way to convert PostScript during the first step. See below. The "copy" in my case fails for most printers I have tried before. One possibility is that "copy" goes directly to the second step. I am still looking for information about that. > > >>>There's no need to convert PostScript to EMF, since a PostScript >>>printer will be happy accepting the PostScript program as plain text. >>> >>> >>> >>> >>What do you mean? How can you assume that it is a PostScript printer? >> >> > >If it's not a PostScript printer, you cannot print PostScript to it. > > In the beginning of this long thread you said that it was a bad advice to tell new users to print from Emacs through their web browsers using htmlize-view.el. This provides colored printing. The printer of course must be a color printer, but it does not have to support PostScript. If you want to print in colors from within Emacs then the only option is that it produces PostScript. Now I have assumed that we were looking for a way to get this printed even if the printer itself does not understand PostScript. One way to do this is using an external program like GhostScript. I said I wanted to avoid using an external program (except for the web browser which is already there and is already used by Emacs through browse-url-of-file for example). I know of course there is a more basic problem: I can not even get black and white printing to work the way you have suggested (but there still might be one possibility left which I have not tried yet). However I keep both these problems (printing at all and printing PostScript) in mind while looking at the documentation. I am sorry if I have not been clear on this and you therefore did misunderstand me. > > >>And if it where, how can you assume that it is in a state where it >>accepts PostScript? >> >> > >The printer enters the PostScript state automatically when it sees the >PostScript preamble. > > I am sorry but I have seen printers where this does not happen.