Closed Bug 228004 Opened 21 years ago Closed 15 years ago

Use Altavista (Babel Fish) for automatic page translation [babelfish]

Categories

(SeaMonkey :: UI Design, enhancement)

Product:
SeaMonkey
Component:
UI Design
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: guanxi_i, Assigned: jag+mozilla)

References

Details

Altavista's Babel Fish translates more languages than Google, the current choice. I have javascript bookmarklets that implement Altavista transations (see below), so I believe it would be easy to implement. I'd also be in favor of anything that translates more languages than Altavista. Also, Google and Altavista translate almost exclusively to/from English (see below), something that translates between other language pairs would be useful. USEFUL NOTES: * Links to the two services: http://www.google.com/language_tools http://babelfish.altavista.com * Both Google and Altavista translate these to English: French, German, Italian, Portugese, Spanish, (& German to/from French) Only Altavista translates these to English: Chinese, Japanese, Korean, Russian * Automatic page translation was re-implemented in bug 135181. * This page has translation javascript bookmarklets doing translation fiva Altavista, and some documentation on them. They don't work perfectly for me (need two clicks, not one), but it's useful background: http://www.joemaller.com/translation_bookmarklets.shtml * This page has excellent Altavista translation javascript bookmarklets that translate the text in situ -- the text automagically changes from (e.g. French) to English, without loading another page or losing formatting. (see bottom right): http://tantek.com/favelets/ Finally, I wasn't sure which component to use, but bug 135181 used XP Apps, so I went with it.
I should add this excerpt from Alex Bishop in the bug re-implementing auto page translation: http://bugzilla.mozilla.org/show_bug.cgi?id=135181#c60 >> AltaVista's BabelFish does more languages but its URL format requires the presence of both a source and target language: http://babelfish.altavista.com/babelfish/tr?lp=fr_en&tt=url&url= Without the lp parameter, it goes to http://babelfish.altavista.com/babelfish/tr with the URL prefilled in the form (not exactly seamless but not terrible either). <<
Babel Fish has significantly widened its lead. Updated comparison: BABEL FISH (ALTAVISTA) GOOGLE ---------------------- ------ Chinese-simp to English Chinese-trad to English English to Chinese-simp English to Chinese-trad English to Dutch English to French English to French English to German English to German English to Greek English to Italian English to Italian English to Japanese English to Korean English to Portuguese English to Portuguese English to Russian English to Spanish English to Spanish Dutch to English Dutch to French French to English French to English French to German French to German French to Greek French to Italian French to Portuguese French to Dutch French to Spanish German to English German to English German to French German to French Greek to English Greek to French Italian to English Italian to English Italian to French Japanese to English Korean to English Portuguese to English Portuguese to English Portuguese to French Russian to English Spanish to English Spanish to English Spanish to French
*** Bug 267565 has been marked as a duplicate of this bug. ***
Well?
Product: Core → Mozilla Application Suite
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.