Click on FTP to download from the FTP archives.
![[FTP]](http://www2.encompassus.org/hidedecus/graphics/i_ftp.gif)
NOTE: The following has been supplied to the DECUS library
by Digital Equipment Corporation. This software has
been supplied as is, with no expressed or implied
commitment to maintain, update, or support it or
its use. By supplying this, DEC and the author(s)
of the following are not responsible for damage,
consequential or inconsequential, which may result
from its use.
**************************************************************
Files referenced in this guide which are necessary for
translation tailoring of the LIMSSM screens are:
UNSPLIT.BAS
UNSPLIT.OBJ
UNSPLIT.EXE
FED.BAS
FED.OBJ
FED.EXE
TAILOR.COM
SCREEN_TAILORING.DOC (this guide)
The object modules and executables are
already supplied with the kit. If you should
need to recompile or relink one of the
routines the compile command is ( $ bas unsplit)
and ($ bas fed). The link command is
( $ link unsplit) and ($link fed)
This utility accomplishes direct translation of LIMS
terminology to the customer's. If you need to rearrange
fields on forms you can run the utilities to do the translations
and then use FMS/EDIT to tailor those forms that require more
extensive work. At step 8 you should have individual .FRM
files to do this more extensive work. You will be able to
continue with the remainder of the utilities after that.
You could also extract the same forms, do the desired tailoring,
and replace the forms into the library before starting to
use the utilities.
**** NOTE ****
If you need to do work with the Digital logo
(removal/replacement), utilities are available.
See DEC_LOGO.DOC in the DECUS library.
1. Create a file, FED.DAT, that contains the translations
of LIMS/SM terms to the customers terms. FED.DAT must have
the following format:
"Limsterm", "Labterm"
"limsterm", "labterm"
"LIMSTERM", "LABTERM"
Hints:
A. Plurals have to be tailored before singulars.
e.g. FED.DAT might contain:
"Projects", "Studies "
"projects", "studies "
"PROJECTS", "STUDIES "
"Project", "Study "
"project", "study "
"PROJECT", "STUDY "
If the plural translation were left out or came
after the singular then "Projects" would be translated
to "Study s".
B. If short words are changed to long words there will be
forms that won't compile because the lines are too long
or text is being placed in fields. These forms will have
to have additional individual editing.
C. If long words are changed to short words the forms may
not be as attractive because things will not line up the
way they used to.
D. If long words are changed to short words with padding
(spaces on the right) things will line up the way they
used to, but there will seem to be excess spaces at
various places in the form. You might want to try padding
the all capital words and shrinking the others. This is
because the words that are all caps are likely to appear
in columns in the help screens whereas the lower case
words would be in sentences.
E. A blank line in FED.DAT is interpreted as the end of file,
therefor no blank lines are allowed.
2. Obtain the forms library from the system library
using a copy statement.
$ COPY
from: LIMSSM$LIBRARY:LIMSSM.FLB
to: LIMSSM.FLB
**** WARNING ****
You will also want to perform the same
operations on the LIMS MENU library.
**** WARNING ****
$ COPY
from: LIMSSM$LIBRARY:LIMS$MENU$FORMS.FLB
to: LIMS$MENU$FORMS.FLB
3. Translate the entire library using FMS/DESCRIPTION in
preparation for use of the first utility. This will
translate the library of forms into a library of form
descriptions made up of Form Descriptor Language
statements.
$ FMS/DESCRIPTION LIMSSM.FLB
The result will be:
LIMSSM.FLB ------> LIMSSM.FLG
(takes about 2 minutes)
4. The next utility takes words that were split across
lines of text in the LIMSSM.FLG file into contiguous
words. The split words need to be reattached before
continuing with the remainder of the utilities.
$ RUN UNSPLIT
The result will be:
LIMSSM.FLG -------> LIMSSM.NEW
(takes about 4 minutes)
5. Rename the newly created file to a Form Descriptor Language
file to continue using the utilities.
$ RENAME LIMSSM.NEW LIMSSM.FLG
6. The next utility does the actual translations from the
FED.DAT that was created earlier. It also logs any
changes that were made during the run of this utility.
The utility creates individual FLG files for the forms
in the library.
$ RUN FED
The result will be:
LIMSSM.FLG -----> ALGORITHM.FLG LIMSSM.LOG
ALGORITHM_HLP.FLG
APPROVE1.FLG
|
V
ZPSET_HLP.FLG
(takes about 12 minutes)
A log of this activity is written to the screen
as well as to a file, FED.LOG. Forms that will
have problems should be checked at this time.
The log file contains the names of the forms, how
many characters were added or removed from a
particular line of the FLG file, and how long
that line is after running the utility. ( see APPENDIX B )
If the length is more than 92 characters, you must
look into changing the wording or abbreviating
the text. Not doing so may cause problems.
note:
Print a copy of FED.LOG to document what
was done.
7. The next utility converts the translated FLG files to
actual forms. Any errors encountered during this
utility indicated a problem with the translation done
in the previous step. This usually involves a field prompt
now overrunning the edge of the screen or into a field.
If this error occurs, recheck the FED.LOG file and/or edit
the .FLG file individually. This may entail abbreviation or
the moving of fields to accommodate the longer prompt.
$ @TAILOR (Choose TRANSLATE option)
The result of will be:
formname.FLG ----> formname.FRM
A log of this activity is written to a file,
TRANSLATE.LOG. The translation errors that took
place will be logged here. By examining which
forms had problems, TRANSLATE.LOG, and what was done
to them, FED.LOG, You should be able to
narrow down the trouble with the form.
Work out any difficulties with the form which usually
involves abbreviations or moving of fields. Then
translate the problem form(s) using the command:
FMS/TRANS formname.FLG
8. (Optional)
Run the next utility to create form listings for printing
the forms.
$ @TAILOR (LISTINGS OPTION)
The result will be:
formname.FRM -------> formname.LIS
9. The next step is to use one of two utilities to examine
each of the forms. One utility examines all forms, the
other lets you specify individual forms. FED.LOG
will let you see what forms have been altered. If most
have been modified, the utility to examine all forms is
the utility of choice,
Examining all forms:
$ TAILOR (CHOOSE VIEW OPTION)
This will prompt you for the form you want to begin
the examination of forms with then go through the
remainder of the forms
10. This step builds the tailored forms library.
$ @TAILOR (Choose BUILDLIB option)
The result will be:
ALGORITHM.FRM ------> LIMSSM.FLB
ALGORITHM_HLP.FRM
APPROVE1.FRM
|
V
ZPSET.FRM
11. The final step in the form tailoring process is to
clean up the directory your working in. Once the forms
library is completed, there should be no further need for
files with extensions of .FRM, .FLG, .LIS, or .SLS. These
should be deleted to conserve disk space.
Click on FTP to download from the FTP archives.