Upgrade Toolkit

Chapter 3. Upgrading to Multilanguage
18
2 Export all text strings by selecting all the objects and clicking Tools, Translate,
Export.
In order to speed up the merge process, you should choose to export only those
objects that make the current custom version different from the old base version.
This is made easier if the customizations are well documented and perhaps marked
with an entry in the Version List field. If you choose to do this, you must carry out a
special step later on as described on page 32.
Save this file as cust_W1W1_client_260.txt, where cust means that it is the
customer’s database, the first W1 means the language of the database, the second
W1 means the country that the database was localized to, client indicates that this
file was exported with the Translate option, and 260 is the version number. For
example, if the database is localized to the German market, the file is saved as
cust_DEDE_client_260.txt.
3 Import the ObjectTime.fob file from the Upgtk folder.
4 Select the dataport 104010, Import/Export Object Time, and click Run (ALT+R).
5 In the request form, on the Options tab, fill in the fields as follows:
Field Name Value
File Name ObjectTime.txt
Direction Export
Note that ObjectTime.txt is a generic name that you should not use for both
database. For the old base version, the file name could be ObjectTimeOld.txt,
and for the customer’s current version, the file name could be
ObjectTimeCust.txt.
6 Click OK to create a file with information from the Modified, Date and Time fields
from the objects.
You will import these files again when you have completed the translation.
Full Match Translation of the Code Base
Before you translate, you must set up the correct folder structure in your working
folder.
If you working folder is C:\Multilanguage\W1\NF\260, you must create a subfolder
called NLW, which must contain two subfolders, Source and Target. Move the
cust_W1W1_client_260.txt file to the Source folder.