Gnus development mailing list
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@myware.rz.uni-karlsruhe.de>
Cc: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>,
	ding@ifi.uio.no, Ulrich Drepper <drepper@gnu.ai.mit.edu>
Subject: Re: Internationalization
Date: 12 Nov 1996 02:57:23 +0100	[thread overview]
Message-ID: <x73eygm5x8.fsf@myware.rz.uni-karlsruhe.de> (raw)
In-Reply-To: pinard@progiciels-bpi.ca's message of 11 Nov 1996 16:35:44 -0500

pinard@progiciels-bpi.ca (François Pinard) writes:

> * Step 5.  Recreate a better gnus.pot file through the following command:
> 
> 	xgettext -drgnus -k_ -kN_ -kmessage *.el
> 
> and send it to me (or to gnu-translation@gnu.ai.mit.edu, it's the same
> address) the resulting gnus.pot file under a name like rgnus-0.63.pot.
> I'll then submit it to all translation teams for getting the translation
> of all messages done.  When I get translated PO files, I check them for
> formal correctness and, if OK, you semi-automatically get a copy.
> 
> Oops!  This is not right.  xgettext has not been changed yet to handle
> Emacs LISP sources.  OK, for now, just stick to the rgnus.po file which
> was generated while you were marking strings in step 3.  I'll push so
> xgettext gets adapted sooner, or I'll do it myself if it slows us down.

I'm still not sure how we should solve the problem of parsing
ELisp code.  For bash and gawk it is/will be solved by having the
programs themselves having the possibility to dump the strings:

	bash --dump-strings --po-format sh-script

will produce a well-formed PO file which can be read by xgettext.
So xgettext will simply call bash and read the result in a pipe.
The same will hopefully happen with gawk.

But what is about Emacs?  Is it reasonable to call Emacs this way and
if yes will RMS agree to do these changes?  Of course the LISP syntax
isn't really difficult to parse but exceptions like doc strings
complicate things again.  Is the scanner/parser code separateble?

> Nevertheless, an Emacs LISP implementation of gettext would be very useful
> as an interim measure, even if partial, before it gets integrated in Emacs
> for real.  If you do so, please keep in close contact with me, as it would
> be a wonderful thing for the GNU translation project.

Let me know before you start this, too.  It shouldn't be too
difficult to write the function is ELisp (at least if there is
the possibility to access the .mo files which are binary files).
In any case I should tell something about the upper-level things,
how to find the catalog file, the string itself etc.

-- Uli
--------------.       drepper@cygnus.com  ,-.   Rubensstrasse 5
Ulrich Drepper \    ,--------------------'   \  76149 Karlsruhe/Germany
Cygnus Support  `--'  drepper@gnu.ai.mit.edu  `------------------------


  reply	other threads:[~1996-11-12  1:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-11-10 15:31 Internationalization Lars Magne Ingebrigtsen
1996-11-10 17:05 ` Internationalization Andy Eskilsson
1996-11-10 17:51   ` Internationalization Kai Grossjohann
1996-11-10 19:02 ` Internationalization David Kågedal
1996-11-11  6:27   ` Internationalization Steinar Bang
1996-11-11 15:20   ` Internationalization Lars Magne Ingebrigtsen
1996-11-11  0:25 ` Internationalization visigoth
1996-11-11 15:25   ` Internationalization Lars Magne Ingebrigtsen
1996-11-11 22:19     ` Internationalization David Moore
1996-11-12 22:45       ` Internationalization Lars Magne Ingebrigtsen
1996-11-11 12:14 ` Internationalization Robert Bihlmeyer
1996-11-11 12:50 ` Internationalization Per Abrahamsen
1996-11-11 15:14   ` Internationalization William Perry
1996-11-11 15:24     ` Internationalization Per Abrahamsen
1996-11-11 22:01   ` Internationalization François Pinard
1996-11-12 10:58     ` Internationalization Per Abrahamsen
1996-11-12 15:59       ` Internationalization François Pinard
1996-11-12 16:57         ` Internationalization Ulrich Drepper
     [not found]           ` <rjwwvqgxz1.fsf@babbage.dina.kvl.dk>
     [not found]             ` <x7ralyf6rx.fsf@myware.rz.uni-karlsruhe.de>
     [not found]               ` <rj3eydhwx5.fsf@babbage.dina.kvl.dk>
1996-11-14 12:28                 ` Internationalization François Pinard
1996-11-12 22:07         ` Internationalization Lars Magne Ingebrigtsen
1996-11-13 19:19           ` Internationalization Jan Vroonhof
1996-11-13 22:05             ` Internationalization William Perry
1996-11-14 19:27               ` Internationalization Ralph Schleicher
1996-11-12 20:12   ` Internationalization Jan Vroonhof
1996-11-11 21:35 ` Internationalization François Pinard
1996-11-12  1:57   ` Ulrich Drepper [this message]
1996-11-12 19:56   ` Internationalization Lars Magne Ingebrigtsen
1996-11-12 22:40     ` Internationalization Ulrich Drepper
2002-10-20 21:21     ` Internationalization François Pinard
1996-11-17 22:59 ` Internationalization Ralph Schleicher

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x73eygm5x8.fsf@myware.rz.uni-karlsruhe.de \
    --to=drepper@myware.rz.uni-karlsruhe.de \
    --cc=ding@ifi.uio.no \
    --cc=drepper@gnu.ai.mit.edu \
    --cc=drepper@ipd.info.uni-karlsruhe.de \
    --cc=larsi@ifi.uio.no \
    /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 NNTP newsgroup(s).