Opened 12 years ago

Closed 12 years ago

#4646 closed defect (invalid)

i18n resource bundles are not looked up properly after building a profile

Reported by: guest Owned by: James Burke
Priority: high Milestone: 1.0
Component: BuildTools Version: 0.9
Keywords: i18n Cc: Adam Peller, ialpert@…
Blocked By: Blocking:

Description

Using a defined local before the build works fine, as soon as i build my project locale lookup throws errors of the form:"Bundle not found: buildResources in coemergence , locale=en-gb"

Change History (5)

comment:1 Changed 12 years ago by Adam Peller

Cc: Adam Peller ialpert@… added
Milestone: 1.0
Priority: normalhigh
severity: normalmajor

so it seems that the resources are getting inserted near the end of the layer file, just before the _preloadLocalizations() call, rather than being split out into nls files; the nls layer files are empty, which explains the error.

I'm going to try building a simple standalone test case.

comment:2 Changed 12 years ago by James Burke

Also, be sure you are using the latest 0.9 trunk code. There have been a few fixes since the 0.9.0 release. If you continue to see the bug, please let me know what subversion revision you are using (or what nightly you picked up from http://archive.dojotoolkit.org).

comment:3 Changed 12 years ago by Adam Peller

ialpert was on 0.9. He will try trunk and get back to us.

comment:4 Changed 12 years ago by guest

I tried this on trunk, and it exhibited the same problem "Bundle not found: ". I'm not convinced that it isn't something i'm doing wrong. What should the structure of the release nls dir look like (mine's only got the default resource bundle which i've created -- nothing else)? It doesn't look like the default resource bundle is being included in the custom build file however

comment:5 Changed 12 years ago by Adam Peller

Resolution: invalid
Status: newclosed

problem was 1) upgrade to trunk 2) remove references to i18n from top-level because they were firing before the bootstrap was finished

The latter could be documented better somewhere, I guess.

Note: See TracTickets for help on using tickets.