PATH WebObjects 4.0 Documentation > What's New in WebObjects 4.0

Table of Contents

Previous Section

Changes to Localization

In WebObjects 3.5 (and earlier releases), localized versions of a component's HTML templates are located in each component's .wo folder, in subdirectories called language.lproj (French.lproj, for example). This mechanism is functional, but isn't supported by developer tools such as Project Builder and WebObjects Builder.

To improve support for developing multi-language web applications, WebObjects 4.0 adopts a localization scheme that's similar to the one for Yellow Box applications. Now components (.wo's) and other resources (such as .gif images) are localizable from Project Builder.

The new scheme changes the locations of localized files as follows:

Localized files go in language.lproj folders in the Web Components, Resources, and Web Server Resources directories. Any component, application resource, or web server resource can have a version in one or more .lproj folders.
As with Java and Objective-C source code, script files now go at the top level of the project (or subproject), outside the .wo, and they are visible in Project Builder's Classes suitcase. Note that Project Builder still keeps track of the relationship between your script files and their components. For example, if you select Main.wo/Main.html and then select the Classes suitcase, Project Builder automatically displays Main.wos.
Similarly .api files go at the top level of the project (or subproject), outside the .wo, as they (like the script and source files) apply to all localized versions of a component. In Project Builder, they are visible in the Resources suitcase.
All language versions of a localized component (.wo) must contain both the .html and .wod files. If a .woo file exists for the component, it must be in included in each version of the component as well.

Table of Contents Next Section