![]() ![]() |
|
Open Client Developer's Guide | |
Search | Index | Glossary | | |
![]() |
|
![]() |
![]() |
![]() |
Globalization and Localization SupportFileNet Open Client provides default fallback resources for globalization/localization
in the form of resource files in the ... This folder also includes the following subdirectories:
To localize for a particular language or culture, you may use, customize, or develop your own idmwsxRS.txt plain text and idmwsxRS.resx files, as appropriate. .NET Localization InformationThe .NET Framework provides extensive support for developing international applications. Globalization is the process of creating a core application that supports localized user interfaces and regional data for all users. Localization is the process of translating an application's user interface into a specific language. In the .NET Framework, culture refers to the user’s language optionally combined with that user's location. By specifying a culture, it is possible to use a set of common preferences for certain information—such as strings, date formats, and number formats—that correspond to the user's language and location conventions. Detailed culture preferences can be accessed using instances of the CultureInfo class, which are in turn accessed using culture tags. Culture tags use the format primary[-secondary], where the primary tag is the language and the optional secondary tag is the country/region code. By convention, the language tag consists of two lowercase letters, and the country/region tag consists of two uppercase letters. How Locale Resources are RetrievedIn an ascx or an aspx page, declare an instance of WsResourceManager and then useGetResourceString to retrieve the localized string or call GetResourceObject to get a localizeimage or other serialized object. Multiple Resource BundlesSharing ResourcesDo not set the Culture, UICulture or Encoding setting in each Web page; they should all be configured by Web.config and global.asax. Separate the name and the label of the control so that the name of the control will not be localized. Working with Locale Resource StringsString resources refer to all the text that appears in the application's user interface. They include,but are not limited to, menus, tabs, dialog boxes, alerts, and error messages. If an application will be used in a language or culture other than the one in which it was developed, these resources will have to be translated, or localized. A text file is used to store the localized string resources for Open Client. Each language and culture has its own resource file. Key-Naming GuidelinesThere is no specific naming convention for strings in general. However, when a string may have different translations, an additional key might have to be added. Currently, the only suggested naming convention is for error messages. Use the classes provided by System.Globalization Namespace to represent or display culture-sensitive data, like Date, Time, and Currency. Generating Resource BundlesThe text resource files have to be compiled into compiled resources, which in turn should be combined into a satellite assembly before it can be used by an application. Localizing ImagesIf an icon or image contains a localized string, it cannot be added to a text file. However, the image resource can be added to the compiled resources using ResourceWriter. To retrieve an object esource out of the resource file, declare an instance of WsResourceManager and use the GetResourceObject method. It is not recommended to have an image resource. If there is a need later, a utility can be easily implemented. |
![]() |
|