From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Internationalization
Date: 11 Nov 1996 16:25:20 +0100 [thread overview]
Message-ID: <m2ybg81wnz.fsf@proletcult.ifi.uio.no> (raw)
In-Reply-To: visigoth@naiad.fac.cs.cmu.edu's message of 10 Nov 1996 19:25:42 -0500
visigoth@naiad.fac.cs.cmu.edu writes:
> This sounds like an interesting way to start--I suspect that it would
> be useful after a time to move the English version out to a file as
> well. So you would have something like:
>
> (in gnus-art.el, lines around 386:)
>
> (format prompt (if (and gnus-number-of-articles-to-be-saved
> (> gnus number-of-articles-to-be-saved 1))
> (format (gnus-get-trans 'these-articles)
> gnus-number-of-articles-to-be-saved)
> (gnus-get-trans 'this-article)))
>
> On the other hand--that's really damned ugly.
Well, even the English versions could be translations from the
strings. So the source code wouldn't change (except for adding lots
of `gnus-get-trans'es around all the strings), and the first
translation would just be an indentity translation, but afterwards, if
I want to change the English version of the text, I'd have to edit the
English "translation" file.
> And the real problem, unfortunately, is documentation strings.
That's true. They're difficult to do anything about without changing
the internals somewhat. Not all that difficult, though -- you just
have to fiddle with the `documentation' function somewhat.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1996-11-11 15:25 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 ` Lars Magne Ingebrigtsen [this message]
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 ` 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=m2ybg81wnz.fsf@proletcult.ifi.uio.no \
--to=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).