MonoX can be fully localized using two different approaches. First one is standard: it involves translating MonoX resource (.resx) files (available from our support team on request) and sending it back to us for recompilation and inclusion to the installation package. This approach is quick and simple, and is more suited if you plan to develop multiple projects on top of MonoX - once you got a localized version, it is easy to open as many sites as you want with that particular language.

Additionally, MonoX includes support for completely interactive localization that does not require recompilation of the project, as all resources are stored in the database. This gives users more power and flexibility, since it would be impossible to localize all resources at run time (both built-in and custom ones) using only a "resx approach". It is possible to export values from database to resx files and vice versa, both for a single page/control or for a whole portal at once. To start using this approach you will have to change the default ResourceProviderModel in the web.config file and set it to DBResourceManager. This will enable the Portal localization management utility (found under "Other tasks" on the main administrative screen), that does the real job for all portal pages and controls.

This pane allows administrators to localize each and every localizable resource in the portal. Note that MonoX uses translation engines to suggest a correct translation for each text.

Regardless of the active resource provider model, administrators can dynamically add or remove languages from a list of supported portal languages in the Language manager administration section.

Note that everything I said above applies to the localization of the base MonoX package. You can choose additional custom scenarios for your projects built on top of MonoX, it will not interfere with any other technique.