From: Karl Eichwalder <keichwa@gmx.net>
Cc: rms@gnu.org, monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: po.el: line up po-compat.el (gettext)
Date: Tue, 01 Oct 2002 06:42:17 +0200 [thread overview]
Message-ID: <shu1k6zs5y.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <200210010245.LAA06580@etlken.m17n.org> (Kenichi Handa's message of "Tue, 1 Oct 2002 11:45:15 +0900 (JST)")
Kenichi Handa <handa@m17n.org> writes:
> I'm not sure. See these lines:
> ("ISO-8859-1" . iso-8859-1)
> ("ISO_8859-1" . iso-8859-1)
>
> We can't get rid of the second line.
Thanks for spotting these lines.
> And, Karl wrote:
>> Please apply the following cosmetical patch to line it up with the
>> po-compat.el file coming with GNU gettext:
>
> Doesn't this imply that there's a merit to keep those lines
> the same as what po-copmat.el has?
Yes, but I will always make sure the synch happens in both directions
(po.el (emacs) <-> po-compat.el (gettext)).
> I'd like to leave this issue to the maintainer(s) of po.el.
> I don't know how *.el in gettext is maintained, thus can't
> judge what is the right thing.
It's basically me (and Bruno Haible) who apply change to the *.el files
in gettext.
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.suse.de/~ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
next prev parent reply other threads:[~2002-10-01 4:42 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 [this message]
2002-10-01 14:25 ` Stefan Monnier
2002-11-02 16:43 ` Karl Eichwalder
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=shu1k6zs5y.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=rms@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).