Bug 75065 - Externalize Strings does not use Value as DefaultValue in Key
Summary: Externalize Strings does not use Value as DefaultValue in Key
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2004-09-27 03:43 EDT by Georg Sendt CLA
Modified: 2009-08-30 02:08 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Georg Sendt CLA 2004-09-27 03:43:03 EDT 
Version 3.1 Build 200408122000 Linux Motif

Externalize String does not use Value as default value in Key instead it uses
prefix + numbers to distinct the different keys. This is very cumbersome if you
have lots of strings to externalize and you want to use the Value as
defaultvalue in 99% of all cases. As far as I remember ;) this was the default
behaviour in eclipse 2.x.

Example: 

Prefix: NewsEditPanel.

current behaviour:

Value     |    Key
-----------------------------
Title     | NewsEditPanel.0
Text      | NewsEditPanel.1

wanted behaviour:

Value     |    Key
-----------------------------
Title     | NewsEditPanel.Title
Text      | NewsEditPanel.Text
Comment 1 Martin Aeschlimann CLA 2004-10-08 06:10:44 EDT 
The problem with the old behaviour is that keys got very long. People had keys
like 'MyPage.do_you_really_want_to_delete_project_and_content?'.
We want to encourrage shorter names as all these keys will also be loaded at
runtime and take considerable amount of memory.

No plan to change that for 3.1
Comment 2 Denis Roy CLA 2009-08-30 02:08:45 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.