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: Tue, 20 Dec 2005 23:22:38 +0100 Message-ID: <43A8842E.5090204@student.lu.se> References: <1134660719.186074.250590@z14g2000cwz.googlegroups.com> 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 1135117558 1111 80.91.229.2 (20 Dec 2005 22:25:58 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 20 Dec 2005 22:25:58 +0000 (UTC) Cc: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Dec 20 23:25:49 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Eopt5-0005pD-RU for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Dec 2005 23:23:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Eopu0-0000Et-KN for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Dec 2005 17:24:12 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Eoptg-0000Cr-UE for help-gnu-emacs@gnu.org; Tue, 20 Dec 2005 17:23:53 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Eoptg-0000CX-EG for help-gnu-emacs@gnu.org; Tue, 20 Dec 2005 17:23:52 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Eoptg-0000CU-4f for help-gnu-emacs@gnu.org; Tue, 20 Dec 2005 17:23:52 -0500 Original-Received: from [81.228.11.98] (helo=pne-smtpout1-sn1.fre.skanova.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Eopwe-0001SV-QP; Tue, 20 Dec 2005 17:26:57 -0500 Original-Received: from [192.168.123.121] (83.249.218.244) by pne-smtpout1-sn1.fre.skanova.net (7.2.069.1) id 43A817AA0002901D; Tue, 20 Dec 2005 23:22:39 +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:32119 Archived-At: Eli Zaretskii wrote: >Similar things happen on MS-Windows; see this page for a more detailed >description: > > http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp > > Seems like a good starting point. I have been reading a bit under "Welcome - Part II Desktop Management - Ch 11 Enabling Printing and Faxing". Under this you find for example "Printing Concepts - Printing Job Formats". To me the usable formats there seems to be EMF and Text. The Raw datatypes seems to be for those processes that knows about the printer. When I print from any application in Windows I never care about the actual printer, just if it is a color printer. Of course I want it to work this way in Emacs too. The Text format seems to be for black and white printing using only ANSI characters. Then it seems to me that we want to use EMF. The problem is how to do this then. One solution I was thinking of before when I decided to make the prefather of htmlize-view.el was creating EMF just like printing.el produces PostScript today. This seems however to be a lot of work and especially troublesome if printing.el changes so I abondoned that idea. Including code from GhostScript (if there is some GPL variant of that today, I am not sure of that actually) or something similar in Emacs seems much better then. Should not that code do just the conversion above from PostScript to EMF (in principle)? Or am I misunderstanding something in the structure of the Windows printing interface here? >When, on Windows, Emacs writes to a port such as PRN or to a share >name such as \\server\printer, as if they were normal files, this >creates a printer job that passes through a series of processors (see >the URL above) and only in the end is sent through the wire to the >physical device. > > Could you give a more specific description of where to find this? I can only find something about using those ports for local printing.