unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "std" <stdecara@gmail.com>
Subject: Re: emacs 22 on win XP, selection-coding-system, and copy & paste outside emacs
Date: 3 Aug 2006 05:08:50 -0700	[thread overview]
Message-ID: <1154606929.961508.191630@m79g2000cwm.googlegroups.com> (raw)
In-Reply-To: <mailman.4795.1154604386.9609.help-gnu-emacs@gnu.org>

Thanks a lot Pete for this valuable information!

St

Peter Dyballa wrote:
> Am 03.08.2006 um 12:18 schrieb std:
>
> > By the way, is latin-9 a smart choice? (compared to latin-1, or other
> > utf-8 or -16...). I have no idea on these things.
>
> Depends - I use ISO Latin-9/ISO 8859-15 in LaTeX, because then I can
> see € (ISO Latin-1 does not have the Euro currency), my usual
> environment is UTF-8 based. GNU Emacs 22.0.50 still is not perfect in
> UTF-8 use (a month name like Mär in dired is displayed as 'Mär',
> file names appear as 'RGB aÌ\210oÌ\210uÌ\210æÃ\206UÌ\210OÌ
> \210AÌ210.txt' or 'Perl_und_BuÌ\210cher'), the Unicode Emacs 23.0.0
> performs better, so I'd recommend so stay with some 8 bit encoding
> like ISO Latin-9/ISO 8859-15. And use UTF-8 or UTF-16 for data
> exchange with MS Windows XP applications. Both encodings are
> "representations" of a file's contents. UTF-8 uses 8 bit words to
> code this contents, usually using three or two of these words for
> each character, only in case of ASCII or ISO Latin-1 use one such
> word suffices. UTF-16 uses 16 bit words - so it can address the first
> 64 K characters in Unicode uniformly, although it makes a difference
> in which sequence/direction the two octets of bits are read, BE or
> LE. Behind the Basic Multilingual Plane (BMP), UTF-8 and UTF-16 need
> to use 32 bits to address the Unicode characters - just as UTF-32
> uses from the start. But of course each of these three systems uses
> its own codes in this range(s)/plane(s) ...
> 
> --
> Greetings
> 
>    Pete
> 
> Bake Pizza not war!

      parent reply	other threads:[~2006-08-03 12:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  9:26 emacs 22 on win XP, selection-coding-system, and copy & paste outside emacs std
2006-08-03  9:48 ` Peter Dyballa
2006-08-03 22:35   ` Reiner Steib
2006-08-03 23:12     ` Peter Dyballa
2006-08-04  8:37       ` set-language-environment (was: emacs 22 on win XP, selection-coding-system, and copy & paste outside emacs) Reiner Steib
2006-08-04 11:44         ` Peter Dyballa
2006-08-04 10:17       ` emacs 22 on win XP, selection-coding-system, and copy & paste outside emacs Eli Zaretskii
2006-08-04 10:51         ` Peter Dyballa
2006-08-04 11:14           ` Eli Zaretskii
2006-08-04 11:36             ` Peter Dyballa
     [not found]         ` <mailman.4839.1154688716.9609.help-gnu-emacs@gnu.org>
2006-08-04 11:07           ` David Kastrup
2006-08-04 11:47             ` Peter Dyballa
2006-08-04 12:11               ` David Kastrup
2006-08-04 15:46                 ` Peter Dyballa
     [not found] ` <mailman.4791.1154598769.9609.help-gnu-emacs@gnu.org>
2006-08-03 10:05   ` std
2006-08-03 10:18     ` std
2006-08-03 11:26       ` Peter Dyballa
     [not found]       ` <mailman.4795.1154604386.9609.help-gnu-emacs@gnu.org>
2006-08-03 12:08         ` std [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

  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=1154606929.961508.191630@m79g2000cwm.googlegroups.com \
    --to=stdecara@gmail.com \
    /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).