Thank You very much Trevally. :yeah: :woot:

Hello,

I'm currently searching different specifications for divings and economic speeds. That means, it is possible to dive or to surface while passing a waypoint and the boat is switching to the best speeds.

So I need the specifications for the following sub-types:

VIIA, VIIB, VIIC and VIIC/41

Best speed at surface, snorkel-depth and submerged.

The depth for snorkeling, periscope and running decksawash.

Sorry Guys, but the searchfunction of subsim is not my friend. :oops:

Greets,
Paco.

Here is some info for the type C (see page 14 for speed):hmmm:
http://www.uboatarchive.net/Manual.htm

For patrol speeds - most think that 7knots surfaced is the best speed.
If you then dive to schorkel depth - your speed will change to 4 to 5 knots - I guess this is the same engine revs so may be the best speed.
I would use the same test for decks awash - set speed on surface (7knots) set decks awash and check speed.

Thanks Trevally.

So I set the depths to the following values:

Output-options / Concatenating phrases
 

I have defined two different Output-options:

1) You get the informations from Your Crew regarding course-, speed-corrections and depths-changes. Speed and Depthoutputs are optional.

In the Messagebox, that looks like:

2.) A dialogstyle. The captain orders, and the crew confirms. For depth-changes, there is also a prepare-command given:

Based on my first tests, I have not defined whole phrases, but I concatenating them from different pieces of words, which are defined in a "text-library". :o

From the example above, I hope You can have a look at this library and give me some hints for the english-, french- and italian version. :D

Here comes the part from the script:

The first three Variables on top are for the correspondending SHA-file:

The example from a real route from Kiel to a position near to Danzig:

You find the SHA_* Variables in bold.


What I actually do:

I have defined the routes for the coastal-waters campaign. The last run to build sha- and shn-files returns:

The distance between the waypoints are < 30 km and they are randomized within 2000 (given WP) and 1000 (calculated WP) mtr around
their calculated (ideal-)positions.

58 routes are in- and outbound-routes, that means that I have defined 29 different routes from Kiel and Wilhelmshaven to destinations in the baltic-, north-, nordic- and celtic-sea. To give the Mod a little more military- or mysterious touch, I named the routes by the KM-Grids of their start- and end-points (see the [AS]-section above).

If You want to travel from A to B, You have to look into a briefcase with charts and Maps to find the name of the needed route. Than You can find the route in the automation-menu and only have to activate it.

The Screenshot below is a preview of some sheets from the briefcase:

http://www.mediafire.com/conv/20db6c...15bd762a6g.jpg

I hope that I was able to give a short insight of my work to You,
Paco

Definitely yes, Paco, keep up your great work! :yeah:

Talking about the dialogs, I wish to help with the Italian translation, but it is an hard task to translate the short sentences of your script without a context. Could you please provide us with some more examples of complete dialogs, besides the ones you have already posted?

The best would be if you could list every text entry (in English/German) in all its possible combinations :)

Comments at a calculated Waypoint
 

Thanks gap for the feedback. :up:

Ok, I begin with the easier part, the comments on calculated waypoints. That are the WPs, where only little corrections for sub-heading are required.

There are thre possible status:
#1 need to turn a little bit to the left.
#2 no correction required
#3 need to turn a little bit to the right.

If You want to get the comments from Your Crew only, the sentences are build from the following Variables:

## Get the correction exact in degrees:

#1
#2
#3
## Get the correction only in decimal-style:

#1
#2
#3
BIGREGBLANK: As BIGREG mentioned, he would like to get the comment given in 10-degree-steps and not as the word "dez/dec". If You define it as the word "dez/dec", You have to set BIGREGBLANK = " " (blank). If You decide to use something like "10,20,30" degree, BIGREGBLANK must be "" (NULL)
After this sentence, we always add the recipient:

Example in german and english:

Or, with exact degrees:
Dialog-style:

At a calculated Waypoint, I designed the dialog very simple:

Before the sentence from above, the captain commands his navigator to check the course:

Example:

With enabling the italian- or french-output, I currently get these sentences:

For the Masterwaypoints, I'll write an extra post.

At This Point, I think, the captain should not ask the navigator to check the course, but rather order him to go 10 degree to port. (It is perhaps the behaviour, which was wanted by BIGREG here: http://www.subsim.com/radioroom/show...3&postcount=34 ).

What do You think?

Cheers,
Paco.

Thank you Paco, :up:

here's an update of the italian dialogs, based on your inputs:

Notice that many entries are still in English: I will wait for further explainations by you before translating them too :)

P.S: is there any special formatting for decimal marks?

:yeah:

Now it looks like:

The Value for the comma has to be a point, because I am not able to hide it from the automation-function. And there it is the field-separator...


decimal marks: You mean something like: 1.000 or 1,000 instead of 1000? No, not at the moment, sorry.

I have made some corrections in the meanwhile. Among them, 'Ufficiale di navigazione' was replaced with 'Ufficiale di rotta'. ;)

Also notice that, likewise its French correspective, the Italian phrase:

sounds a bit akward.

I have translated the 'DEC_TO' entry just in case, but if you look closely at my previous post, I have also set 'BIGREGBLANK' to '' (Null). If I understood your explanations, it should result in the following phrase being used instead:

Finally, the italian word 'gradi' is case sensitive (singular: grado). I could replace it with the degree symbol '°', but then, it should be linked with the respective value (es. '1°' instead of '1 °'). Can you remove the space separator between degree values and their unit of measure? :D

So this entry:

'KOMMATA' : ',',

has to be:

'KOMMATA' : '.',?

Using periods instead of commas makes dialogs lesser intellegible, imo...

maybe we can add a comma and a space at the end of text entries that are always followed by a recipient, or a comma and a space to the entries used for recipients, thus making the use of other separators dispensable :hmmm:

no, I was especially concerned about the separator used in Imperial/Intenational system for decimal numbers:

1.5 instead of 1,5

You understood it in the right way. :yeah:

Hm, I could implement the singular and plural form. It looks better than the degree symbol, imho?



I know, but TDW has assigned the comma as a field-seperator in his automation.py-Script. I have looked into it and found the function which is reading and processing the shn-file. I'm able to change it there, but we have to be compatible to the other automation-scripts from Trevally, AvM, etc.

If we decide to use "#" instead of "," as field seperator, I could add a query in TDWs scipt, which checks the given format in the shn-File and sets the correct separator for the further instructions. But, BUT(!) it is TDWs work and as I see, he isn't active here at the moment. Furthermore he isn't very amused, if someone is patching in his work...

from his work:

So we need a decision:
1) To accept the period.
2) If someone is in contact with him outside of subsim, to get his contact-data and ask him for permission to add a change to his code.
3) To patch his work as an unofficial patch with a suitable comment and if he will be back here, to get this (only three lines of code) into the official Mod.

At the moment, where if found the problem with comma or period, I decided that I use option 1 and respect TDWs disclaimer.


Sorry, no. As soon as a comma is in use in a comment, the automation.py gives an exception and I can't mask it (\,) :-?

But I want to say, that it is not a bug by TDW or a bad design, it was simply his decision to use the comma as separator for his datastructure. :up:

Not impossible :03: -> I wrote it to my todo-(wish-)list.

:cool:

yes, nice :up:
I don't know in other languages, but we Italian do use the singular form (grado) only for the "1" value. Numbers bigger or lesser than 1, including decimal numbers, take the plural (gradi) i.e:

0 gradi
0,5 gradi
1 grado
1,5 gradi
2 gradi
...

I may be wrong, but I think TDW is only concerned about people using part of his code in their own mods for any other reason than ensuring compatibility with them. On the other hand, he has always been extremely open to suggestions meant to improve his work and to stimulate other's creativity.

I don't see how switching from a comma to an hash could be considered code stealing, especially seen that your scripts would rely anyway on script support, coded by TDW himself in his NewUIs, and you are not pretending to have invented anything new :yep:

All the same, I would get anyway in touch with him for three reasons:

- politeness :)

- asking him if by any chance the changes proposed by you may be generating bugs, or breaking other's scripts

- asking him to include your inprovements in the next version of New UIs, provided that they have no side effects :03:

singular/plural; TDW Scripts
 

Hi gap,

I added the singular and plural-forms to the scipt. 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 "#".

Have a look for the italian version:

:yeah: I will do so.

Cheers,
Paco.

Comments at a given Waypoint (MWP)
 

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:

If using the dialog-style, the captain commands to change speed or to stop the sub:

- stopping:
-changing speed:
Than, the crew confirms this command - this part is the same as the no dialog-style:

- stopping:
-changing speed:
Examples:
2. Headings:

If using the dialog-style, the captain commands the new heading of the sub:

Than, the crew confirms this command - this part is the same as the no dialog-style. It is divided to write the heading in degree or as a compass:

a) degree - change heading:

b) degree - heading is not changing:

c) compass-style - change heading:

d) compass-style - heading is not changing:

Examples:

3. Changing Sub-depth:

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

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:

Dialog-style surfacing:
Dialog-style from surface -> diving:
Dialog-style from surface -> diving to the testdepth of the sub:
Dialog-style all other depth-changes:
Than follows the command with the exact depth:

The last part is used from dialog or non-dialog-style:
Examples:


4. Routing informations:

You get an information about the distance to the next MWP, the time ingame and realtime (calculated with the given TC)

Example:


5. Arrival:

At the last MWP, the comment is:

TEXT['WE_ARE_THERE'] + TEXT['HERR_KALEUN']

Good luck :arrgh!:
Paco

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

:up:

That's not correct :hmmm:

the correct forms should be:

or even:


translation done without problems :up:
(see post #53)


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. :hmm2:
  
  
• 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. :D
  
  
• 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 :)

No problem here :up: