Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 358419

Summary:	[ui] Plugin installation dialogs have untranslated text
Product:	[Eclipse Project] Equinox	Reporter:	Mark Ingamells <mark.ingamells>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	pascal, remy.suen, tjwatson
Version:	3.6.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Mark Ingamells

2011-09-21 10:02:38 EDT

Build Identifier: 3.6.2.201106161553

While defining and installing a plugin to an RCP, the error messages and the "Installing Software" dialog contain English text, even though most other fields and buttons are in the local language.

Reproducible: Always

Steps to Reproduce:
1.Change to non-English locale (e.g. Chinese) and start RCP
2.Menu - Help -> "Install new software..."
3."Add.." button
4.In Location text box type "ftp" - untranslated error of "Location must be absolute"
5.Enter a valid location and press "OK"
6."Add.." button again
7.Enter the same location again -  untranslated error of "Duplicate location"
8.Cancel dialog and select the plugin to install, except licenses etc.
9.Installing Software dialog has untranslated title and test of "Installing Software"
10.Once installed and restarted, trying to install the same plugin again gets a translated error message in the "Install Details" dialog, but the details section contains the untranslated message:
Cannot complete the request.  See the error log for details.
"<Translated product name here>" will be ignored because it is already installed.

Comment 1 DJ Houghton

2011-09-21 11:01:46 EDT

Since non-English language translations are not shipped with Eclipse, I assume you're getting your translations from Babel? If so, which Babel version did you download? Also, does this problem happen in the Indigo (3.7) release?

Comment 2 Eclipse Genie

2019-09-20 14:35:13 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.