Translation Procedure
When you select System screens (forms) for translation, FTU accesses the LINCFORM file for your System.
The first Ispec screen or Teach screen (in alphabetical sequence of name) is displayed on page 1 of your terminal.
To translate individual screens, perform the following:
If a LINCFORM/LoadED file is present (as when modifying a new release), and there is a screen layout of the same name as a format in the LINCFORM file, then the screen layout in the LINCFORM/LoadED file are displayed on Page 2, for your use.
Select the version you want to use, and change display items by moving the cursor to the item to be changed and overtyping. Transmit your changed screen from the home position.
If a Teach screen exists in the LINCFORM/LoadED file, but not in the LINCFORM file, it is displayed on Page 2, and you can either insert it into the LINCFORM file, or ignore it. Refer to :IGNORE and :INSERT commands in FTU Commands: Format Screen and Teach Screen for more information.
Change existing Teach screen text by moving the cursor, and overtyping. Teach text should be entered as it is to appear on the screen for users.
Transmit your changed Teach screen from the home position.
Your new or modified screen layout or Teach screen is then written to the LINCFORM file and the next screen is displayed. If you want to skip forward to a particular screen, use the :SKIP command, as detailed under FTU Commands: Format Screen and Teach Screen. If there are no more screens, FTU closes the files, and prompt you to either commence another session, or to terminate.
About Translation
Translations cannot go beyond the end of the last item on the primary screen, as the transmit character immediately follows the last item.
Direction Out, No Persistence properties in your screens are indicated by a sequence of X characters in the LINCFORM file version (displayed on Page 1).
When screen layouts are also displayed on Page 2 (that is, when the LINCFORM/ LoadED file is present), your Page 2 screens will not contain the Direction Out, No Persistence attributes. Although the properties are not visible, FTU will not allow them to be overwritten. This restriction is due to Direction Out, No Persistence properties not being present in your LINCFORM files. (FTU accesses the GLI format file to detect the presence of these properties.)
Because FTU processes sequentially (you cannot cycle backwards through the LINC/FORMS file), any errors encountered during the process of an :ADD ispec*language command cause the current form to be completed and the :ADD command to terminate at that point.
This means that, if you accidentally transmitted prior to finishing work on a particular screen (Ispec or Help screen), you are taken to the next available screen and the :ADD command you entered previously is terminated.
To complete such an interrupted change, you must save your FTU session, quit FTU, and then initiate a new FTU session. You can then use the FTU commands to locate the screen you were previously working on, and continue from that point.
Translation Example – Display Item Modification
In Ispec screens, display items can be modified from column one up to column 80 in that line (excluding any columns used by attributes).
An example of an Ispec screen displayed by FTU is shown below.
Customer Number: >000000< XXXXXXXXXX
Branch Number: >000 Type: 00<
Credit Limit: >00000.00 00< Discount Type |
Example of FTU Screen Translation
In the figure above, you cannot change the attributes in areas between angle bracket delimiters, (for example >000<). You can change other areas containing text by overtyping (provided they are not Direction Out, No Persistence attributes, which are indicated by X characters).
Blank lines can be modified up to column 80. You cannot add past the last property on the screen.
On Teach screens, lines can be freely added, deleted, or changed from column 1 to column 74.