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: Printing Date: Wed, 1 Apr 2009 23:19:57 +0200 Message-ID: References: <49D3A2BA.5070908@gmx.de> <49D3B88A.4000809@harpegolden.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1238620836 1976 80.91.229.12 (1 Apr 2009 21:20:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 Apr 2009 21:20:36 +0000 (UTC) Cc: grischka , monnier@iro.umontreal.ca, emacs-devel@gnu.org To: David De La Harpe Golden Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 01 23:21:53 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Lp7sK-0001oG-Tf for ged-emacs-devel@m.gmane.org; Wed, 01 Apr 2009 23:21:33 +0200 Original-Received: from localhost ([127.0.0.1]:54138 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lp7qx-00048n-2p for ged-emacs-devel@m.gmane.org; Wed, 01 Apr 2009 17:20:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lp7qt-00048d-BE for emacs-devel@gnu.org; Wed, 01 Apr 2009 17:20:03 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lp7qo-00048H-SE for emacs-devel@gnu.org; Wed, 01 Apr 2009 17:20:03 -0400 Original-Received: from [199.232.76.173] (port=44522 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lp7qo-00048E-Md for emacs-devel@gnu.org; Wed, 01 Apr 2009 17:19:58 -0400 Original-Received: from mail-bw0-f167.google.com ([209.85.218.167]:48589) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lp7qo-0007FJ-8W for emacs-devel@gnu.org; Wed, 01 Apr 2009 17:19:58 -0400 Original-Received: by bwz11 with SMTP id 11so221371bwz.42 for ; Wed, 01 Apr 2009 14:19:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=j1AHhfClAnKvtNbE+m2B/MYLA8yLW0zRlHu6VbfIcQM=; b=rZC0REG0+EKSeCWuuEGMXpFxEqdkfcKrp3Z1DG7J2S0ePYmAaQONOD8Eue7VAevVLq H9yAo1SQlhW9YwUtlf7dskodXfZxwQ2RhlwpBm8xCbyvSnGBBBfr6q0PuxqJ8gD4ApJL MLMVWB9HMBaL6uqKUBz4IDNlr1a2t8IRMZKnE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ITfVxCKBIDyf4NaCJ738gMsT4jSUOJjdPB6Akrd0Pm5+Gfa2KlTb4HvoFommSycHCH aroFFJW2mVqP+EmXy2hJIvop8pxteVPR2+GSAK1TB0Lzg6ALcRNf3we8VewjdYNbY0TA pnNfQjnAuTVz9Y5GNnfR0MK+xTMG64WPYfPe8= Original-Received: by 10.223.116.72 with SMTP id l8mr6602231faq.33.1238620797185; Wed, 01 Apr 2009 14:19:57 -0700 (PDT) In-Reply-To: <49D3B88A.4000809@harpegolden.net> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:109974 Archived-At: On Wed, Apr 1, 2009 at 8:55 PM, David De La Harpe Golden wrote: > On windows, the toolkit uses win32 drawing commands on a printer device > context [2] instead of postscript drawing on a postscript document. > Typically they might internally rasterise to a high-res DIB (.bmp) then > printed with basically just one such win32 drawing command consisting of > "draw this enormous .bmp please". As Jason pointed out (and I guess you mean) printing using the ms w32 toolkit is done using GDI API:s. It is like outputting things to the screen. Therefore printing on w32 is normally very simple to implement. However Emacs does its own output to the screen and does not use GDI API:s on that level. Whether the output is a DIB file or a PostScript dito depends on the printer used. (The printer driver that is part of w32 or installed with the printer decides that.) Like someone (Jason?) said it may be possible to use the code in ps-*.el to implement calls to the w32 GDI API:s (some C code is of course needed to for the API calls). If someone understands the structure of both PostScript and the w32 GDI API:s involved sufficiently well it would perhaps be rather easy. Of course such work should be coordinated with what is needed on GNU/Linux. (Something for Google Summer of Code?)