From: "A. L. Meyers" <nospam.look@replyto.because.this.is.invalid>
Subject: Re: problems printing non-usascii characters
Date: Tue, 03 Sep 2002 21:24:08 +0200 [thread overview]
Message-ID: <87elcaop0n.fsf@nomad.consult-meyers.com> (raw)
In-Reply-To: wk65xn6p4p.fsf@ID-97657.usr.dfncis.de
Thanks, Lawrence. Here is Eli's answer:
It's a 2-step dance:
1. Frob the list in ps-mule-font-info-database-bdf to include an
association for Latin-9 (see ps-mule.el).
2. Install a Latin-9 BFD font (if you don't have it already).
(While at that, please submit the changes to ps-mule.el for inclusion in
a future release.)
Alternatively, if your printer can print Latin-9 directly, modify
ps-mule-font-info-database-latin to include an association for Latin-9.
Sounds simple but it puts me out of my depths, which, admittedly, are
very shallow. Some observations:
1. The problem exists with Gentoo GNU/Linux, not with Debian 3.0.
(Perhaps blissful Southwestern US Province influence; they would
anyway have preferred countinuing with 7bit ascii forever. ;-) )
2. Cannot find the verb "to frob" in my English dictionary.
3. Have a Postscript level 3 printer. How can I know if it "groks"
(he-he) Latin-9 directly?
So, to paraphrase Goethe's saying, I am as clever as before.
Lucien
--
If you receive this by error, please delete it and inform the sender.
PGP Key fingerprint=F1C0 D9AE 1B18 1405 4DFA B4CC 6DC7 FF78 C76E FB15
To Big Brother Echelon from "spook":
Semtex supercomputer cryptographic sentiero luminoso kibo Sharon Ortega
next prev parent reply other threads:[~2002-09-03 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 13:14 problems printing non-usascii characters A. L. Meyers
2002-09-03 15:12 ` Kai Großjohann
2002-09-03 15:39 ` A. L. Meyers
2002-09-03 15:59 ` lawrence mitchell
2002-09-03 19:24 ` A. L. Meyers [this message]
2002-09-03 21:49 ` Kai Großjohann
2002-09-04 6:42 ` A. L. Meyers
2002-09-03 15:55 ` A. L. Meyers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87elcaop0n.fsf@nomad.consult-meyers.com \
--to=nospam.look@replyto.because.this.is.invalid \
--cc=almeyers@freesurf.ch \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).