Bugzilla – Full Text Bug Listing
| Summary: | [NLS] use correct .properties files | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Benjamin Wolff <eclipse> |
| Component: | JFace | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | b.muskalla, batxut, fr.appel, stefan.roeck |
| Version: | 1.2 | ||
| Target Milestone: | 1.3 M2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Benjamin Wolff
The additional dialogmessages.properties was due to the way RAP handles message bundles. Fixed this by assigning the keys "by hand" to the corresponding dialog labels. This is the same way as done in JFace, just at another point in time. Deleted the dialogmessages.properties as this is no longer needed. But in the end, I think it's easier to use the rap-specific NL bundles from babel as you don't need to adjust the fragment hosts for these. Using the latest CVS HEAD Plug-ins, i get the following error for the org.eclipse.rap.iu Plug-in: Description Resource Path Location Type Key 'category.edit.description' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 668 Plug-in Problem Key 'category.file.description' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 664 Plug-in Problem Key 'category.help.description' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 680 Plug-in Problem Key 'category.navigate.description' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 672 Plug-in Problem Key 'category.perspective.description' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 1162 Plug-in Problem Key 'category.window.description' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 676 Plug-in Problem Key 'Color.counterText' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 1385 Plug-in Problem Key 'Color.decorationsText' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 1376 Plug-in Problem Key 'command.closePerspective.perspectiveId.name' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 1034 Plug-in Problem Key 'ExtPoint.configurableStackPresentation' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 16 Plug-in Problem Key 'ExtPoint.layouts' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 15 Plug-in Problem Key 'ExtPoint.rap.entrypoint' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 9 Plug-in Problem Key 'ExtPoint.rap.phaselistener' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 10 Plug-in Problem Key 'ExtPoint.rap.settingstores' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 12 Plug-in Problem Key 'ExtPoint.rap.themeableWidgets' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 14 Plug-in Problem Key 'ExtPoint.rap.themes' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 13 Plug-in Problem Key 'ExtPoint.rap.adapterfactory' is not found localization properties file plugin.xml /org.eclipse.rap.ui line 7 Plug-in Problem can someone help me?! please, this is urgent, i need to deliver my diploma thesis (i developed a RAP based application) this friday and i need to put the workspace including the application plug-ins on a DVD and deliver it along. i need to use the CVS plug-ins because they contain important bugfixes. i already tried to use the babel nl fragments for rap, but the errors shown above still appear. i would really like to use only target-platform bundles, but the 1.3M3 release is dated on the 2nd Octobre, thats too late for me because i have to deliver my diploma thesis on that day :(((((. i hope someone could help me with this issue :(. I can't imagine how the bug fix for this bug affected the rap.ui plugin. What I understand is that if you use the original RCP NL fragments, you get error markers for things like "ExtPoint.rap.entrypoint" as these keys don't exist in the RCP NL bundles. Which language pack do you use for testing? Just checked with the arabish one and they only translated two out of ten RAP-specific entrypoints :( In case your translation is missing these keys, the easiest way is to fix them in Babel yourself (you only need a bugzilla account) or add the missing keys to the plugin_XX.properties yourself. Keys like "category.edit.description" seem to be missing as the don't contain any text in the original properties (but there are keys). If this problem is new to you, it may be that you changed the default locale of your target you compile against. That would at least explain why you get any errors and me not. (In reply to comment #2) I ran into the same problem checking out the latest Version. I could "solve" this by adding a space into the plugin.properties file, save it and replace it with the latest head version (just fumbling around). Unfortunately I can not reproduce this anymore, so I decided to post this solution here in case anybody stumbles over the same problem and finds this bug entry by a related google search as I did... |