unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: emacs 22 release
Date: Wed, 28 Sep 2005 14:35:36 -0600	[thread overview]
Message-ID: <dheuqq$cp0$1@sea.gmane.org> (raw)
In-Reply-To: <35a160348ae861f38acfdc01919ddb27@Web.DE>

Peter Dyballa wrote:
 > I don't see so many changes from stable GNU Emacs 21.4 to GNU Emacs 22
 > from CVS. The latter still can't handle completely the case of dealing
 > with more than one ISO or Unicode encoding.

Did you happen to turn off unify-8859-on-encoding-mode?  (It's enabled
in Emacs 22 by default.)  Did you try turning on
unify-8859-on-decoding-mode?

 > And printing is still bad
 > too! This message comes from trying to print a buffer in ISO 8859-15/ISO
 > Latin-9:
 >
 >     These characters in the buffer can't be printed:
 > 	 €,  , ¡, ¢, £, €, ¥, Š, §, š, ©, ª, «, ¬, ­, and more...
 >     Click them to jump to the buffer position,
 >     or C-u C-x = will give information about them.
 >
 > And it's not even true, since I can see ¡, ¢, £, §, ©, ª, «, ¬, ­ ...

Have you submitted a bug report?  Looking at the source code, it might
be useful to `M-x debug-on-entry RET ps-mule-show-warning RET' and
report what `e unprintable-charsets RET' shows when invoked in the
*Backtrace* buffer.

Also, that error message includes 4 characters that are outside ISO
8859-x: 0x80 (twice), 0x8A, and 0x9A.  Your message was sent as:

	Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
	Content-Transfer-Encoding: quoted-printable

 > Is it really that complicated to determine the system's TrueType fonts
 > and use the Unicode encoded ones to print in whatever ISO, Greek, or
 > Cyrillic encoding? Or in Arabic or Hebrew?

I don't know, but I suspect it is hard to do for all the platforms that
Emacs supports.

 > I'd look forward to Unicode Emacs 23.

You'd be looking very far forward.

-- 
Kevin Rodgers

  reply	other threads:[~2005-09-28 20:35 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 [this message]
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
     [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='dheuqq$cp0$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.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).