From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: PostScript printing Latin-N (with N != 1)
Date: Wed, 11 Jan 2006 16:55:15 +0100 [thread overview]
Message-ID: <v9d5iydajg.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: uy81nri4h.fsf@gnu.org
On Tue, Jan 10 2006, Eli Zaretskii wrote:
>> /usr/share/fonts/bdf$ ls
[...]
> Does any of these fonts support Latin-9? If not, that's the reason
> for the empty box instead of the Euro.
I don't know. Probably not, as you message on emacs-devel suggests.
> But if your printer has Latin-9 fonts, you could use
> 'bdf-font-except-latin if you modify
> ps-mule-font-info-database-latin to handle Latin-9 instead of
> Latin-1.
With the patch and setup suggested by Kenichi Handa I was able to
print Latin-9 but it was wrong for Latin-1. (see my previous message:
<http://article.gmane.org/gmane.emacs.pretest.bugs/9536>)
Maybe Emacs could do something similar to GNU enscript. Printing my
sample file with "enscript --encoding=latin9" (and latin1) works
there: gs is able to display the correct glyphs. (Since most
end-users don't have real PostScript printers, it should be possible
to render the output with gs as most print systems on GNU/Linux use
it, AFAIK.)
> Anyway, the original issue was this:
>
>> On Fri, Jan 06 2006, Eli Zaretskii wrote:
>>
>> > Your message to which I replied made it sound like Emacs PostScript
>> > printing is broken for anything but Latin-1. Which is clearly not
>> > true. All one needs is download and install the GNU Intlfonts
>> > package and customize a few variables as documented in ps-mule.el.
>
> So, even if Latin-9 is not supported because Intlfonts doesn't have a
> font for it, it doesn't mean only Latin-1 is supported.
I didn't claim that it doesn't work for anything else but Latin-1. I
only tested the most important encoding beyond Latin-1 for my region
which is Latin-9 because of the Euro sign.
> Try printing Latin-2, Latin-3, Cyrillic, Thai, Japanese, etc.
Printing the same file (with the €uro) encoded in UTF-8 fails with:
"bdf-read-font-info: BDF file etl24-unicode.bdf doesn't exist"
Printing the Thai example text from HELLO produces a PS file, but gs
can't display the PS file (as in my previous mail):
Unrecoverable error: typecheck in aload
Operand stack:
SpaceWidth --nostringval--
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-01-11 15:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 0:34 Printing from WindowXP version of emacs BRUCE INGALLS
2006-01-04 10:00 ` Peter Dyballa
2006-01-05 1:56 ` BRUCE INGALLS
2006-01-05 13:01 ` Peter Dyballa
2006-01-05 15:41 ` Lennart Borgman
2006-01-05 21:17 ` Peter Dyballa
2006-01-06 8:39 ` Eli Zaretskii
2006-01-05 20:44 ` Eli Zaretskii
2006-01-05 21:18 ` Peter Dyballa
2006-01-06 8:36 ` Eli Zaretskii
2006-01-06 11:59 ` Peter Dyballa
2006-01-06 14:07 ` Eli Zaretskii
2006-01-10 17:37 ` PostScript printing Latin-N (with N != 1) (was: Printing from WindowXP version of emacs) Reiner Steib
2006-01-10 19:35 ` Eli Zaretskii
2006-01-11 15:55 ` Reiner Steib [this message]
2006-01-11 19:59 ` PostScript printing Latin-N (with N != 1) Eli Zaretskii
2006-01-12 20:35 ` Reiner Steib
2006-01-13 8:10 ` Eli Zaretskii
2006-01-13 17:09 ` Reiner Steib
2006-01-11 21:55 ` Peter Dyballa
2006-01-05 16:05 ` translation software (was: Printing from WindowXP version of emacs) Reiner Steib
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=v9d5iydajg.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@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.
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).