Gnus development mailing list
 help / color / mirror / Atom feed
From: William Perry <wmperry@aventail.com>
Cc: ding@ifi.uio.no
Subject: Re: Internationalization
Date: Mon, 11 Nov 1996 07:14:33 -0800	[thread overview]
Message-ID: <199611111514.HAA17526@newman.in.aventail.com> (raw)
In-Reply-To: <rjeni0lrs7.fsf@babbage.dina.kvl.dk>

Per Abrahamsen writes:
>
>
>I hate the whole idea, but if it *must* be done I think there should
>be at least these requirements:
>
>* It must not be Gnus specific.

  Correct.

>* There should be _zero_ overhead for a user of the English version.

  Well, I would rephrase this to be 'zero overhead for a user of the
originating language version'.  If lars all of a sudden decides to only
speak french (even in lisp), then so be it. :)

>* There should be _zero_ new stuff to learn for an English speaking
>  programmer.

  similar rephrasing to point #2.

>I suggested this implementation when someone wanted to make a French
>version of AUC TeX.  It follows all 3 requirements.
>
>;;; trans-fr.el --- French translation of message strings
>
>;;; Code:
>
>(fset 'raw-message (symbol-function 'message))
> 
>(defvar translate-message-alist
>  '(("hello" "bonjour")))
> 
>(defun translate-message (format &rest args)
>  (let ((trans (assoc format translate-message-alist)))
>    (apply 'raw-message (or (nth 1 trans) format) args)))
> 
>(fset 'message (symbol-function 'translate-message))

  You would have to hook more than 'message'.  You would definitely have to
hook error, and possible a few other places.  And any custom format-like
functions would have to be modified by the package author as well.

  I like the gettext() approach, and have been considering something
similar in Emacs-W3 for a while, just haven't gotten around to it.

-bill p.


  reply	other threads:[~1996-11-11 15:14 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   ` William Perry [this message]
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   ` Internationalization Ulrich Drepper
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=199611111514.HAA17526@newman.in.aventail.com \
    --to=wmperry@aventail.com \
    --cc=ding@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).