From: Kenichi Handa <handa@etl.go.jp>
Cc: emacs-devel@gnu.org, vinicius@cpqd.com.br
Subject: Re: Print eight-bit-* characters with ps-print
Date: Mon, 13 May 2002 15:23:29 +0900 (JST) [thread overview]
Message-ID: <200205130623.PAA06806@etlken.m17n.org> (raw)
In-Reply-To: "eliz@is.elta.co.il"'s message of Sun, 12 May 2002 19:31:42 +0300
"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> I use ps-print a lot, and it annoys me that it whines about
> eight-bit-control and eight-bit-graphic characters not having fonts to
> print them with. (These charsets are Emacs's invention, so there's no
> chance anyone will ever have a font for them.)
> So I came up with the change below. It doesn't really print the same
> glyphs you see on your screen--that's impossible without knowing what
> fonts are available to your printer or PostScript interpreter. But at
> least the whining is gone, and for many cases, such as those \222
> characters and Latin-1 email messages sent as ``charset=US-ASCII'', it
> does DTRT.
We already have a function ps-control-character that
properly print control codes, eight-bit-control, and
eight-bit-graphic.
So, to just stop whining about eight-bit-*, what we need is
to delete eight-bit-control and eight-bit-graphic from
charsets in this code (in ps-mule-begin-job of ps-mule.el):
;; Initialize `ps-mule-charset-list'. If some characters aren't
;; printable, warn it.
(let ((charsets (find-charset-region from to)))
(setq charsets (delq 'ascii (delq 'unknown (delq nil charsets)))
ps-mule-charset-list charsets)
Please try to add more delq for eight-bit-* here, and set
ps-print-control-characters to `8-bit' (the default is
`8-bit-control'). Then all eight-bit-* should be printed in
octal form. Isn't it what you want?
> (Btw, it looks like iso-safe can safely encode eight-bit-* characters.
> If that's true, I think we should update its doc string. Handa-san,
> can you please comment on this?)
This is a difficult part. Currently, as far as I remember
all coding-systems encode them as is. They are treated as
special bytes that should be written out as is. I'm not
sure whether or not we should make iso-safe as an exception.
Instead, how about documenting clearly that there's a super
rule that any coding system encodes eight-bit-* as is?
---
Ken'ichi HANDA
handa@etl.go.jp
next reply other threads:[~2002-05-13 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 6:23 Kenichi Handa [this message]
2002-05-17 14:21 ` Print eight-bit-* characters with ps-print Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 0:32 Kenichi Handa
2002-05-12 16:31 Eli Zaretskii
2002-05-13 14:19 ` Richard Stallman
2002-05-13 14:19 ` Richard Stallman
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=200205130623.PAA06806@etlken.m17n.org \
--to=handa@etl.go.jp \
--cc=emacs-devel@gnu.org \
--cc=vinicius@cpqd.com.br \
/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.