Community
Participate
Working Groups
The current fragment support does not allow strings in the fragment.xml to be isolated and translated. In particular, this is a problem for any contributed extensions (but also for extension point names/ etc that appear in PDE UI). NOTES: The problem is that we only support a single plugin.properties, and information contributed by fragments is looked up in the plugin.properties bundle. Any one given fragment could play the NL game and supply plugin.properties containing base strings plus strings for itself, but this would miss other fragments. We need a mechanism that allows a fragment to contribute strings that logically augment the plugin.properties, without creating conflicts with the base plugin, or other fragments for that plugin (ie. sort-of-a "fragmented" bundle). Until we have a solution, fragments are really not usable to contribute extensions that need to be NL-enabled. Related PR: 1GHH215: ITPCORE:WINNT - translated plugin.properties cannot be contributed by fragments
Fixed pre-20020115 build. See bug 3089. getResourceBundle will now have access to fragment directories (we were not actaully using the class PlatformURLFragmentConnection as we had no way to get to it. New method getAuxillaryURLs in the PlatformURLConnection allows fragment directories to be communicated from the plugin descriptor.
*** Bug 3116 has been marked as a duplicate of this bug. ***
