Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 426943

Summary: Unexternalized strings for Getting Started
Product: [ECD] Orion Reporter: Kit Lo <kitlo>
Component: ServerAssignee: Project Inbox <orion.server-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: ahunter.eclipse, maciej.bendkowski, mamacdon
Version: 5.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Getting Started menu
none
Getting Started dialog none

Description Kit Lo CLA 2014-01-29 15:50:40 EST
Created attachment 239443 [details]
Getting Started menu
Comment 1 Kit Lo CLA 2014-01-29 15:51:18 EST
Created attachment 239444 [details]
Getting Started dialog
Comment 2 Bartosz Grabski CLA 2014-02-17 07:24:52 EST
Proposed fix

https://git.eclipse.org/r/#/c/22088/
Comment 3 Bartosz Grabski CLA 2014-02-17 07:26:39 EST
Proposed fix

https://git.eclipse.org/r/#/c/22088/
Comment 4 Mark Macdonald CLA 2014-02-19 15:36:25 EST
The proposed fix loads message bundles directly from plugin code (pageLinksPlugin). This is not going to work (see here: https://wiki.eclipse.org/Orion/Internationalization#Plugins )

Instead we must add support for translation to the "orion.page.getstarted" service. pageLinksPlugin should provide a "nls" bundle and "labelKey" field, and the UATaskPanel should be responsible for loading the bundle and looking up the translated string for the labelKey.
Comment 5 Maciej Bendkowski CLA 2014-02-20 07:33:14 EST
(In reply to Mark Macdonald from comment #4)
> Instead we must add support for translation to the "orion.page.getstarted"
> service. pageLinksPlugin should provide a "nls" bundle and "labelKey" field,
> and the UATaskPanel should be responsible for loading the bundle and looking
> up the translated string for the labelKey.

As for this particular bug the suggested solution is fine, I think we're missing a more general case of external plugin string externalization. The current il18n framework puts the responsibility of loading translation bundles on the plugin consumer. Moreover, the plugin has no notion of "current locale" and can't obtain it from Orion. I'll open a separate bug for this discussion.
Comment 6 Anthony Hunter CLA 2015-05-08 09:24:23 EDT
The getting started dialog and menu no longer exists.