Bug 232391

Summary: TVT34:TCT289: JA: "In" in English in JavaScript Library ->Global Supertype panel
Product: [WebTools] JSDT Reporter: CDE Administration <cdeadmin>
Component: GeneralAssignee: Bradley Childs <childsb>
Status: RESOLVED FIXED QA Contact: Phil Berkland <berkland>
Severity: normal    
Priority: P1 CC: camle, david_williams, hjzhang, kaloyan, kitlo, neil.hauge
Version: 3.0Flags: david_williams: pmc_approved+
childsb: pmc_approved? (raghunathan.srinivasan)
childsb: pmc_approved? (naci.dai)
childsb: pmc_approved? (deboer)
neil.hauge: pmc_approved+
kaloyan: pmc_approved+
berkland: review+
Target Milestone: 3.0 RC4   
Hardware: PC   
OS: Linux-GTK   
URL: 289
Whiteboard: PMC_approved
Attachments:
Description Flags
3.001580_ja.gif
none
patch to externalize "() in" string
none
better patch using best practice as suggested. kaloyan: review+

Description CDE Administration CLA 2008-05-15 15:20:23 EDT
<response_by> Eriko Takahashi at 2008.05.15.09.12.19 </response_by>
OS: Linux
Build date: 0514
Component/Functoin name:WTP
Blocking:NO
Language: Japanese
Tester Name: Eriko Takahashi

Steps to recreate the problem:
1. Create Static Web Project.
2. Right click on the Project created, and select ?Properties?
2. Expand the JavaScript node.
3. click on Javascript Libraries
4. Click on Global Supertype tab

Problem description:
The description in the field at the very bottom of the Global Supertype tab says "*** in xxx" (eg. "Window () in ECMA 3

browser support").

I believe "***" and "xxx" part are externalized, but not the word, "in".
Could you provide the text, "*** in xxx " as one string so we can translate it properly?

Thank you.
Eriko Takahashi

<response_by> Matthew Mazaika at 2008.05.15.13.43.17 </response_by>
This article was reassigned from Category:''TVT/Testing,Inbox''.
Comment 1 CDE Administration CLA 2008-05-15 15:20:31 EDT
Created attachment 100528 [details]
3.001580_ja.gif
Comment 2 CDE Administration CLA 2008-05-15 15:20:38 EDT
<cde:tctdetail>
Testcase: 3.001580
Project: WSW34
Component: Xfer - Web Tools/jst.server
Priority: 3
Subject: JA: "In" in English in JavaScript Library ->Global Supertype panel
Article ID: 289
Originator: ERIKOT@jp.ibm.com
</cde:tctdetail>
Comment 3 Tim deBoer CLA 2008-05-15 15:26:40 EDT
Moving to correct component.
Comment 4 CDE Administration CLA 2008-05-21 10:28:33 EDT
<response_by> YoungSun Ko at 2008.05.21.09.14.47 </response_by>
Same for Korean.

thanks,
Youngsun
Comment 5 Bradley Childs CLA 2008-05-29 11:46:51 EDT
Created attachment 102670 [details]
patch to externalize "() in" string
Comment 6 Bradley Childs CLA 2008-05-29 11:49:16 EDT
i've updated with a patch. 

i don't believe this bug's severity is major or that it's necessary for 3.0.  i'm going to move severity to normal and target the fix at 3.01
Comment 7 Bradley Childs CLA 2008-06-04 13:57:46 EDT
Re-targeting/requesting PMC approval for 3.0RC4 per request of Cam-Thu T. Le (camle@us.ibm.com) on June 04.
Comment 8 Phil Berkland CLA 2008-06-04 14:46:08 EDT
looks ok to me
Comment 9 David Williams CLA 2008-06-04 14:57:34 EDT
I think we need to get in all the "externalized string" problems we can, as that leaves the code in an "untranslatable state" until it's fixed. And ... there's already a lot of "lead time" required for translations. 

This will help the Eclipse Babel Project be able to do what it needs to (based on community participation), as well as any specific adopters that want to do translations. 

And, IMHO, we often under prioritize these issues, because, after all ... we can read them :) (that is, it's hard for many of us to empathize with non-English speakers.). 

Comment 10 Bradley Childs CLA 2008-06-05 11:17:38 EDT
Patch applied to HEAD.

Thanks.
Comment 11 Kaloyan Raev CLA 2008-06-05 12:42:48 EDT
Bradley, please note that for RC4 it is required three positive votes by PMC - not two. 

I see a problem with the proposed patch. It still maintains the bad i18n practice. This is the proposed fix:

-		return superTypeName + "() in " + getLibraryName(); //$NON-NLS-1$
+		return superTypeName + Messages.getString("LibrarySuperType.0") + getLibraryName(); //$NON-NLS-1$

+LibrarySuperType.0=() in 

A much better solution would be:

-		return superTypeName + "() in " + getLibraryName(); //$NON-NLS-1$
+		return Messages.getString("LibrarySuperType.0", new Object[] {superTypeName, getLibraryName()}); //$NON-NLS-1$

+LibrarySuperType.0={0}() in {1}

This way you give the freedom to the translator to change the order of words in the whole string if needed. It is almost guaranteed that there is a language on the earth that will require this. 
Comment 12 Kaloyan Raev CLA 2008-06-05 14:26:48 EDT
Bradley, please go on and correct your latest changes in CVS. Just make sure that you attach the new patch in bugzilla, so I have a look at it. 
Comment 13 Bradley Childs CLA 2008-06-05 14:47:51 EDT
Created attachment 103800 [details]
better patch using best practice as suggested.
Comment 14 Kaloyan Raev CLA 2008-06-05 14:53:50 EDT
Comment on attachment 103800 [details]
better patch using best practice as suggested.

great
Comment 15 Bradley Childs CLA 2008-06-09 11:21:18 EDT
applied patch.

Comment 16 CDE Administration CLA 2008-06-13 10:48:02 EDT
<response_by> Matthew Mazaika at 2008.06.13.09.23.31 </response_by>
It doesn't look like this will make it in by the end of TVT.  It may make it in for 3.4, but will most likely be deferred until the first maintenance release.