Hi, David: I copied this from one of our email exchanges : The chrome directory structure is basically... chrome/<windowType>/<providerType>/<providerName>/<files> Where <windowType> = "navigator", "composer", "messenger", etc. <providerType> = "content", "skin", "locale", "platform" <providerName> = "en-US", "MozillaZine", "Yahoo", "Mac" We need this feature by M7 so that XUL-based UI can be localized. Thanks!

setting p2 for m7. Note that this is only a target, not a commitment that it will be done in M7!

Done. See xpfe newsgroup for details.

verified

Hi, david: I tested it on jun-15-99 build and found that this feature does not work as it claimed. When the name entry is defined in the registry but not in the chrome url path, the referenced file will not be located. For example, with a chrome url like this: "chrome://navigator/locale/test.dtd" and the base entry, "resource:/navigator/locale/", and name entry, "en-US". The chrome url gets converted into "resource:/navigator/locale/test.dtd" instead of "resource:/navigator/locale/en-US/test.dtd". I'm reopening this bug unless this is an intended feature.

You should not be using a <base> entry any more, and you should be installing your locales in the right place (under the chrome directory). See the post in mozilla.xpfe, "Anatomy of a chrome registry entry".

It's out of my expectation; but, hey, it's cool ;) I'll clear the resolution and verify it.

BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.