Bug 345165 - Special character replacement in extension xml should recognize already translated characters
Summary: Special character replacement in extension xml should recognize already trans...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
Depends on: 342512
Blocks:
  Show dependency tree
 
Reported: 2011-05-09 12:10 EDT by Curtis Windatt CLA
Modified: 2023-04-22 03:03 EDT (History)
3 users (show)

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 Curtis Windatt CLA 2011-05-09 12:10:02 EDT 
1) In a plug-in xml, select an extension that uses a label that can use mnemonics.
2) Change the label to 'TEST&ATEST' and save.
At this point the UI will show the label as TEST&ATEST while the xml should be TEST&ATEST
3) Change the label to 'TEST&ATEST' and save
Now the xml will be converted to 'TEST&ATEST'

The replacement is done in XMLInputContext.getWritableAttributeNodeValue which calls out to another utility method.  Rather than do a straight string replacement, the code should check whether the replacement has already been done.

What makes this worse for the user, is that extension point documentation often assumes you are editing the xml by hand.  It encourages you to enter & in the label.
Comment 1 Eclipse Genie CLA 2019-05-11 01:11:53 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2021-05-01 06:42:35 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-04-22 03:03:52 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.