| Summary: | Globalization of plugins | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Component: | Client | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Szymon.Brandys |
| Version: | 0.4 | ||
| Target Milestone: | 0.5 RC1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 374414, 375700 | ||
|
Description
Malgorzata Janczarska
The POC for globalization of plugins is in branch Bug376148. It has the same problems as in Bug 375700 so I wait with merging in until I get some review on Bug 375700. I discovered that when locale changes plugins need to be reloaded. I opened bug 376207 for that. I pushed changes that add string extrenalization for two plugins: pageLinksPlugin.html and landingPageTasksPlugin.html. There is a tool that does not require dojo or reqjire.js, but consumes the same message format as them. The technology has changed and we need to change the loading of strings. The solution here is easy, but I run out of time for it. I'll do it first thing in RC1. We changed the approach. The plugins may now use our messages, if they know the exact messages file location. All plugin needs to supply is to add "nls" property with the messages module path, for instance "nls: 'orion/nls/messages'". If this property is added then "name" and "tooltip" are treated as messages ids instead of being displayed as they are. This approach is used in plugins delivered with Orion. For other plugins they may use the same approach if Orion contains all messages they need. They as well may localize their messages as they want on their site, according the browser locale. Bug 376207 is no longer blocking this task because messages are now localiezed on the client site. |