From: jasonr (Jason Rumney) @ f2s.com
Subject: Re: emacs 22 release
Date: Thu, 29 Sep 2005 22:18:10 +0100 [thread overview]
Message-ID: <uachvh8tp.fsf@jasonrumney.net> (raw)
In-Reply-To: mailman.9069.1127988970.20277.help-gnu-emacs@gnu.org
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
> In my 'standard' edition of GNU Emacs 22 I have not changed the
> default values. Adding
>
> (setq unify-8859-on-encoding-mode nil)
> (setq unify-8859-on-decoding-mode t)
>
> makes no change in that field which I address in my writing
As per the documentation for those variables, you can't just set them
like that. Also, I think you want them both set to t, otherwise you
will have problems writing files in various encodings, due to the
buffer representation being a different encoding than what you are
trying to save as. You probably need to kill existing buffers and
reread the files after changing unify-8859-on-decoding-mode, since it
only has any effect when reading files/process output etc.
>> > These characters in the buffer can't be printed:
>> > €, , ¡, ¢, £, €, ¥, Š, §, š, ©, ª, «, ¬, , and more...
>> >
>> > And it's not even true, since I can see ¡, ¢, £, §, ©, ª, «, ¬, ...
This is probably because those characters pass through
unify-8859-on-encoding-mode to convert them to Latin-1 after the
message has already been displayed. Out of the box, ps-print only
handles Latin-1, but there are variables to control this.
> Not yet, but you motivate me to do so! (Again. I think I reported
> something similiar earlier this year and Kenichi Handa then made some
> changes that the message about unprintable characters became more
> realistic, being based on the actual glyphs of the encoding used. He
> promised that in Unicode Emacs 23 the problem will be solved. Could be
> some backlash happened in the meantime that the reports are not true
> again ... as in real life and its politics. Or politicians?)
I think the change you are talking about was when saving a file. The
code for printing is different, so a separate fix will be required
there.
> From these bugs I'd like to estimate that Unicode Emacs 23 will be
> released before GNU Emacs 22. It's worth to go directly to Unicode,
> without wasting the valuable resources of the developers.
Using Unicode in Emacs will not magically fix postscript. There is
more work involved in getting all the peripheral code like ps-print to
take advantage of the Unicode support in the core of Emacs 23 than
there is in fixing a few minor bugs in Emacs 22.
next prev parent reply other threads:[~2005-09-29 21:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 13:04 emacs 22 release Olive
2005-09-28 14:43 ` Nurullah Akkaya
2005-09-28 15:22 ` Peter Dyballa
2005-09-28 20:35 ` Kevin Rodgers
2005-09-29 10:14 ` Peter Dyballa
[not found] ` <mailman.9069.1127988970.20277.help-gnu-emacs@gnu.org>
2005-09-29 21:18 ` Jason Rumney [this message]
[not found] ` <mailman.8996.1127922118.20277.help-gnu-emacs@gnu.org>
2005-09-29 7:12 ` Jason Rumney
2005-09-29 9:25 ` Peter Dyballa
[not found] ` <mailman.9059.1127986983.20277.help-gnu-emacs@gnu.org>
2005-09-29 14:21 ` Johan Bockgård
2005-09-29 19:14 ` Peter Dyballa
2005-10-04 4:48 ` Stefan Monnier
2005-09-29 8:09 ` Sébastien Kirche
2005-09-29 20:43 ` Peter Dyballa
2005-09-30 22:53 ` Peter Dyballa
[not found] ` <mailman.9287.1128121742.20277.help-gnu-emacs@gnu.org>
2005-10-01 12:13 ` Sébastien Kirche
2005-10-01 14:14 ` Peter Dyballa
[not found] ` <mailman.9353.1128176131.20277.help-gnu-emacs@gnu.org>
2005-10-03 17:26 ` Sébastien Kirche
2005-10-04 3:57 ` Stefan Monnier
2005-10-04 8:59 ` Peter Dyballa
[not found] ` <mailman.9673.1128422429.20277.help-gnu-emacs@gnu.org>
2005-10-04 20:43 ` Harald Hanche-Olsen
2005-10-04 22:25 ` Peter Dyballa
[not found] <mailman.8988.1127916392.20277.help-gnu-emacs@gnu.org>
2005-09-29 11:19 ` Ralf Resack
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=uachvh8tp.fsf@jasonrumney.net \
--to=jasonr@f2s.com \
/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).