Closed Bug 123064 Opened 23 years ago Closed 15 years ago

view->translate loads a useless site - make customizable?

Categories

(SeaMonkey :: UI Design, enhancement)

x86
Windows NT
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED
Future

People

(Reporter: sds, Assigned: trudelle)

References

()

Details

when I click on view->translate, I am taken to a site other than the altavista babelfish which is useless: it cannot translate text (only web pages), and even there the interface is broken. can't that location be made customizable? (e.g., I want babelfish!) also, right next to view->translate there should be view->dictionary (pointing to, say, www.m-v.com).
Sev: nor -> enh
Severity: normal → enhancement
To XP Apps. That said, the translator in question usually does a better job than babelfish.... (and it _is_ in the menu so you can translate your current page, btw).
Assignee: mpt → trudelle
Status: UNCONFIRMED → NEW
Component: User Interface Design → XP Apps
Ever confirmed: true
QA Contact: zach → sairuh
->future
Target Milestone: --- → Future
The location is customisable - check your prefs.js. It's not completely trivial to change; I can't remember if the comments I added explaining how to do it are still there. Gerv
prefs.js does not have teletranslator how do I customize it then?
"I am taken to a site other than the altavista babelfish which is useless: it cannot translate text (only web pages)," Well, that I would not consider a bug, not even a design issue: View|Translate means displaying a different view (like source, info) of the current document, like a translation.
so? what if I prefer a different translator? why have such a fleeting entity as a URL hardwired?!
Sam: To which comment are you replying?
yours. hardwiring a URL is a design issue, IMO.
Well, I was specifically talking about "it cannot translate text (only web pages)". It thought my comment made that clear.
Again, the URL is not hardwired. Search lxr.mozilla.org for teletranslator to find the appropriate pref names. Gerv
There's browser.translation.service and browser.translation.serviceDomain
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.