all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Penton <djp@arqux.com>
To: GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: ps-print question
Date: Sun, 2 Jan 2011 21:19:48 -0500	[thread overview]
Message-ID: <5B72ACF7-0ACA-4DC9-A49F-98AA1DF0B504@arqux.com> (raw)
In-Reply-To: <EA1D8D5D-741D-4FA2-BD65-89CFF32DA2A8@Web.DE>


On 2011-01-02, at 7:22 PM, Peter Dyballa wrote:

> 
> Am 02.01.2011 um 22:20 schrieb David Penton:
> 
>> (This is in `Bitstream Vera Sans Mono Roman)
> 
> 
> Yeah – this is OK, except that the font is not "Roman". The ` character becomes

Actually, the font IS a Roman font. In typography Roman can either mean a serif font or an upright (not slanted, not italic) font. (Check wikipedia on this point.)  The Bitstream Vera font name uses Roman in the second sense.

In any case this font name was generated by the genfontmap.ps utility that comes with ghostscript, which extracts the font name directly from the TTF font file. That is what I used to generate a new fontmap for ghostscript; I did not choose the font names.

No matter; this is not part of the problem in any case.

> 
>        character: ‘ (8216, #o20030, #x2018)
> 
> in the PDF file via a CMAP (character mapping) in the PDF output file! Heh, this is a GNU service! Messages from the GNU Compiler Collection (GCC) are quoted in these "typographic" single or double quotes. (For which you can see in the *compilation* buffer lots of \342\200\234, \342\200\235, \342\200\236, \342\200\237 sequences.)
> 
> I tried to use -dCMAPDEBUG -dTTFDEBUG to debug a bit what gs is doing, but it's not clear why and when which CMap file gets inserted. Maybe you can find on the Ghostscript home page a clue to get specific ps2pdfwr help.
> 

Well, thanks for the information, Peter, but this line of analysis may not help very much, I fear.

The content of the pdf file is not directly relevant to the problem, nor is ps2pdfwr. The problem arises before conversion to pdf.

In my earlier posts I pointed out that the backquote IS preserved in the simple little postscript example that I supplied. It is preserved in interactive ghostscript, and also by my modified ps2pdfwr script so that the backquote appears properly in the resulting pdf file.

However, postscript generated by ps-print does NOT preserve the backquote - even when viewed interactively in ghostscript, without converting to pdf. So something about the way ps-print generates postscript is interfering with the use of the added fonts, perhaps.

Thus inspecting the resulting PDF is unlikely to tell us anything interesting. It would be far easier to just inspect the original postscript generated by ps-print.

> 
> What keeps you from using mac-print-mode? It preserves the backquote. Or /quoteleft in PostScript.

By now I already have more than one way of printing that preserves the backquote. But I am still interested in getting ps-print to work as I believe it should.

> 
> --
> Greetings
> 
>  Pete
> 
> A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools.
> 	- Douglas Adams, »Mostly Harmless«
> 




  reply	other threads:[~2011-01-03  2:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-31  7:22 ps-print question David Penton
2010-12-31  7:33 ` David Penton
2010-12-31  9:22 ` Peter Dyballa
2010-12-31 14:02   ` David Penton
2010-12-31 14:44     ` Peter Dyballa
2011-01-01  2:07     ` David Penton
2011-01-01 20:55       ` Peter Dyballa
2011-01-02  0:43         ` Peter Dyballa
2011-01-02 21:20           ` David Penton
2011-01-03  0:22             ` Peter Dyballa
2011-01-03  2:19               ` David Penton [this message]
2011-01-03 13:15                 ` Peter Dyballa
2011-01-03 14:25                   ` David Penton
2011-01-03 18:02                     ` Peter Dyballa
2011-01-03 23:43                     ` Peter Dyballa
2011-01-05  0:20                     ` Peter Dyballa
2011-01-07  3:56                       ` David Penton
2011-01-07 10:28                         ` Peter Dyballa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B72ACF7-0ACA-4DC9-A49F-98AA1DF0B504@arqux.com \
    --to=djp@arqux.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.