unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Eichwalder <keichwa@gmx.net>
Cc: Kenichi Handa <handa@m17n.org>,
	emacs-devel@gnu.org, Dave Love <d.love@dl.ac.uk>
Subject: Re: po.el: line up po-compat.el (gettext)
Date: Sat, 02 Nov 2002 17:43:46 +0100	[thread overview]
Message-ID: <shheez6hx9.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <200210011425.g91EPIw18223@rum.cs.yale.edu> ("Stefan Monnier"'s message of "Tue, 01 Oct 2002 10:25:18 -0400")

"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

> But in light of the above I suggest we also try
>
>   (coding-system-p (intern-soft (subst-char-in-string ?_ ?- charset-lower)))

[...]

> Obviously this sync issue is very relelvant and it's for you to decide
> what's the best option from a maintainability POV.
> I suggest the patch below, but it trims down the explicit list whereas
> the current list keeps redundant entries (entries that would already
> be found by the (intern-soft charset-lower) in the code).

Thanks for your work!  I just saw that Dave checked in something along
your lines.

I guess in the long run the coding detection code can go into mule.el
as one of the auto-coding-functions.

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

      reply	other threads:[~2002-11-02 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27  5:37 po.el: line up po-compat.el (gettext) Karl Eichwalder
2002-09-27 15:12 ` Stefan Monnier
2002-09-27 15:41   ` Karl Eichwalder
2002-09-28  3:20   ` Richard Stallman
2002-10-01  2:45     ` Kenichi Handa
2002-10-01  4:42       ` Karl Eichwalder
2002-10-01 14:25         ` Stefan Monnier
2002-11-02 16:43           ` Karl Eichwalder [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=shheez6hx9.fsf@tux.gnu.franken.de \
    --to=keichwa@gmx.net \
    --cc=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).