Consultor Eletrônico

TranMan can't find translated files moved to a new dir.

If you move translated files from one part of your directory structure
to another AFTER translation, you will find that TranMan is unable
to find them, no matter how you set your PROPATH. What you may find
is that TranMan is looking in the original directory where the files
were originally tranlated, instead of looking in the new directory
to where they were moved. It may ideed seem as if TranMan is
'broken'.

This is not surprising. TranMan was never designed to handle this
case. To understand why this "broke TranMan", the user needs
to understand that the compiler translates strings on an instance
by instance basis. An instance is defined by three criteria - all of
which must match:

1) String content (after the "&"'s have been removed)
2) Filename (full path names are used to determine a match here.)
3) String attributes (the little ":R10" things)

Clearly by moving the files to a different directory after the strings
have been extracted and translated, #2 will not match and no
translations will be made. It might be possible to write some
programs to change the Project database so that the filenames will
"sync-up" but this is completely up to the user to design and is not
supported.

The best resolution of this situation is to export your glossary to a
file. Then create a new project database and re-extract the strings
from the files. Then import the exported glossary and do a
"PreTranslation". This will result in translating everything that was
previously translated and the Project database having the correct
file identifications.

The only problem would arise if there are multiple translations for
the same source string, the batch PreTranslation might choose the
wrong translation. However, the log file will list all of the times
when TranMan had to choose from multiple possible translations so
each case could be checked out.

10/09/98 FSI - RH