From: ken <gebser@mousecar.com>
To: GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: utf8 char display in buffer
Date: Tue, 09 Jun 2009 10:51:43 -0400 [thread overview]
Message-ID: <4A2E76FF.1010306@mousecar.com> (raw)
In-Reply-To: <zfKdnTURLPMBwLPXnZ2dnUVZ_oSdnZ2d@sysmatrix.net>
On 06/09/2009 09:03 AM B. T. Raven wrote:
> ken wrote:
>> On 06/08/2009 04:43 PM B. T. Raven wrote:
>>> ken wrote:
>>>> ....
>>>>
>>> C-x ret C-\ latin-4-postfix
>>>
>>> then a,e,i,o,u followed by hyphen generate macroned vowels
>>>
>>> ....
>>
>> Fantastic! But... when I save and close the buffer and then open it up
>> again, in place of the beautiful and correct characters, there are
>> little boxes.
>
> After you see then correctly in the buffer do:
>
> C-x ret c utf-8
>
> then
>
> C-x C-s
>
> Now next time you load that file it should appear correctly.
> ā and ī are not in iso-8859-1 and so you must use a more comprehensive
> coding system.
Hmmm... it doesn't. Doing everything just as you say above, I still get
the little boxes in place of the non-English characters.
When after reloading the buffer, I run "describe-coding-system" on this
buffer, I get:
=============================================
Coding system for saving this buffer:
u -- mule-utf-8-unix
Default coding system (for new files):
u -- mule-utf-8 (alias: utf-8)
Coding system for keyboard input:
nil
Coding system for terminal output:
0 -- iso-latin-9 (alias: iso-8859-15 latin-9 latin-0)
Defaults for subprocess I/O:
decoding: u -- mule-utf-8 (alias: utf-8)
encoding: u -- mule-utf-8 (alias: utf-8)
Priority order for recognizing coding systems when reading files:
1. mule-utf-8 (alias: utf-8)
2. iso-latin-1 (alias: iso-8859-1 latin-1)
3. iso-2022-jp (alias: junet)
4. iso-2022-7bit
5. iso-2022-7bit-lock (alias: iso-2022-int-1)
6. iso-2022-8bit-ss2
7. emacs-mule
8. raw-text
9. japanese-shift-jis (alias: shift_jis sjis)
10. chinese-big5 (alias: big5 cn-big5)
11. no-conversion (alias: binary)
Other coding systems cannot be distinguished automatically
from these, and therefore cannot be recognized automatically
with the present coding system priorities.
The followings are decoded correctly but recognized as iso-2022-7bit-lock:
iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn iso-2022-cn-ext
iso-2022-jp-2 iso-2022-kr
....
==================================================================
I don't know... does utf-8 or mule-utf-8 contain latin-4, greek, and/or
German characters? (This file has some of each.)
>>
>> I tried using ‘C-x C-m c utf-8 RET’ prior to 'C-x C-f filename'... but
>> no joy. Same no-go with 'C-x C-m c mule-utf-8 RET'.
>>
>> The fact that these non-English characters display properly in the
>> buffer initially tells me that I have the requisite fonts installed. So
>> what little connection is emacs not making (and how do I tell it to make
>> that connection)?
>
> If you use utf-8 a lot you can put ;; -*- coding: utf-8[;] -*- into the
> first line of the file. I don't know whether that sem in brackets is
> needed or not.
Sorry, I should have mentioned that I have this (with the semi-colon) at
the top of the file.
Let me also say that, though the little boxes appear in the emacs
buffer, the proper non-English characters appear when the file is loaded
into firefox. (Yeah, this emacs file is an HTML page.)
>
>>
>> Thanks, all.
>>
>>
next prev parent reply other threads:[~2009-06-09 14:51 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.227.1244485995.2239.help-gnu-emacs@gnu.org>
2009-06-08 19:10 ` utf8 char display in buffer Teemu Likonen
2009-06-08 19:52 ` Xah Lee
2009-06-09 10:52 ` ken
2009-06-08 20:43 ` B. T. Raven
2009-06-08 20:49 ` B. T. Raven
2009-06-08 22:49 ` ken
2009-06-09 10:24 ` ken
[not found] ` <mailman.289.1244543082.2239.help-gnu-emacs@gnu.org>
2009-06-09 13:03 ` B. T. Raven
2009-06-09 14:51 ` ken [this message]
[not found] ` <mailman.297.1244559110.2239.help-gnu-emacs@gnu.org>
2009-06-10 1:34 ` B. T. Raven
2009-06-10 14:03 ` Lewis Perin
2009-06-11 3:21 ` B. T. Raven
2009-06-12 14:54 ` ken
2009-06-13 3:30 ` Eli Zaretskii
[not found] ` <mailman.522.1244818530.2239.help-gnu-emacs@gnu.org>
2009-06-12 15:39 ` Lewis Perin
2009-06-12 16:48 ` B. T. Raven
2009-06-12 17:45 ` Lewis Perin
2009-06-12 17:53 ` Xah Lee
2009-06-12 20:59 ` Lennart Borgman
2009-06-12 22:23 ` ken
2009-06-12 22:27 ` Lennart Borgman
2009-06-12 23:38 ` ken
2009-06-13 4:11 ` Eli Zaretskii
2009-06-13 12:30 ` ken
2009-06-13 13:23 ` Eli Zaretskii
2009-06-14 20:59 ` Stefan Monnier
2009-06-13 1:36 ` Miles Bader
2009-06-13 1:43 ` Lennart Borgman
2009-06-13 5:50 ` Richard Stallman
2009-06-15 4:34 ` Miles Bader
2009-06-15 19:30 ` Richard Stallman
2009-06-16 0:30 ` James Cloos
2009-06-16 1:10 ` Miles Bader
2009-06-16 1:12 ` Miles Bader
2009-06-17 5:07 ` Richard Stallman
2009-06-16 13:53 ` Chong Yidong
2009-06-16 20:48 ` Stefan Monnier
2009-06-15 20:06 ` Chong Yidong
2009-06-15 21:57 ` Drew Adams
2009-06-16 5:30 ` Richard Stallman
[not found] ` <mailman.536.1244845400.2239.help-gnu-emacs@gnu.org>
2009-06-13 0:35 ` Xah Lee
2009-06-12 17:27 ` Xah Lee
2009-06-12 19:30 ` Lewis Perin
2009-06-12 19:43 ` Xah Lee
2009-06-12 20:56 ` B. T. Raven
2009-06-13 16:16 ` Xah Lee
2009-06-13 20:35 ` Lewis Perin
2009-06-14 11:47 ` ken
2009-06-15 7:28 ` Bernardo
2009-06-11 12:03 ` Teemu Likonen
2009-06-11 12:55 ` Lennart Borgman
2009-06-11 13:04 ` Andreas Schwab
2009-06-11 13:07 ` Lennart Borgman
2009-06-11 13:08 ` Lennart Borgman
2009-06-11 13:24 ` Tassilo Horn
2009-06-08 18:33 ken
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2E76FF.1010306@mousecar.com \
--to=gebser@mousecar.com \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.