From: David Kastrup <dak@gnu.org>
Subject: Re: Trouble compiling latex sources in UTF-8 encodind
Date: Wed, 19 Jan 2005 11:54:24 +0100 [thread overview]
Message-ID: <x53bwx8za7.fsf@lola.goethe.zz> (raw)
In-Reply-To: 87zmz6b96x.fsf@nostromo.wy
giglio robbo' d'acciaio <daniele@mother.nostromo.wy> writes:
> Forgive me i I make dumb questions but this unicode stuff really
> drives me crazy.
> Once I've saved a file using unicode utf-8, how can I translate it
> into another coding system, like latin-1 for istance, without
> messing 8bit chars?
C-x RET f runs the command set-buffer-file-coding-system
which is an interactive compiled Lisp function in `international/mule'.
It is bound to C-x RET f, <menu-bar> <options> <mule> <set-various-coding-system> <set-buffer-file-coding-system>.
(set-buffer-file-coding-system CODING-SYSTEM &optional FORCE NOMODIFY)
Set the file coding-system of the current buffer to CODING-SYSTEM.
This means that when you save the buffer, it will be converted
according to CODING-SYSTEM. For a list of possible values of CODING-SYSTEM,
use M-x list-coding-systems.
If CODING-SYSTEM leaves the text conversion unspecified, or if it
leaves the end-of-line conversion unspecified, FORCE controls what to
do. If FORCE is nil, get the unspecified aspect (or aspects) from the
buffer's previous `buffer-file-coding-system' value (if it is
specified there). Otherwise, leave it unspecified.
This marks the buffer modified so that the succeeding C-x C-s
surely saves the buffer with CODING-SYSTEM. From a program, if you
don't want to mark the buffer modified, specify t for NOMODIFY.
If you know exactly what coding system you want to use,
just set the variable `buffer-file-coding-system' directly.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2005-01-19 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 15:06 Trouble compiling latex sources in UTF-8 encodind giglio robbo' d'acciaio
2005-01-17 15:41 ` Peter Dyballa
[not found] ` <mailman.13693.1105977418.27204.help-gnu-emacs@gnu.org>
2005-01-17 16:10 ` David Kastrup
2005-01-17 16:25 ` Matthias
2005-01-17 16:47 ` David Kastrup
2005-01-18 9:34 ` Matthias
2005-01-18 23:37 ` giglio robbo' d'acciaio
2005-01-19 10:54 ` David Kastrup [this message]
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=x53bwx8za7.fsf@lola.goethe.zz \
--to=dak@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.