The process of creating an application that is useful to many different users with different locales and languages is called software internationalization. Such an application requires localization to customize it to the supported locales and languages. You can use many localization models to create software for international users. However, FileHold technology supports a highly effective localization model of its own.

FileHold's client interfaces ( FileHold Web client, FileHold Desktop application and Microsoft Office FileHold clients) are able to be localized into languages other than English. At this point in time we are not offering localization of FileHold Installers and Updaters utilities. When users logon via any of the client interfaces the language to be displayed is automatically set based on the language settings of the user’s operating system. Both single and double byte character sets are supported with FileHolds internationalization model.

FileHold software is currently localized into 2 languages, English and Polish. The following help article covers the steps required by third party (either a FileHold Partner or FileHold Customer) that is wanting to localize any or all of the FileHold client user interfaces. Please understand that the topic of user interface localization is a complex one when you consider how the characteristics of different human languages can affect the user interface experience of a given system. The web contains many resources on multilingual user interface (MUI) design and we encourage you to research the topic of localization before you proceed with a FileHold localization project.

An Overview of the FileHold Localization Process

This section provides an overview of the steps that are required of the localization team (a FileHold Partner, Reseller or Customer) and FileHold Customer Service when localizing FileHold clients to a different language. Please use localize@filehold.com when communicating with FileHold Customer Service regarding FileHold client localization.

Step 1. Resource File Translation - The localization team translates some or all of the resource files for the areas of FileHold they wish to localize. Once this stage is completed all resource files are sent to FileHold for building into resource DLL's. Use the following link to learn more about Obtaining and Translating Resource Files.
Step 2. Sending the Resource Files To FileHold Customer Service for Building - After resource file translation is complete the resource files are sent from the localization team to FileHold Customer Service for Building. FileHold Customer service complies the new resource files and sends back to the localization team a zipped-up folder structure with the DLL versions of all new resource files ready for Testing.
Step 3. Testing the New Localization - the localization team takes the DLL versions of the new resource files and tests them using the FileHold clients to ensure the new interface captions have been accurately translated and are not breaking any areas of the user interface by being too long. Steps 1 through 3 are completed until the localization team is satisfied that the translation is complete. Use the following link to learn more about Testing the New Localization.
Step 4. Creation of New Server & Client Installers - using the final, tested DLL versions the FileHold Customer Service team incorporates the new languages into new server and client installer builds. The new client and server installer builds are provided to the localization team allowing them to install the application using the new languages at their (or their customers) site(s). It should be noted that only the FileHold client and server installation packages are modified. The RTM build of the FileHold application embedded in the installation package(s) is/are not modified. FileHold customer service retains the right to include the localization in future public releases of its software.