From: Karl Eichwalder <ke@gnu.franken.de>
Cc: emacs-devel@gnu.org, sanvila@unex.es, neil@darlow.co.uk,
haible@ilog.fr, handa@etl.go.jp
Subject: Re: PO files and Emacs
Date: Sun, 10 Mar 2002 06:29:06 +0100 [thread overview]
Message-ID: <sh7kolt2hp.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <200203100503.g2A53jS03926@wijiji.santafe.edu> (Richard Stallman's message of "Sat, 9 Mar 2002 22:03:45 -0700 (MST)")
Richard Stallman <rms@gnu.org> writes:
> Are you saying that this is a problem which po.el does not handle and
> that we need to fix?
It was my intention to describe the PO file format informally.
> The other messages don't seem to describe an outstanding problem.
> They seem to describe a file that already works fine.
Yes. The feature request is to add po.el to Emacs---is this possible?
The code is already disclaimed, since it's basically distributed with
GNU gettext and the algorithms ware invented by François and Bruno.
Then some updates (check list of available encodings) or minor fixes are
necessary (change encoding from UTF-8 to something else; UTF-8 is only
used for po.el because of 1 "ç" inside of a comment string).
When po.el is installed I'll help to test it.
--
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/ | (*)/'(*)
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-10 5:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 14:11 PO files and Emacs Karl Eichwalder
2002-03-10 5:03 ` Richard Stallman
2002-03-10 5:29 ` Karl Eichwalder [this message]
2002-03-11 9:00 ` Richard Stallman
2002-03-11 11:03 ` Eli Zaretskii
2002-03-11 17:54 ` Karl Eichwalder
2002-03-11 19:29 ` Andreas Schwab
2002-03-11 20:02 ` Karl Eichwalder
2002-03-12 5:53 ` Eli Zaretskii
2002-03-12 13:41 ` Bruno Haible
2002-03-12 15:53 ` Kim F. Storm
2002-03-12 16:25 ` Karl Eichwalder
2002-03-12 17:19 ` Bruno Haible
2002-03-12 17:20 ` Bruno Haible
2002-03-15 13:53 ` Eli Zaretskii
2002-03-16 3:41 ` Karl Eichwalder
2002-03-12 17:17 ` Eli Zaretskii
2002-03-15 13:54 ` Eli Zaretskii
2002-03-10 11:10 ` Neil Darlow
2002-03-11 5:46 ` Eli Zaretskii
2002-03-11 6:45 ` Karl Eichwalder
2002-03-11 6:53 ` Eli Zaretskii
2002-03-12 13:30 ` Bruno Haible
2002-03-15 13:29 ` Eli Zaretskii
2002-03-15 18:43 ` Bruno Haible
2002-03-16 4:36 ` Karl Eichwalder
2002-03-16 9:26 ` Eli Zaretskii
2002-03-16 13:05 ` Karl Eichwalder
2002-03-16 17:29 ` Eli Zaretskii
2002-03-16 18:41 ` Karl Eichwalder
2002-03-17 4:35 ` Eli Zaretskii
2002-03-17 5:26 ` Karl Eichwalder
2002-03-17 11:40 ` Patch for GNU gettext (Re: PO files and Emacs) Karl Eichwalder
2002-03-17 11:42 ` PO files and Emacs Eli Zaretskii
2002-03-16 10:39 ` Alex Schroeder
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 8:44 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=sh7kolt2hp.fsf@tux.gnu.franken.de \
--to=ke@gnu.franken.de \
--cc=emacs-devel@gnu.org \
--cc=haible@ilog.fr \
--cc=handa@etl.go.jp \
--cc=keichwa@gmx.net \
--cc=neil@darlow.co.uk \
--cc=sanvila@unex.es \
/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).