Bug 458798 - Camel case and underscores in translation keys are handled unintuitively by e4 translation service
Summary: Camel case and underscores in translation keys are handled unintuitively by e...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: 4.5 M6   Edit
Assignee: Dirk Fauth CLA
QA Contact:
URL:
Whiteboard:
Keywords: greatfix
Depends on:
Blocks:
 
Reported: 2015-01-30 04:42 EST by Ragnar Nevries CLA
Modified: 2015-03-16 07:46 EDT (History)
1 user (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 Ragnar Nevries CLA 2015-01-30 04:42:28 EST 
If your @Messages class has a field named 'camelCase_Subtree', then at the moment the appropriate ressource bundle is browsed for the keys
  camelCase_Subtree
  camel_case__subtree
  camel.case..subtree
and nothing else.

I suggest to also look for the keys
  camelCase.Subtree
  camel_case._subtree

Background:
I have @Messages classes that provide strings for several java classes and my convention is to name the fields javaClass_StringDescription. If I replace the underscores by dots in the ressource bundle, the actual algorithms fails to find by keys.
Comment 1 Ragnar Nevries CLA 2015-01-30 04:51:31 EST 
Made an implementation as suggested:

https://git.eclipse.org/r/40695
Comment 3 Lars Vogel CLA 2015-03-16 07:46:26 EDT 
.