| Summary: | externalize string plugin - tries to add the catalog if it's already there | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> | ||||
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | ahunter.eclipse, Szymon.Brandys | ||||
| Version: | 0.5 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
yes, that was the problem. I replaced the default proposition i18n!messages with i18n!orion/navigate/nls/messages (the existing catalog name) and it's okay now. thanks for the tool, by the way! (In reply to comment #1) > yes, that was the problem. > I replaced the default proposition > i18n!messages > with > i18n!orion/navigate/nls/messages (the existing catalog name) > > and it's okay now. I'll fix it, but I don't think I'll have time in 0.5 We no longer use this method to external strings. |
Created attachment 216159 [details] screenshot showing two catalog entries maybe I'm misunderstanding how to use the new externalize string plugin, but when I tried to use the externalize strings page, it seemed to want to add a catalog definition even if I already had one. I wasn't sure what to put in the info on the left hand side, so perhaps that is part of the problem?