From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mildred Newsgroups: gmane.emacs.bugs Subject: UTF8 encoded Tibetan text doesn't display correctly (ISO-2022 does) Date: Fri, 15 Feb 2008 01:41:06 +0100 Message-ID: <20080215014106.1c678a89@kylae> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/FPrICFY9Y0meeveN1r047Pw"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Trace: ger.gmane.org 1203040520 28952 80.91.229.12 (15 Feb 2008 01:55:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 Feb 2008 01:55:20 +0000 (UTC) To: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Feb 15 02:55:42 2008 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JPpnb-0006SA-9K for geb-bug-gnu-emacs@m.gmane.org; Fri, 15 Feb 2008 02:55:35 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JPpn7-0003RT-IN for geb-bug-gnu-emacs@m.gmane.org; Thu, 14 Feb 2008 20:55:05 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JPofy-0005CM-8Z for bug-gnu-emacs@gnu.org; Thu, 14 Feb 2008 19:43:38 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JPofx-0005BS-Kr for bug-gnu-emacs@gnu.org; Thu, 14 Feb 2008 19:43:38 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JPofx-0005BG-G5 for bug-gnu-emacs@gnu.org; Thu, 14 Feb 2008 19:43:37 -0500 Original-Received: from fg-out-1718.google.com ([72.14.220.159]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JPofx-0006j0-2Q for bug-gnu-emacs@gnu.org; Thu, 14 Feb 2008 19:43:37 -0500 Original-Received: by fg-out-1718.google.com with SMTP id d23so316870fga.30 for ; Thu, 14 Feb 2008 16:43:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject:message-id:x-mailer:jabber-id:x-face:mime-version:content-type:sender; bh=if1l84k8tMYFrLh2CNSHlQMFfzNC6imvsngwxc9Nba8=; b=B/Lj2XYhr8C73vB8rPSfWA5RKD1NlbSD6RD2DOmwUIiUHfz/t2Lja12msbJAFIhGJSI6swUDGwBDKBiyM/RB2eePjT7Z4vo8ama1DTPsQELG0GaWfBsMDOcHpXZ3dJmxD3FGaNUcblSRs9Ipra5lCSCr8koMeEiOQ3TBCPjkISI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:jabber-id:x-face:mime-version:content-type:sender; b=R40UXUg0bR2TyHeQ7G6Ol2e37DAdY+ZMYy/O/aDIjzKClaQLci/KgYKXrYS5ydRi33Vvi89P+td+BOFlcSULNfT7uAMpXEh8QJROqZEj3Fdh7XhwXgwIZqxPn7Vl9MIBHtqYCAqyMPb9bh6vovZUk2ruk14kds1dOT+gcXRYvQc= Original-Received: by 10.86.74.15 with SMTP id w15mr1873457fga.37.1203036215661; Thu, 14 Feb 2008 16:43:35 -0800 (PST) Original-Received: from kylae ( [78.113.252.77]) by mx.google.com with ESMTPS id 4sm3905201fgg.4.2008.02.14.16.43.33 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Feb 2008 16:43:34 -0800 (PST) X-Mailer: Claws Mail 3.2.0 (GTK+ 2.12.5; i686-pc-linux-gnu) Jabber-ID: mildred@jabber.fr X-Face: 8GNwq-wp^)-`2h1s$2D@0K.&&@k%qL3Ir->`)a~K?DkicwES"'xM5^NNQ!T_rjM5D\~$^_V Nhor4E,9' List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:17532 Archived-At: --Sig_/FPrICFY9Y0meeveN1r047Pw Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I have a problem with emacs. It seems that it is not able to display Tibetan characters correctly if the buffer is utf-8 encoded. Instead of tibetan characters, we see rectangles as if the font wasn't available. But others X programs can use it. What I don't understand is that it is possible to display tibetan characters when we use MULE on a new buffer that is not unicode encoded. By default, MULE choose the ISO-2022 encoding and it works. So, why does it works with iso-2022 (that I never heard about, and never used) and not utf-8 ? Thanks Mildred PS: You can find a tibetan unicode font in this page: Follow the link then the link in the third paragraph. Here is some UTF-8 encoded tibetan text if you want to test: =E0=BD=A7=E0=BD=B1=E0=BD=B4=E0=BE=82=E0=BC=94 =E0=BD=A8=E0=BD=B4=E0=BC=8B= =E0=BD=A2=E0=BE=92=E0=BE=B1=E0=BD=93=E0=BC=8B=E0=BD=A1=E0=BD=B4=E0=BD=A3=E0= =BC=8B=E0=BD=82=E0=BE=B1=E0=BD=B2=E0=BC=8B=E0=BD=93=E0=BD=B4=E0=BD=96=E0=BC= =8B=E0=BD=96=E0=BE=B1=E0=BD=84=E0=BC=8B=E0=BD=98=E0=BD=9A=E0=BD=98=E0=BD=A6= =E0=BC=94 =E0=BD=94=E0=BD=91=E0=BE=A8=E0=BC=8B=E0=BD=82=E0=BD=BA=E0=BC=8B=E0=BD=A6=E0= =BD=A2=E0=BC=8B=E0=BD=A6=E0=BE=A1=E0=BD=BC=E0=BD=84=E0=BC=8B=E0=BD=94=E0=BD= =BC=E0=BC=8B=E0=BD=A3=E0=BC=94 --=20 Mildred Ki'lya Site: XMPP: (GoogleTalk, Jabber) GPG: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 [9A7D 2E2B] --Sig_/FPrICFY9Y0meeveN1r047Pw Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (GNU/Linux) iEYEARECAAYFAke036MACgkQb52o1pp9LitpxwCdFMCite479VV01Co9GjLGsiNI m44An3AwaO4VL81+GR0P1k9gK7sG4JnD =ybQ5 -----END PGP SIGNATURE----- --Sig_/FPrICFY9Y0meeveN1r047Pw--