unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Editing exportet registry files
Date: Fri, 1 Jul 2005 20:01:14 +0200	[thread overview]
Message-ID: <f7ccd24b050701110167c72609@mail.gmail.com> (raw)
In-Reply-To: <85vf3ul8sj.fsf@lola.goethe.zz>

On 7/1/05, David Kastrup <dak@gnu.org> wrote:

> Shouldn't the utf-x files with signature be quite in front of the list
> of detected coding systems?  I mean, that's what the signature is good
> for in the first place, right?

Well, yeah, but FF and FE *are* valid characters in many encodings.
Latin encodings for most european language environments are going to
be higher up the priority list, for example. It makes no sense putting
utf-* encodings before the others unless you know beforehand that
you're going to deal with a lot of these files.

And there's an UTF-8 language environment, after all, for people who
routinely deals with utf-8 data. Are there environments (operating
systems, language environments, whatever) where utf-16 is the norm?

-- 
                    /L/e/k/t/u

  reply	other threads:[~2005-07-01 18:01 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 20:27 Editing exportet registry files Markus Gritsch
2005-06-30 21:23 ` Stefan Monnier
2005-07-01  7:12   ` gritsch
2005-07-01  8:17     ` Miles Bader
2005-07-01  8:24     ` Juanma Barranquero
2005-07-01 17:45       ` David Kastrup
2005-07-01 18:01         ` Juanma Barranquero [this message]
2005-07-01 18:52           ` Gaëtan LEURENT
2005-07-01 23:25             ` Juanma Barranquero
2005-07-01 22:12           ` Jason Rumney
2005-07-01 23:38             ` Juanma Barranquero
2005-07-02 11:50               ` Andreas Schwab
2005-07-02 14:33                 ` Juanma Barranquero
2005-07-03 19:52             ` Gaëtan LEURENT
2005-07-03 21:34               ` Jason Rumney
2005-07-03 21:48                 ` David Kastrup
2005-07-04  7:43               ` Kaloian Doganov
2005-07-03 19:58         ` Coding system priority (was: Editing exportet registry files) Gaëtan LEURENT
2005-07-01  8:28   ` Editing exportet registry files gritsch
  -- strict thread matches above, loose matches on Subject: below --
2005-07-01  9:02 Dhruva Krishnamurthy (RBIN/EDI3) *
2005-07-01  9:49 ` gritsch
2005-07-01 11:02   ` Mathias Dahl
2005-07-01 13:13     ` Juanma Barranquero
2005-07-02 14:50   ` Juanma Barranquero
2005-07-02 14:55     ` Juanma Barranquero
2005-07-02 16:07       ` Juanma Barranquero
2005-07-07  0:28         ` Juanma Barranquero
2005-07-07  6:25           ` Kenichi Handa
2005-07-07  9:09             ` Juanma Barranquero
2005-07-07  9:55               ` Juanma Barranquero
2005-07-07 12:36                 ` Kenichi Handa
2005-07-07 13:35                   ` Juanma Barranquero
2005-07-07 18:56                     ` Benjamin Riefenstahl
2005-07-07 19:34                       ` Gaëtan LEURENT
2005-07-07 21:32                         ` Benjamin Riefenstahl
2005-07-08  0:15                       ` Juanma Barranquero
2005-07-08  1:42                     ` Kenichi Handa
2005-07-11  9:37                       ` Juanma Barranquero
2005-07-08  1:52       ` Kenichi Handa

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=f7ccd24b050701110167c72609@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).