Telerik Sitefinity helps easily create and manage multilingual Web sites. The Framework 2.0 localization mechanism is used where ASP.NET utilizes the Unicode and
String class of the .NET Framework. This enables the developer to easily specify different encoding types. Sitefinity stores the localized version of the pages for a given
project in the database. You can localize the interface of Sitefinity that affects all the labels, tool tips, error messages, and buttons (except for image buttons). The interface
languages are in the bin folder of the project.
The folder names follow the RFC 1766 standard format, [Language code]-[County/Region code]. For example, American English is "en-US".
 |
For more information on localization of pages, sites, modules, and so on, see the section "Multilingual Content Management" in the User Manual.
|
404 Error for Non-existent Language Versions of a Page
A single page could contain numerous versions with one and the same content but in different languages. When, however, there is an attempt to access a page version
for a given language, and this page has not been created yet, a 404 error is displayed to notify the user. This is its expected behavior.
Localization and the Built-in Generic Content Module
Throughout this section, there will be several examples that focus on Localization but use the Generic Content module to demonstrate their implementation. Therefore, some
information on the applied tables of the database might prove useful when working with this section:
The following tables hold the multilingual content from the Generic Content Module:
- sf_CmsContentBase
- sf_CmsContentMetaData
- sf_CmsTextContent
If versioning is used (it is used by default), the staged content is stored in:
- sf_VersionItem
- sf_VrsTxtData
See Also