From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: problem with editing/decoding utf-8 text
Date: Fri, 23 May 2003 21:23:38 +0200 [thread overview]
Message-ID: <u4r3ltqkl.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: 843cj5hakf.fsf@lucy.is.informatik.uni-duisburg.de
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> Fery <engard.ferenc@innomed.hu> writes:
>
>> I have a UTF-8 text file, containing latin-1 text. When I try to edit it
>> with emacs, it does not detect that it is utf-8; the
>> describe-coding-system gives back 'iso-latin-1-unix'. (And I see the
>> two-byte representation of latin1 chars, which is not bad to me.)
>
> Released versions of Emacs put UTF-8 at a rather low priority for
> automatic encoding detection. So you need to help Emacs by
> explicitly specifying the encoding. Do C-x RET c utf-8 RET before
> using C-x C-f to open the file.
>
> You can also put utf-8 somewhat earlier in the list for automatic
> encoding detection. I think this can be achieved in the following
> way, but I'm not sure. I'm not a Mule expert. If anyone knows
> better, please help out.
>
> (setq coding-category-list
> (cons 'coding-category-utf-8
> (delq 'coding-cateogcoding-utf-8
> coding-category-list)))
>
Not 100% if this really makes a difference --
(set-coding-priority (list 'coding-category-utf-8))
maybe?
If you want UTF-8 to be the default for new files:
(prefer-coding-system 'utf-8)
[...]
>> 1. Cannot I tell to a buffer (after the load of a file) that interpet it
>> as binary, and save exactly the same bytes what it did read into the
>> buffer (i.e. transparent buffer)?
>
> It's not a good idea. The buffer contents might already be munged at
> that point.
[...]
Maybe the OP wants to visit files with `M-x find-file-literally'?
Oliver
--
4 Prairial an 211 de la Révolution
Liberté, Egalité, Fraternité!
next prev parent reply other threads:[~2003-05-23 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6635.1053692285.21513.help-gnu-emacs@gnu.org>
2003-05-23 16:50 ` problem with editing/decoding utf-8 text Kai Großjohann
2003-05-23 19:23 ` Oliver Scholz [this message]
2003-05-23 20:53 ` Kai Großjohann
2003-05-23 21:20 ` Stefan Monnier
[not found] <mailman.6818.1054022957.21513.help-gnu-emacs@gnu.org>
2003-05-27 11:10 ` Oliver Scholz
[not found] ` <3ED37785.CA5A9AD5@innomed.hu>
[not found] ` <ubrxnb5m2.fsf@ID-87814.user.dfncis.de>
2003-05-30 12:45 ` Fery
[not found] ` <mailman.7046.1054298932.21513.help-gnu-emacs@gnu.org>
2003-05-30 13:24 ` Kai Großjohann
[not found] <mailman.6770.1053942670.21513.help-gnu-emacs@gnu.org>
2003-05-27 11:05 ` Oliver Scholz
2003-05-27 11:41 ` Oliver Scholz
2003-05-27 8:06 Fery
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 9:47 Fery
2003-05-26 9:47 Fery
2003-05-23 12:08 Fery
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=u4r3ltqkl.fsf@ID-87814.user.dfncis.de \
--to=alkibiades@gmx.de \
/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.