From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: stromme@mi.uib.no (Stein Arild =?utf-8?Q?Str=C3=B8mme?=) Newsgroups: gmane.emacs.help Subject: Re: postscript printing from emacs Date: Fri, 23 Mar 2007 22:17:15 +0100 Message-ID: References: <243C6E55-C719-4B05-9290-C5C5A8472B71@Web.DE> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1174685921 14018 80.91.229.12 (23 Mar 2007 21:38:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 23 Mar 2007 21:38:41 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Mar 23 22:38:34 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HUrSt-0005kz-Nx for geh-help-gnu-emacs@m.gmane.org; Fri, 23 Mar 2007 22:38:27 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HUrUp-00013n-Vi for geh-help-gnu-emacs@m.gmane.org; Fri, 23 Mar 2007 16:40:28 -0500 Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin) Cancel-Lock: sha1:D2S+a5L+4n5Gl/G1suZLGxciUSE= Original-NNTP-Posting-Host: 138.84-49-153.nextgentel.com X-Original-NNTP-Posting-Host: 138.84-49-153.nextgentel.com Original-X-Trace: news.broadpark.no 1174684634 84.49.153.138 (23 Mar 2007 22:17:14 +0100) Original-Lines: 77 Original-Path: shelby.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!newspump.sol.net!161.49.252.4.MISMATCH!sxnews1.qg.com!nntp.gblx.net!nntp3.phx1!news.broadpark.no!not-for-mail Original-Xref: shelby.stanford.edu gnu.emacs.help:146542 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:42146 Archived-At: Peter Dyballa writes: > Am 23.03.2007 um 16:41 schrieb Stein Arild Strømme: > >> I also find it suspicious that Preview.app in OS X cannot display >> the file correctly (it does with other postscript files). > > I reported this error before. Ps-print is pretty useless, in any case > in Mac OS X. Besides this it only supports one or two encodings: US 7- > bit ASCII and ISO 8859-1. I should have stated more about my situation: I'm running Linux in a centralized university environment. Printing is via a cups server which in turn talks to a Windows print server common for the whole university. My mention of Mac OS X is peripheral to the issue, it was just a test naively trying to narrow down the search for the culprit. Involving a Mac is no solution in any case. > From the failure with Preview you can deduce that the Mac OS X and > CUPS related mechanisms to prepare the PS output for printing are the > reason that your printer reports a failure. It's nothing but non- > sense that gets into the printer queue. (You can halt the queue and > inspect what's in it!) Unfortunately, I have absolutely no control of the queue at all. >> So what is it about the ps-print-generated postscript files fools the >> printer and Preview.app, that's the question. > > I presume it's like MSIE "optimised" web sites: only Ghostscript can > convert and only Ghostscript can display. So the function family > should better, before release of GNU Emacs 22.1, be renamed gs-print. OK, but both a2ps and enscript *do* work, in so far as the buffers get printed, and even correctly, if encoded in 8859-1. ps-print gives nothing, even on the simplest of buffers. >> | Use htmlize to convert the buffer or region content to UTF-8 encoded >> | HTML, view it in a capable browser, print from the browser. >> >> That is tongue-in-cheek, surely? > > No. It's a proven way. And it's the only way a few members on this > list could find. OK, I have no doubts that it works, but it is too cumbersome. I suppose it is a luxury problem for me, I don't *really* need utf-8 (I can get by with 8859-1), I simply want to try to migrate to utf-8. What you are saying below about postscript and utf-8 gives me second thoughts indeed. > The problem with PostScript is that it usually only supports 8 bit > encodings. So you can't print Unicode. You can try to find a CID > keyed PostScript font and with some effort you can print CJK. No such > font is available for free or public domain. TrueType and OpenType > fonts have better Unicode support. Modern PostScript can use such > TrueType fonts, which are quite often free and acceptable quality. > But I have no idea how to create a mapping from an UTF-8 encoded text > to a Unicode encoded font in PostScript. It seems that I have two distinct problems: 1) ps-print does not work at all, even for straight ascii, and 2) nothing simpler than your solution works for utf-8 encoded files. I'd still like to understand 1) better. > > -- > Greetings > > Pete Thanks for informative posts! SA