Bug 51767 - I18N: Optimize CSearchMessages.properties
Summary: I18N: Optimize CSearchMessages.properties
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-11 15:59 EST by Tanya Wolff CLA
Modified: 2020-09-04 15:24 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tanya Wolff CLA 2004-02-11 15:59:41 EST
To reduce the number of strings to translate, many property values can be 
associated with a single key.
Ie
Search.Error.search.title=Search Error 
Search.Error.javaElementAccess.title=Search Error

can be replaced with
Search.Error.Search_Error=Search Error

The duplicate property values with only a difference in plurality can be merged 
into one, by implementing ChoiceFormat along with MessageFormat in the code.

The strings that are not externalized for Search are the scope strings in the 
search dialog (Scope, Workspace, Selected Resource, Working Set) and the (# 
matches) output in the Search Results view.
Comment 1 Bogdan Gheorghe CLA 2004-06-17 19:15:34 EDT
Since the translations are done, I think we can close this one. Tanya?
Comment 2 Tanya Wolff CLA 2004-06-18 10:08:34 EDT
"(1 match)" in the search results pane is still not translated, unless it's 
outside of CDT. If so we can close this, but since this string exists in 
CSearchMessages.properties, either take it out if it's not being used or let me 
know where it is so I can check the translation. Thanks.
Comment 3 Tanya Wolff CLA 2004-06-23 10:26:13 EDT
Reopening to see if the "1 match" is something we can fix.
Comment 4 Kleo Hapitas CLA 2004-07-07 16:54:25 EDT
PR was not targeted to any particular release. Changing target milestone to 2.1