From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Peter Dyballa Newsgroups: gmane.emacs.help Subject: Re: font or face problem in emacs Date: Fri, 30 Jun 2006 11:03:24 +0200 Message-ID: <3C4B580F-CC90-4C6A-A915-92E2F5FB7CF5@Web.DE> References: <7F44E50F-B4E1-4692-A021-D78D5596956D@Web.DE> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1151658271 2176 80.91.229.2 (30 Jun 2006 09:04:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 30 Jun 2006 09:04:31 +0000 (UTC) Cc: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jun 30 11:04:29 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FwEul-00024Z-SY for geh-help-gnu-emacs@m.gmane.org; Fri, 30 Jun 2006 11:03:52 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FwEul-0008Bb-DG for geh-help-gnu-emacs@m.gmane.org; Fri, 30 Jun 2006 05:03:51 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FwEuR-0008BB-Ac for help-gnu-emacs@gnu.org; Fri, 30 Jun 2006 05:03:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FwEuO-0008AQ-Kb for help-gnu-emacs@gnu.org; Fri, 30 Jun 2006 05:03:29 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FwEuO-0008AI-HC for help-gnu-emacs@gnu.org; Fri, 30 Jun 2006 05:03:28 -0400 Original-Received: from [217.72.192.227] (helo=fmmailgate02.web.de) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FwF78-0005bg-15 for help-gnu-emacs@gnu.org; Fri, 30 Jun 2006 05:16:38 -0400 Original-Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate02.web.de (Postfix) with ESMTP id 47C4457BF46; Fri, 30 Jun 2006 11:03:27 +0200 (CEST) Original-Received: from [84.245.187.34] (helo=[192.168.1.2]) by smtp05.web.de with asmtp (TLSv1:RC4-SHA:128) (WEB.DE 4.107 #114) id 1FwEuM-0002rY-00; Fri, 30 Jun 2006 11:03:27 +0200 In-Reply-To: X-Image-Url: http://homepage.mac.com/sparifankal/.cv/thumbs/me.thumbnail Original-To: H.S. X-Mailer: Apple Mail (2.750) X-Sender: Peter_Dyballa@web.de X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:35754 Archived-At: Am 30.06.2006 um 01:34 schrieb H.S.: > Peter Dyballa wrote: > >> Make the *compilation* buffer be encoded in UTF-8 or make your =20 >> LANG or LC_CTYPE environment variables 8 bit -- could be there is =20= >> some option in your g++ to stay in 8 bit when printing some message. > > Yes, that is one method. But with all this talk of systems being =20 > utf-8 compatible and such these days, I was expecting that =20 > applications are getting better at this. If Emacs is not UTF-8 =20 > complaint, I would like to know for sure so that I can accomodate =20 > other applications I use. On the other hand, if Emacs is expected =20 > to recognize UTF-8, then there ought to be a way to make it do so =20 > by default. All I want to know is which way is it? > GNU Emacs 21.4 is probably missing a lot (I don't use it, I 21.3.50 =20 from CVS around), version 22.0.50 is far away from an UTF-8 =20 application, at least with my customisation. GNU Emacs 23.0.0 =20 performs better, but has problems, too. In 21.3.50 and 22.0.50 *shell* and dired buffers seem to have =20 problems with UTF-8 file names, although in *shell* I can 'cat' =20 kermit's utf_8.txt and some 10K glyphs are displayed. *compilation* =20 or *Completions* work fine. It depends on your demands ... Sometime in GNU Emacs 21.x code was introduced to read LANG and/or =20 LC_CTYPE and prepare some default encoding of buffers based an these =20 environment variables. Since then it's not necessary to set terminal =20 or keyboard or clipboard or ... coding systems. There is much code =20 that outputs only 7bit or 8bit messages. You can see from my *shell* =20 example that most things work, but some don't. In GNU Emacs 23 for =20 example the method of Mac OS X's HFS+ file system to store UTF-8 file =20= names as decomposed characters leads to file names that look ugly =20 because some mechanism builds from a and =C2=A8 an =C3=A4. And somehow = the =20 combining modifier =C2=A8 is not positioned correctly ... When the =20 character is pr=C3=AAt-=C3=A0-porter, "composed," as in kermit's = utf_8.txt, =20 then it looks fine -- but the fonts to display these characters =20 change to so that the glyphs used do not fit in size and other =20 parameters. If there were a monospaced Unicode encoded font without gaps to span =20 from SPACE to REPLACEMENT CHARACTER ([=EF=BF=BD] at FFFD) it wouldn't be = so =20 ugly. (There are two more PLANES with each 64K characters defined in =20 Unicode 4.x.) -- Greetings Pete There are two major products that come out of Berkeley: LSD and UNIX. =20= We don't believe this to be a coincidence. - Jeremy S. Anderson