Summary: | TVT: Externalized Strings to be removed from .properties file | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Hwa Truong <truonghw> |
Component: | Core | Assignee: | David Audel <david_audel> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | critical | ||
Priority: | P3 | CC: | camle, Kevin_Haaland |
Version: | 2.1 | ||
Target Milestone: | 2.1 RC2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Hwa Truong
2003-02-24 13:20:29 EST
This problem was logged against translation of 2.0.2. However, after analysing the problem, we realized that strings which should not be externalized for translation had been put into file codegenerationmessages.properties of directory eclipse\plugins\org.eclipse.jdt.ui_2.0.2 \jdt_jar\org\eclipse\jdt\internal\corext\codemanipulation Please ensure that the 3 keywords are being removed from the .properties file for eclipse 2.1 so that the translation centers will not make a mistake of translating them. NameProposer.getterPrefix=get NameProposer.queryPrefix=is NameProposer.setterPrefix=set If we remove this from the properties file JDT/UI will always suggest setter and getters of the form: setValue, getValue. If the field identifier is not written in English but in German you will get setWert and getWert which is funny as well. The NamePropser class is no longer in use in JDT/UI. Removed keys form JDT/UI land. Moving to JDT/Core since they are now doing name proposing. David - pls verify that these strings are indeed externalized. Actually, these Strings should NOT be externalized as per original request. Currently these Strings are not externalized. Closing. |