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

Bug 177541

Summary:	NLS33:translation questions
Product:	[Eclipse Project] JDT	Reporter:	Brent Hepburn <bahepbur>
Component:	Debug	Assignee:	Michael Rennie <Michael_Rennie>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.3
Target Milestone:	3.3 M6
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Brent Hepburn

2007-03-15 09:24:01 EDT

Build ID: eclipse-JDT-SDK-3.3M5eh.zip

filename: 
eclipse\plugins\org.eclipse.jdt.debug\jdimodel_jar\org\eclipse\jdi\internal\JDIMessages.properties 

sentence: 
getValues not allowed on array

Translators Question: 
"getValues" here means the get values operation, right? Translatable or not? Would you pls confirm it?

Comment 1 Michael Rennie

2007-03-15 10:01:43 EDT

yup

Comment 2 Darin Wright

2007-03-15 10:05:59 EDT

This is actually an internal error that should not be translated (i.e. indicates a programming problem). We should remove the string from the properties file, and have it hard coded in the class.

Comment 3 Michael Rennie

2007-03-15 10:29:44 EDT

This doesn't change the fact that the answer to the original question of '"getValues" here means the get values operation, right?' is still yes :)

I have opened two other bugs to track us removing NLS'd strings that should not be NLS'd

platform: 177554
JDT: 177556

Comment 4 Darin Wright

2007-03-15 10:37:40 EDT

sure... but the important thing is that this is *not* translatable.

Comment 5 Darin Wright

2007-03-15 15:11:37 EDT

It turns out that many of these JDI error messages can appear as the "underlying cause" or "detail" message of an exception. So, we may want them to be translated. I have fixed this message to read: "get values not allowed on array".

Comment 6 Darin Wright

2007-03-15 15:11:48 EDT

Please verify, Mike.

Comment 7 Michael Rennie

2007-03-16 15:13:54 EDT

verified

Comment 8 Brent Hepburn

2007-03-16 15:27:34 EDT

Replied to translation center.