Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: babelgnus
Date: 14 Jun 1999 02:57:32 +0200	[thread overview]
Message-ID: <m3lndnk39f.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Karl Kleinpaste's message of "13 Jun 1999 09:28:32 -0400"

Karl Kleinpaste <karl@justresearch.com> writes:

> I think that the babel service will go away entirely if it's made so
> ubiquitously accessible in reading interfaces.

Well, babelfish seems to have gone away already.  :-(  The host seems
totally dead at the moment.

Anyway, the "Babelfish tool page" (if I remember correctly) detailed
how to install an automatic translator into Mozilla and MSIE based on
babelfish.  I think it added a plugin that adds a button to the
toolbar that would translate the current page.

I think the impact of Gnus users compared to that would be
negligible. 

> Once Gnus is able to do such a thing, one can only wonder how long
> before Netscrape and Internet Exploder plug-ins will become available
> to do the same thing.

:-)  

> There is after all a heavy feature-copying mentality in such stuff.
> (Recall why Gnus gained smilification.)

Er...  Remind me.  I thought it was because Wes wrote the code.  :-)

> Keeping translation as a manual request for a single article should be
> the way to go.  Auto-translating whole hierarchies will just hurt us,
> on a social level.  Those reading national hierarchies should in
> general be capable in the subject language.

They should, but...  For instance, there are quite a lot of people who
work in Norway (for shorter or longer time) who don't speak
Norwegian.  These get along well verbally if the speak English, but
they can't read the Norwegian newsgroups.  Wouldn't it be neat if they 
could?  (Babelfish doesn't do Norwegian, but, like.)  

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  parent reply	other threads:[~1999-06-14  0:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-28  7:45 babelgnus Steinar Bang
1999-05-28  8:10 ` babelgnus David Hedbor
1999-05-28 13:41 ` babelgnus Eric Marsden
1999-05-28 19:25   ` babelgnus Per Abrahamsen
1999-05-28 20:29     ` babelgnus Stainless Steel Rat
1999-06-01 11:00       ` babelgnus Robert Bihlmeyer
1999-06-01 16:12         ` babelgnus Hans de Graaff
1999-06-02 11:26           ` babelgnus Robert Bihlmeyer
1999-06-02 16:19           ` babelgnus Jan Vroonhof
1999-06-13  0:45     ` babelgnus Lars Magne Ingebrigtsen
1999-06-13 16:57       ` babelgnus Eric Marsden
1999-06-14  0:59         ` babelgnus Lars Magne Ingebrigtsen
1999-06-14  2:50           ` babelgnus William M. Perry
1999-06-15 15:24         ` babelgnus Eric Marsden
1999-06-15 16:23           ` babelgnus Toni Drabik
1999-06-16  7:04           ` babelgnus Jaap-Henk Hoepman
     [not found]     ` <yaau2sc6asf.fsf@tyrfing.ifi.uio.no>
1999-06-13  7:03       ` babelgnus Lars Magne Ingebrigtsen
1999-06-13 13:28         ` babelgnus Karl Kleinpaste
1999-06-13 18:59           ` babelgnus Per Abrahamsen
1999-06-14 17:36             ` babelgnus Shaun Lipscombe
1999-06-14  0:57           ` Lars Magne Ingebrigtsen [this message]
1999-06-13  4:49   ` babelgnus Lars Magne Ingebrigtsen
1999-06-13 17:38     ` babelgnus Eric Marsden

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=m3lndnk39f.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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.
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).