From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: problem with editing/decoding utf-8 text
Date: Fri, 23 May 2003 22:53:57 +0200 [thread overview]
Message-ID: <848ysxo04a.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: u4r3ltqkl.fsf@ID-87814.user.dfncis.de
Oliver Scholz <alkibiades@gmx.de> writes:
> Not 100% if this really makes a difference --
>
> (set-coding-priority (list 'coding-category-utf-8))
>
> maybe?
Thanks!
> 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'?
Gnah :-(
--
This line is not blank.
next prev parent reply other threads:[~2003-05-23 20:53 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
2003-05-23 20:53 ` Kai Großjohann [this message]
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
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=848ysxo04a.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).