[gap]

Originally Posted by Paco

Hi gap,

I added the singular and plural-forms to the scipt.

Thank you Paco!
I've updated the italian translation at post #53 and added a new text entry: 'DEGREES' for the plural form

Originally Posted by Paco

Than I added a variable to setup a new delimiter for the shn-files and patched the TDW-scipt additive.

For better digest, I used the "_" as delimiter and not "#".

Originally Posted by Paco

Have a look for the italian version:

That's not correct

the correct forms should be:

Viriamo 10 gradi di barra a dritta, Comandante.
Viriamo 10 gradi di barra a sinistra, Comandante.

or even:

Viriamo 10 gradi a dritta, Comandante.
Viriamo 10 gradi a sinistra, Comandante.

Originally Posted by Paco

Ok, now I try toexplain the outputs while passing a Masterwaypoint:

A Masterwaypoint is mostly a turning-point, we have to set a new heading, for example to circle around an island. Additional we are able to change the speed and/or the depth of the sub.


1. Speed-Changes:

...

2. Headings:

...

translation done without problems
(see post #53)

Originally Posted by Paco

3. Changing Sub-depth:

The process of changing the subdepth is a little bit more complex.

A sub is on surface while travelling above the waves or decks-awash. It is Submerged if it is on snorkel depth or below. So I have designed different prepare-commands:

....

Okay, translation done, but with some remarks:

• the entry ['FOR'] should be translated with the italian preposition "a" combined with the definite article, wich may vary depending on the noun that follows it. In our case we would have "al" or "all'" (with the apostrophe). My workaround was leaving the 'FOR' entry blanc, and including the preposition in the ['TO_SURFACE'], ['TO_DIVE'], ['TO_TESTDIVE'] and ['TO_CHANGE_DEPTH'] entries. Are they used in any other combination that the one you have illustrated?
  
  
• In italian we make a broad use of the apostrophe. Nevertheless I see that your code uses straight apostrophes as string markers. I've used the curly apostrophe instead (hoping that it is not going to be confused with the straight one), but this forum doesn't recognize it: it gets replaced with a ***8217; code. In your code, you should replace that text with the correct character. If you are going to do it, please remember that there is no space between words separeted by postrophes (for example: "all'immersione" not "all' immersione".
  
  
• 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.
  
  
• As far as depth commands are concerned, could you put the ['GO_TO'] string to before these phrases:
  
  TEXT['SNORKEL_DEPTH'] + TEXT['XO']
  TEXT['PERISCOPE_DEPTH'] + TEXT['XO']
  TEXT['DECKSAWASH_DEPTH'] + TEXT['XO']
  
  it would make more obvious that they are orders, and it would also make them symmetrical with their respective answers (order carried out), thus easing their translation.
  
  
• In this dialog:
  
  TEXT['GO_TO'] + subdepth + TEXT['METRES'] + TEXT['XO']
  TEXT['GOING_TO'] + subdepth + TEXT['METRES'] + TEXT['HERR_KALEUN']
  
  can you insert a ['DEPTH'] string between ['GO_TO'] / ['GOING_TO'] and the subdepth value: it is not indispensable, but in italian in would make it more straightforward from the beginning that we are talking about meters of depth. For other languages that don't require it, the entry could be left blank

Originally Posted by Paco

4. Routing informations:

...

5. Arrival:

...

No problem here