To support a new language locale, you must create the corresponding
.resx resource files by copying an existing language resource file and translating the terms as required using a resource file editor such as Visual Studio or Visual Studio Express.
The naming convention for each file should follow the convention of existing language file names and have the language code added to them (e.g.
The resource files are located in the
Workflow Applications and Web Services API
There are additional resource files for WorkflowGen applications and the Web Services API in the following folders:
There is one resource files for each language code, by module or application.
To create a Spanish (Mexico) resource file:
Go to the folder \wwwroot\wfgen\App_GlobalResources\
Advantys.Workflow.Web.UI.Portal.resxfile (the default English-US User Portal resource file).
Rename your copy with the Spanish country code
Open the file in a text editor and translate the English-US labels into Spanish-Mexico.
Repeat steps 2 to 4 for all resource files in the core module folder and the workflow application folders.
Important: Do not remove or alter the content of the
Name column in the resource file when translating, as these names are bound to the WorkflowGen application controls. Only alter the
Value column during the translation.
List of language codes
Language codes should be specified in the format
COUNTRY is optional is some cases). See http://www.codedigest.com/CodeDigest/207-Get-All-Language-Country-Code-List-for-all-Culture-in-C---ASP-Net.aspx for a complete list of language codes.
Important notes when creating or modifying resource files
The resource files for the
es-ESlanguages are provided in each update pack, and will overwrite any changes you may have applied to the existing files.
Upgrading WorkflowGen will create new resource file versions that may include changes to label identifiers (
Name) which could be altered, removed, or added. If you make changes to these files or have copied these files to create a language, you will need to make a backup copy of the files prior to any upgrades, study the changes to the resource files from the prior version, and manually re-apply changes.
Root resource files (those without the language-code suffix) should not be deleted.