From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Windows Printing Date: Sat, 20 May 2006 00:59:56 +0200 Message-ID: <446E4DEC.8080309@student.lu.se> References: <446CF318.2000703@student.lu.se> <446DC3BD.1010706@student.lu.se> <446E0F3F.9060100@student.lu.se> <446E27C8.2050906@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 1148079620 12052 80.91.229.2 (19 May 2006 23:00:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 19 May 2006 23:00:20 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 20 01:00:19 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FhDx8-0007E0-OW for ged-emacs-devel@m.gmane.org; Sat, 20 May 2006 01:00:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FhDx8-0007A9-5q for ged-emacs-devel@m.gmane.org; Fri, 19 May 2006 19:00:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FhDwv-00079L-Jq for emacs-devel@gnu.org; Fri, 19 May 2006 19:00:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FhDwu-00077n-2P for emacs-devel@gnu.org; Fri, 19 May 2006 19:00:01 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FhDwt-00077j-Qb for emacs-devel@gnu.org; Fri, 19 May 2006 18:59:59 -0400 Original-Received: from [81.228.8.83] (helo=pne-smtpout1-sn2.hy.skanova.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FhE0H-0005Dr-Qe; Fri, 19 May 2006 19:03:30 -0400 Original-Received: from [192.168.123.121] (83.249.218.244) by pne-smtpout1-sn2.hy.skanova.net (7.2.072.1) id 446DCC030001708F; Sat, 20 May 2006 00:59:57 +0200 User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) Original-To: Eli Zaretskii In-Reply-To: X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:54843 Archived-At: Eli Zaretskii wrote: >>> That's not what I said. I said that I didn't see anything in the docs >>> that specifically _precludes_ us from doing what Emacs does. >>> >>> >> No, the printer drivers of course have to do something like that. But >> they are printer specific. If you want to print to any printer on MS >> Windows without having to care about what type of printer it is then you >> must use the GDI interface instead as far as I understands it. On this >> higher level the printer obscurities are hidden. >> > > Sorry, you are repeating some of the nonsense written in the original > thread by someone who confessed that he knew almost nothing about how > printing works on Windows. AFAICS, there's nothing in the Microsoft > documentation that backs up what he wrote. Plain text output to a > printer has nothing to do with raw byte streams sent by the printer > drivers. > I admit I am simplyfying things. I should have thought before writing. The printer drivers goes in on another level. However that has not very much to do with the main argument. There are some support in MS Windows for the way Emacs prints, but it is not a full support for all printers and all kind of printing as far as I understands it. You have to use GDI for that. Or do you think differently? (Actually I do not believe you do, but I want it to be clear in the archives if someone wants to work on this.) > ps-print solves this in a different way: it talks PostScript to a > special printer driver, and that driver then takes care of converting > to GDI. Font selection is also different, take a look at ps-mule.el > and ps-bdf.el. > Yes I know. I just thought that the logic for taking care of pages etc is there. > Yes. In fact, the Windows-specific display code doesn't even see the > whole buffer, only its part represented in the glyph matrices created > by the higher-level platform-independent redisplay engine. > Thanks. Would it be hard to let the display code see the whole buffer? I mean for printing.