Localizing binary files

First create a new project in your localization tool that point to your bin folder (like c:\tera\gn4\bin), and then load the files to be localized. See List of binary files to be localized.

Whatever application you add remember to add also the corresponding *SystemAddIn.dll.

While defining the project you must check the "Sign assembly" for .NET Assembly Output adding a Strong Name Key file.

If the localized resources are not signed there will be a mismatch and the resources will not be loaded.

Request by email the TeraDP.snk file to Tera Support, or load it from the ..src\GN4AddIns

The last option to choose is the output language. It can be inside the project or in the tool's options.

The localization creates a folder named as the selected language in your source folder.

If you start your project in c:\tera\gn4\bin and then choose to translate into Portuguese - Brazil the output will be in c:\tera\gn4\bin\pt-BR

Once the project is created you are ready to start to translate. A small test to see if your localization works properly is the following:

•Add the following parameter to your default connection (the first connection in the case you have more) in %appdata%\TeraDP\GN4\UserConfig.xml

UILanguage="pt-BR"

so that your connection line reads like:

<Connection UILanguage="pt-BR" RequireLogin="true" Domain="" UserName="" Url="http://domain/gn4/adminsrv.asmx" Name="GN4"/>

This will show the culture code in the splash screen just beside the application version

•Make sure that the culture shown in the splash screen matches the subfolder created by the localizer in you bin folder

•Select the WinUI.dll in your project and search for the string "connecting..." and translate it to your language.

•Save your project

•Run a "create localized files"

•If everything is correct you should find all the translated resources in the "culture" bin's subfolder.

•Start Fred4 and connect to your application. The translation of the "connecting..." string should be visible in the splash screen while connecting.

If this test succeeded, your localization tool is properly configured.

You can use a single Lingobit project to generate translated files for both 32-bit and 64-bit versions of GN4.

To do it, create a project as explained in previous paragraphs, pointing to the folder with 32-bit GN4 binaries, translate and then generate the translated files. Copy the translated files from the Lingobit output folder to the 32-bit bin folder. Now, in Lingobit change the GN4 bin folder to the folder with 64-bit GN4 binaries, and then re-generate the translated files. Copy the translated files from the Lingobit output folder to the 64-bit bin folder.

•In version 2.0, GNText and GNPage dlls has been replaced by GNCore and GNCoreWinUI. The first one must be installed on editorial servers, the second one is a client only dll.

•GNCore requires Common.dll and Editorial.dll installed into server GAC (not on clients).

•Every time you reopen your project after a binaries update do a scan to check for changes and even though there are no changes the project must be recompiled

•Normally the localization tool shows a tree of the selected binaries. Each one can be expanded to see the internal resources. For example if you navigate the GNPage.dll you will see all the dialog's resources which are not visible selecting the GNPage.dll root.

•When localizing application's panels, like Fred4's panels in FredWinUI.dll, you can sort your strings by id. The .ShortTitle is the panel's label when the panel is tabbed; .Title is the full panel label.

•The "status" column can help to group the string by New/Not translate/Translated/Translated auto. This is a great help when updating an existing project.

•The FredWinUI.dll contains the WPF Fred4's panels (*page.baml in the project's tree). Attention to the translation because the available space is narrow. Use TedWinUI.dll for Ted4's panel.

•Possibility to select all and do a "Translate using Google translator or Microsoft translator". Good for resources that contain few strings, like editorial.dll or editorialClient.dll. Attention to some chars that are translated using the XML identity, this has to be fixed manually.

•When using this feature the status is set to auto and the translation might change in a future run

•90 days trial, very good for a deep testing. The trial ramdonly inserts _lingobit_ as string prefix.