Hi gap,
I got Your remarks into the script:
Quote:
|
the entry ['FOR'] should be translated with the italian preposition "a" ....
|
Your workaround is good. I do it for some german translations, too.
Quote:
|
code uses straight apostrophes as string markers.
|
Changed it into double quote and added Your straight apostrophes into the strings.
Quote:
|
Are the strings ['TO_SNORKEL_DEPTH'], ['TO_PERISCOPE_DEPTH'] and ['TO_DECKSAWASH_DEPTH'] used likewise the remaining ['TO_*'] entries. I didn't translate them yet, because I couldn't find any mention to them among your examples
|
Yes
Quote:
|
As far as depth commands are concerned, could you put the ['GO_TO'] string to before these phrases:
|
Done. I divided it into 'GO_TO_DEPTH' for a depthchanging in metres and 'GO_TO_FIXED_DEPTH' for a change to a preset, like Snorkel, or Periscopedepth. For the german translation I leave the second one empty, because we don't need that 'GO_TO_FIXED_DEPTH'.
Quote:
|
can you insert a ['DEPTH'] string between ['GO_TO'] / ['GOING_TO']
|
Yes I can. -> Done. Added the new string into the TEXT-dictionary.
Greets,
Paco.