Localization of LiquidFiles Outlook Plugin and Windows Agent
All the resources are now customizeable with XML files. We have hardcoded default localization into our application and will continue to do so based on your feedback. However you can add your own resources, and that includes ability to change not only text but icons and position/size of elements too.
|Text and icons
How to change and debug localization for an existing language
- (Optional). Add registry policy
NoXmlResourceManagerLocalizationCache=1(DWORD). See Registry configuration for more details. This will prevent LiquidFiles from caching resources, so you would not need to restart Outlook and LiquidFiles Windows Agent each time you change the resource files.
- Unzip the downloaded file into
%appdata%\LiquidFilesfolder, e.g. file paths should be like this
C:\Users\USERNAME\AppData\Roaming\LiquidFiles\Resources.V3\LiquidFiles.WinUI.Base\ButtonCaptions.resx. Note: the location
C:\Users\USERNAME\AppData\Roaming\LiquidFilescan be determined by
SharedDataFolderpolicy as described below.
- Change resources and remove unnecessary ones. You might need to restart Outlook and LiquidFiles Windows
Agent between edits to verify your changes.
NoXmlResourceManagerLocalizationCacheRegistry policy to minimize restarts.
- We suggest that you only keep changed resources. Remove all unchanged resources, which includes
.resxfiles. However, do not remove
.resxfiles, otherwise the files cannot be read by .NET resource reader.
How to add localization for a new language
- Define new list of languages. You need to set
Languagesregistry policy to a comma-separated list of languages in Alpha-2 format. LiquidFiles Agent will use this list of languages in the specified order. To add a Japanese locale
jaas the first option before existing localizations, you need to seet the registry key like this
- Make a copy of necessary resource files with the new resource suffix. For example, make a copy of
ButtonCaptions.resxwith file name
- Edit resources as necessary.
- Restart LiquidFiles Windows Agent and Outlook to verify the new resources.
How to deploy localization
- Deploy to a shared folder: use registry policy
SharedDataFolderto specify a shared folder with resources. Copy
Resources.V3folder to that folder.
Example: if the policy value is
\\server\share\sharedfolder, then the file paths should be like
The shared folder can also be a local path, e.g.
- Deploy as a ZIP file: zip the resources, including
Resources.V3folder, so the directory structure of the ZIP file resembles the one of downloaded resources. Then, use registry policy
SharedDataFolderto specify either path to the ZIP file (such as UNC path
\\server\share\sharedfolder\myresources.zip), or URL to the file
In either case, LiquidFiles will download and unzip the file, and will be using the resources. Note: it might take an additional restart of Outlook and Windows Agent before the resources become available after initial download.
A few other translation resources:
- You can use this official Microsoft resource to look up how to translate OK, Cancel, Subject, Message and other strings in context), according to industry standards: http://www.microsoft.com/en-US/language