From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David De La Harpe Golden Newsgroups: gmane.emacs.devel Subject: Re: Printing Date: Thu, 02 Apr 2009 01:09:56 +0100 Message-ID: <49D40254.1000401@harpegolden.net> References: jwveiwcbg87.fsf-monnier+emacs@gnu.org <49D3A2BA.5070908@gmx.de> <49D3B88A.4000809@harpegolden.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1238631019 29209 80.91.229.12 (2 Apr 2009 00:10:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 2 Apr 2009 00:10:19 +0000 (UTC) To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 02 02:11:37 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 1LpAWs-0006h5-7Y for ged-emacs-devel@m.gmane.org; Thu, 02 Apr 2009 02:11:34 +0200 Original-Received: from localhost ([127.0.0.1]:54786 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LpAVU-0004Wu-BN for ged-emacs-devel@m.gmane.org; Wed, 01 Apr 2009 20:10:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LpAVQ-0004Wk-0p for emacs-devel@gnu.org; Wed, 01 Apr 2009 20:10:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LpAVL-0004WP-9w for emacs-devel@gnu.org; Wed, 01 Apr 2009 20:10:03 -0400 Original-Received: from [199.232.76.173] (port=42946 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LpAVL-0004WM-5c for emacs-devel@gnu.org; Wed, 01 Apr 2009 20:09:59 -0400 Original-Received: from harpegolden.net ([65.99.215.13]:43182) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LpAVK-0003XT-LN for emacs-devel@gnu.org; Wed, 01 Apr 2009 20:09:58 -0400 Original-Received: from [87.198.54.195] (87-198-54-195.ptr.magnet.ie [87.198.54.195]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "David De La Harpe Golden", Issuer "David De La Harpe Golden Personal CA rev 3" (verified OK)) by harpegolden.net (Postfix) with ESMTP id E2088804E for ; Thu, 2 Apr 2009 01:09:57 +0100 (IST) User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) In-Reply-To: <49D3B88A.4000809@harpegolden.net> X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:109977 Archived-At: David De La Harpe Golden wrote: > Since emacs is currently a "toolkit unto itself" for the most part, as > Stefan has already pointed out, it kind of makes sense for it to > generate its own postscript. Though maybe just saving out and > "enscript"ing text files might currently work about as well... > Hey, just found enscript homepage itself now recommends the "paps" (giggle) command line tool for postscript printing of unicode text files. http://paps.sourceforge.net/ See scans of me printing emacs hello with emacs' ps-print and through paps - spot the difference: http://harpegolden.net/misc/emacs-paps/emacs-hello-psprint.jpg http://harpegolden.net/misc/emacs-paps/emacs-hello-paps.jpg Yes, the paps output isn't _perfect_ (but all I did was saved HELLO as utf-8 and fed it to paps), but it's already far, far better - seeing as it supports non-latin1 stuff at all and all. Lennart Borgman wrote: > Of course such work should be coordinated with what is needed on > GNU/Linux. (Something for Google Summer of Code?) Turns out paps also apparently supports pango's small text formatting markup language with the --markup flag: http://library.gnome.org/devel/pango/unstable/PangoMarkupFormat.html - if emacs could be persuaded to output such marked-up utf-8 text to be filtered through paps, that might be a *very* short route to semidecent printing, at least on GNU/linux and similar platforms. Of course paps is using pango for its rendering - I guess Stefan's aforementioned "real gtk" emacs port is a long-term solution for free platforms, using the whole gtk+/cairo/pango stack (I believe libm17n and libotf are also involved as a possible pango "shaper", but don't really understand the whole area myself at present...) for a unified vector-based screen GUI and print layer. Whole lot of work though. But making emacs output utf-8 text marked up with pango markup language (for replicating font-locking for quasi-wysiwig) to be fed through paps might be more at GSoC project scale ? Might even be too small...