Register Language-Specific Resources
Collapse the table of content
Expand the table of content
The document is archived and information here might be outdated

Register Language-Specific Resources

Exchange Server 2003

Register Language-Specific Resources

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Language-specific form registry entries allow an application to use any number of localized resources. The language, formurl, and executerurl properties in a form registration enable delivery of the localized content.

The language property in a registry entry associate resources with languages and allows different forms to be used depending on the language preferences of the user. When the browser makes a request the Accept-Language header reflects the language preferences of the user. Registry Language Fallback describes the content of the Accept-Language header and discusses how language preferences are matched against available form registry entries.

The form registry must contain a set of language-specific form registration entries for each language, the application supports. A wildcard (*) in the language property identifies the ASP and HTML forms that the application uses when the form registry does not provide an explicit or implicit language match. These default resources are also used when the Accept-Language header is blank. The formurl and the executeurl properties contain the names of the localized ASP and HTML pages. Once the registry entries exist for a language, then the form registry automatically direct users to the correct localized resources. The following lines of code show language properties for Japanese, Australian English, and Greek.

<form:language>ja</form:language>
<form:language>en-au</form:language>
<form:language>el</form:language>

The formurl property specifies the language-specific ASP and HTML files that contain localized markup. When the locale-specific files share names, they must be fully qualified by a folder name. The following lines of code show the formurl properties for Japanese, Australian English, and Greek. MyForm.htm resides in folders named ja, en-au, and el. The format foldername/filename format indicates this is a relative URL. To indicate an absolute URL, the format changes to /foldername/filename. The following example uses relative URLs.

<form:formurl>ja/MyForm.htm</form: formurl>
<form:formurl >en-au/MyForm.htm</form:formurl>
<form:formurl >el/MyForm.htm</form:formurl>

In the following example, the executerurl property specifies a language-specific ASP file. MyForm.asp resides in folders named ja, en-au, and el. The syntax requirements for relative and absolute URLs also apply the executeurl property. The value exwform.dll in the executeurl is not language specific. The following examples use relative URLs.

<form:executeurl>ja/MyForm.htm</form: executeurl >
<form: executeurl >en-au/MyForm.htm</form: executeurl >
<form: executeurl >el/MyForm.htm</form: executeurl >
Note  Unique names for ASP and HTML files can eliminate the need for language-specific folders. For example, files named MyFormJa.htm and MyFormEnAu.htm do not need to be further qualified by folder names.
Show:
© 2016 Microsoft