From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter Dyballa Newsgroups: gmane.emacs.help Subject: Re: ps-print question Date: Mon, 3 Jan 2011 14:15:58 +0100 Message-ID: <8A0622C4-69A5-4BC0-861F-66CE369EBF68@Web.DE> References: <9E47A63C-3337-4CF9-AC0E-C91082557375@arqux.com> <97BBE33A-D586-4CFA-BE9C-96C6ABBD22A3@Web.DE> <63E6A495-DFCF-4791-B39A-9B9893228275@Freenet.DE> <47A0F9E5-9581-4484-99DA-71B1D2E54DF2@arqux.com> <5B72ACF7-0ACA-4DC9-A49F-98AA1DF0B504@arqux.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1294060605 7932 80.91.229.12 (3 Jan 2011 13:16:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 3 Jan 2011 13:16:45 +0000 (UTC) Cc: GNU Emacs List To: David Penton Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jan 03 14:16:41 2011 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.69) (envelope-from ) id 1PZkH9-00028s-Vd for geh-help-gnu-emacs@m.gmane.org; Mon, 03 Jan 2011 14:16:40 +0100 Original-Received: from localhost ([127.0.0.1]:37309 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PZkH8-0004xC-TS for geh-help-gnu-emacs@m.gmane.org; Mon, 03 Jan 2011 08:16:38 -0500 Original-Received: from [140.186.70.92] (port=47912 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PZkGb-0004uo-1p for help-gnu-emacs@gnu.org; Mon, 03 Jan 2011 08:16:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PZkGZ-00010e-O3 for help-gnu-emacs@gnu.org; Mon, 03 Jan 2011 08:16:04 -0500 Original-Received: from fmmailgate01.web.de ([217.72.192.221]:52839) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PZkGZ-00010B-BB for help-gnu-emacs@gnu.org; Mon, 03 Jan 2011 08:16:03 -0500 Original-Received: from smtp05.web.de ( [172.20.4.166]) by fmmailgate01.web.de (Postfix) with ESMTP id A880F184C0F37; Mon, 3 Jan 2011 14:16:02 +0100 (CET) Original-Received: from [91.35.221.46] (helo=[192.168.1.2]) by smtp05.web.de with asmtp (WEB.DE 4.110 #2) id 1PZkGY-0002uS-00; Mon, 03 Jan 2011 14:16:02 +0100 In-Reply-To: <5B72ACF7-0ACA-4DC9-A49F-98AA1DF0B504@arqux.com> X-Mailer: Apple Mail (2.936) X-Sender: Peter_Dyballa@web.de X-Provags-ID: V01U2FsdGVkX18o9gHNRDK5h50e/E5/GWJVcaKO1PvZuG5JSAB0 twjSMLB7FeD/Mba5EaeV0+IURgImfHmpMzUQzCk2kJDWMZMZJz vRnAmmhH2cDP8Oq3XlQA== X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4-2.6 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:78102 Archived-At: Am 03.01.2011 um 03:19 schrieb David Penton: > The content of the pdf file is not directly relevant to the problem, =20= > nor is ps2pdfwr. The problem arises before conversion to pdf. You don't seem to print (send to the printer, queue into the printer =20 queue) the PS file, so the PDF file *is* the problem. And there, by =20 means of a Character Mapping table (the CMap table) the ` (GRAVE =20 ACCENT, U+0060) becomes =91 (LEFT SINGLE QUOTATION MARK, U+2018). > > In my earlier posts I pointed out that the backquote IS preserved in =20= > the simple little postscript example that I supplied. Why is not possible to print the PS file directly? > It is preserved in interactive ghostscript, and also by my modified =20= > ps2pdfwr script so that the backquote appears properly in the =20 > resulting pdf file. Please, tell me which Ghostscript version you are using and what the =20 command line is! I'd like to see this result myself. With the output =20 of ps-print, if you refer to this. If you mean your own PS test file, =20= then I understand that omitting -dSAFER allows gs some reasonable doing. > > However, postscript generated by ps-print does NOT preserve the =20 > backquote - even when viewed interactively in ghostscript, without =20 > converting to pdf. I see! Before I just looked into the PS file... (it's OK) It's a bug =20 on the presentation level. Certainly! The font encoding used in the PS =20= file, /ISOLatin1Encoding, does not change the ` to =91 =96 and I think =20= it's even not applied because the /FontType of BitstreamVeraSansMono =20 (I just noticed the "Roman" in its PostScript font name!) is 0 (and =20 PostScript font is only then re-encoded when it does not know about =20 the /ISOLatin1Encoding). And so its Unicode font encoding is used =20 straight away =96 which might cause the application of some default =20 features of the font, one of them being the change from ASCII quotes =20 to "typographic" quotes. You can check this behaviour in OpenOffice or =20= TextEdit. There must be some way of turning these default features =20 off! I am thinking of reporting a bug... Or at least a request for =20 enhancement! Your first report was with the "standard" Ghostscript fonts in use, =20 i.e. with substituting the real fonts, Courier, with clones from urw+=20 +, NimbusMonL. These are PostScript Type 1 fonts, they have kind of a =20= backquote, which could be clearer. When I produce with a ps-print =20 output from the ascii(7) man page it uses the Courier font name but =20 looks up NimbusMonL. Pdffonts tells Courier is used in the PDF file =96 =20= which shows =91 instead of `. When gs or gv are displaying the PDF file =20= I can't see an open font file with lsof, will try later=96European =20 evening, five or six hours from now=96with some DTrace to determine =20 which font file get used. If at all! Libfontconfig might supply them. =20= And then they'll be TrueType or OpenType. I'm thinking of one more experiment: embedding the PostScript fonts, =20 Courier and LuxiMono. > So something about the way ps-print generates postscript is =20 > interfering with the use of the added fonts, perhaps. No! This is *not* happening. Although I can understand the cause of =20 this: your short test file shows `, the other file from ps-print =20 not... But see above! > > Thus inspecting the resulting PDF is unlikely to tell us anything =20 > interesting. It would be far easier to just inspect the original =20 > postscript generated by ps-print. As far as I can understand the PS code it's OK. Inside it no =20 conversion of ` to =91 happens. But then I wonder why when I use the =20 PostScript Type 1 LuxiMono fonts from X11, which do not have a TT or =20 OT "counterpart", the same conversion happens! It's a deep mystery, =20 making life worth living, presumingly. The Mac OS X software uses this to convert between formats: /System/Library/Printers/Libraries/convert -f Vera.ps -o = Vera.pdf -i =20 application/postscript -j application/pdf -P =AB path your printer's PPD = =20 file, for example /etc/cups/ppd/EPSON_EPL_5800.ppd or where ever the =20 Installer installs the printer driver package; /etc/cups/ppd is the =20 place where the PrintUtility copies and customises it =BB -- Greetings Pete Progress (n.): Process through which USENET evolved from smart people =20= in front of dumb terminals to dumb people in front of smart terminals.