Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 272641 - Externalize Strings for MANIFEST.MF should not put ".0" suffix on each header
Summary: Externalize Strings for MANIFEST.MF should not put ".0" suffix on each header
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.5 M7   Edit
Assignee: Chris Aniszczyk CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-17 02:54 EDT by Philipp Kursawe CLA
Modified: 2009-04-27 10:29 EDT (History)
1 user (show)

See Also:

Attachments
Initial patch (1.42 KB, patch)
2009-04-24 06:57 EDT, Philipp Kursawe CLA 		caniszczyk: iplog+
Details | Diff
View All 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 Philipp Kursawe CLA 2009-04-17 02:54:16 EDT 
Is there any particular reason to suffix each OSGI-Bundle header that is externalized from a MANIFEST.MF with ".0"? 
Bundle-Name becomes substituted as "Bundle-Name.0"
We always have to manually remove the ".0" suffix as there cannot be more than one Bundle-Name header anyway.
Would be nice if the Externalization-Wizard would just leave the substitution name untouched and keeps it equal with the bundle header name.
I could provide a patch.
Comment 1 Philipp Kursawe CLA 2009-04-24 06:57:10 EDT 
Created attachment 133096 [details]
Initial patch

Key name is now only suffixed with counter if plain keyname does already exist in bundle l10n.
Comment 2 Chris Aniszczyk CLA 2009-04-27 10:29:14 EDT 
done.

> 20090427