Kbase P86383: Translation Manager & Visual Translator generating errors translating UNIX application
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  8/9/2004 |
|
Status: Unverified
FACT(s) (Environment):
UNIX
FACT(s) (Environment):
Windows
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
Translating a UNIX based application using the Translation Manager & the Visual Translator.
Translation Manager Error: "zero strings are translated"
Visual Translator Error: "source string not found"
CAUSE:
The Translation Manager and the Visual Translator assume that procedure file and directory names use the Windows "\" and not the UNIX "/" notation.
FIX:
A solution is to fool progress into thinking the source code originated on Windows, by running the following program AFTER Loading the STRING-XREF data file:
FOR EACH xl_instance WHERE INDEX(proc_name,"/") NE 0:
proc_name = REPLACE(proc_name,"/","~\").
END.
Once the translation is complete, convert the procedure names back to their original UNIX notations before compiling the programs on UNIX.