unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Tim X <timx@nospam.dev.null>
Cc: help-gnu-emacs@gnu.org
Subject: Re: g-client: character coding problem
Date: Mon, 14 May 2007 12:16:13 +0200	[thread overview]
Message-ID: <C57E744B-8D01-444A-925B-F60A681E37E8@Web.DE> (raw)
In-Reply-To: <87zm47g866.fsf@lion.rapttech.com.au>


Am 14.05.2007 um 09:45 schrieb Tim X:

> BTW, can someone tell me what emacs 23 is? I'm running from CVS and  
> it reports
> the version as emacs 22. I've seen a number of references to emacs  
> 23, which
> I've not heard of and didn't think existed (given that I would  
> expect the CVS
> to be the latest version).

It's another branch (unicode-2) of GNU Emacs. It is based on Unicode  
as a means to represent text characters. Therefore a particular  
character has the same code no matter what encoding is used in that  
buffer. You can isearch for à or ï in every buffer and every  
encoding. It also uses anti-aliasing (although I am not sure whether  
I see the effect) and an experimental font-backend, that seems to be  
different from the fontsets used in earlier Emacsen. Another  
difference is the use of font-config library. Recently libotf has  
been introduced into the code, but it still does not use OpenType  
fonts. All the changes that happen to GNU Emacs 22 in CVS can be  
found after some delay in Unicode Emacs 23.

Documentation is not perfect, there is no explicit mentioning of  
Emacs 23 specific functions and you have to search a lot to  
understand how to make use of the additions. It seems to me that the  
extra code for Carbon Emacs (for Mac OS X) is buggy and not supported  
and maintained. Besides, the X client runs quite reliable!

--
Greetings

   Pete

There's no sense in being precise when you don't even know what  
you're talking about.
                                   -- John von Neumann

  parent reply	other threads:[~2007-05-14 10:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 14:55 g-client: character coding problem Joseph Fahey
2007-05-13 15:33 ` Hadron
2007-05-13 15:43   ` Hadron
2007-05-13 17:55     ` Joseph Fahey
2007-05-13 21:08       ` Hadron
2007-05-14  7:45         ` Tim X
2007-05-14  9:36           ` Hadron
2007-05-17  8:49             ` Tim X
2007-05-14  9:39           ` Hadron
2007-05-14 10:16           ` Peter Dyballa [this message]
     [not found]           ` <mailman.631.1179138267.32220.help-gnu-emacs@gnu.org>
2007-05-14 10:31             ` Hadron
2007-05-14 12:12               ` Peter Dyballa
2007-05-14  7:28 ` Enchanter
2007-05-14  7:49   ` Tim X

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=C57E744B-8D01-444A-925B-F60A681E37E8@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=timx@nospam.dev.null \
    /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).