all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregor Zattler <grfz@gmx.de>
Cc: 41812@debbugs.gnu.org
Subject: bug#41812: 28.0.50; pr-ps-... does not print certain accented characters, bust shows question marks instead
Date: Fri, 12 Jun 2020 10:30:24 +0300	[thread overview]
Message-ID: <83tuzg4u7j.fsf@gnu.org> (raw)
In-Reply-To: <871rmlv2po.fsf@no.workgroup> (message from Gregor Zattler on Thu, 11 Jun 2020 21:09:55 +0200)

> From: Gregor Zattler <grfz@gmx.de>
> Date: Thu, 11 Jun 2020 21:09:55 +0200
> 
> when printing via ps-print-... I realized, that some
> accented characters, namely
> 
> - capital letter L slash
> - small letter n acute
> - small letter o acute
> - small letter z acute
> 
> are exchanged for question marks.

With the exception of o acute, the other characters aren't Latin-1, so
I think what you see is expected.  To see more characters, you need to
customize ps-mule.el; at least ps-mule-font-info-database-default
should be customized.  Maybe you should also install GNU Intlfonts.  I
suggest to read the commentary at the beginning of ps-mule.el for more
details.

To make the report more easily reproducible and investigated, it is
better to leave printing.el commands that invoke Ghostview out of the
picture, since invoking external commands could produce other
irrelevant issues.  If you instead produce a PostScript buffer out of
your text and look at the produced PostScript, do you see the question
marks there, and if so, for which characters?

Thanks.





  parent reply	other threads:[~2020-06-12  7:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 19:09 bug#41812: 28.0.50; pr-ps-... does not print certain accented characters, bust shows question marks instead Gregor Zattler
2020-06-12  7:14 ` Eli Zaretskii
2020-06-12  7:30 ` Eli Zaretskii [this message]
     [not found] <draft-87pna3i9d5.fsf@no.workgroup>
2020-06-14 19:59 ` Gregor Zattler

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=83tuzg4u7j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=41812@debbugs.gnu.org \
    --cc=grfz@gmx.de \
    /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.