Collapse All Expand All

Version: 10.6.1a

Resource Center Home

If you wish to view your Responder application in a language other than English, you may localize it into any language using the following instructions.

When localizing a .NET project, you have the option of localizing only some *.resx files and leaving the remainder in English. You may also localize all *.resx files.

You can localize global resources and/or forms. The first section below discusses localizing global resources (such as strings), while the second section discusses localizing forms. The final section discusses the steps to be performed after localizing any .resx files (strings or forms).

Localize Global Resources

1. You will need to modify the .resx files installed with Responder. They are installed at the following locations (see Localizing Responder Map and Switch Order Request Viewers for information on modifying those specific .resx files):
   • Client and Server: Program Files\Miner and Miner\ArcFM Solution\Resources. In this directory look for any files that contain MinerResources.resx or Properties.Resources.resx and that reside in any directory that starts with Miner.Responder. These files contain strings; all others contain forms.
   • Web: These resource files reside in several locations:
     • C:\Inetpub\wwwroot\Responder\App_GlobalResources
     • C:\Inetpub\wwwroot\Responder\App_LocalResources
     • C:\Inetpub\wwwroot\Responder\Authorized\Admin\App_LocalResources
     • C:\Inetpub\wwwroot\Responder\Authorized\Csr\App_LocalResources
     • C:\Inetpub\wwwroot\Responder\Authorized\Dispatchers\App_LocalResources
     • C:\Inetpub\wwwroot\Responder\Authorized\Settings\App_LocalResources
     • C:\Inetpub\wwwroot\Responder\Controls\App_LocalResources
     • C:\Inetpub\wwwroot\Responder\Dashboard\App_LocalResources
     • C:\Inetpub\wwwroot\Responder\WebParts\App_LocalResources
2. Open each .resx file using an application that allows you to view and edit *.resx files (e.g., Catalyst, Visual Studio). Modify the strings as needed.
3. Save the .resx files, but DO NOT move them from the directory in which they reside.
4. Follow the steps in the Finish Localization section below.

Localize Forms

You can localize forms using the same method as strings (see Localize Global Resources section above), or you can use the WinRes.exe provided with the .NET 2.0 Framework. The instructions below discuss how to use WinRes.exe.

If you choose to use WinRes.exe, you will need an Infragistics license in order to view the fields on the forms. Without an Infragistics license, WinRes.exe will use a placeholder instead of displaying the component.

1. The Windows Resource Localization Editor (WinRes.exe) allows you to localize forms. This product is included with the .NET 2.0 Framework. You may also choose to use another third-party tool to localize .resx files. WinRes.exe is installed here: Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin

2. In order to use the Windows Resource Localization Editor, it must reside in the same directory as the .resx files. Copy WinRes.exe to the directory that holds the Responder .resx files. By default Responder .resx files are installed in the following locations. Note that WinRes.exe cannot be used to localize the Responder Web.
   • Client and Server: Program Files\Miner and Miner\ArcFM Solution\Resources
3. Open each .resx file using WinRes.exe and modify the forms as necessary. See the Windows Resource Localization Editor for more information about this tool. If you do not have an Infragistics license, the Infragistics components will be replaced with a place holder.
4. Save the .resx files, but DO NOT move them from the directory in which they reside.
5. Follow the steps in the Finish Localization section below.

Finish Localization

The following steps apply for ALL localized .resx files (strings and forms).

1. Create copies of the .NET resource files (*.resx) in the same directory. DO NOT move them from the directory in which they reside. The .NET resource files are installed in various places, depending upon the Responder application.

2. Change the name of the copied resource files to include the CultureCode that corresponds to your language. For example, a file called Miner.Resource.Properties.Resources.resx would be renamed to Miner.Resource.Properties.Resources.es-Mx.resx when translated to Mexican Spanish. Maintain the original resource files in the same directory.
3. Web Server Only (if you have chosen to localize it). Open the Web.config file C:\Inetpub\wwwroot\Responder and locate the <globalization> tag. Enter your CultureCode in the culture and uiCulture attributes (e.g., es-Mx).

       <globalization culture="es-Mx" uiCulture="es-Mx" />
   

4. This step is optional. You may override the current localization setting by modifying the following registry setting: HKEY_LOCAL_MACHINE\Software\Miner and Miner\Resources\CultureCode. By default, the CultureCode value is set to the language of your Operating System. If your OS is Mexican Spanish and you're translating your ArcFM Solution application to Mexican Spanish, then this setting does not need to be modified. If you're translating your ArcFM application to a language different from your OS language, this registry key must be set to the CultureCode used when renaming *.resx files.

4. This step is optional. Perform this step only if full Unicode support is needed for characters in the language to which you are localizing (i.e., if your DBTUNE file uses Unicode as a setting). Modify all VarChar2 fields to be NVarChar2 fields in all Responder tables in your geodatabase.

 

 

---

Send Comment to ArcFMdocumentation@schneider-electric.com