EU Inland ECDIS Manual (IEM)

[Rasbats]

At present OpenCPN is in compliance with the rules of EU Inland ECDIS Standard Edition 2.3 (Information Mode). The Standard was updated and in order to comply with Edition 2.4 there is a requirement for a multi-language manual (English, Dutch, French, German) for OpenCPN iECDIS.

Why does this matter?

In some countries with carriage obligations for Inland ECDIS in information mode, only Inland ECDIS that are in compliance with Inland ECDIS Standard Edition 2.4 (i.e. Commission Implementing Regulation (EU) 2018/1973 of 7 December 2018 amending Implementing Regulation (EU) No 909/2013) are permitted to be installed on Inland vessels.

In addition there is a pilot EU project for using OpenCPN as the basis for the reception of binary messages (Water level, Bridge height etc). The appeal is the opensource nature of OpenCPN.

The first draft of a multi-lingual IEM is here:
https://opencpn-manuals.github.io/inland-ecdis/manuals/en/index.html
Translations are needed in Dutch, French and German.

The draft manual uses asciidoc markup. Crowdin is able to work with asciidoc. Help is requested for translating the 7 pages now posted on Crowdin. Shock, horror 7 pages. But a graphic approach has been taken. Much of the text relates to buttons used by OpenCPN and already translated and will therefore be suggestions. There are many images (shown by ⌇⇠⇠⇠). I will make the screenshots for the different languages.

We have tested the workflow and if a document has to be amended the translations already in place will carry forward, as for the plugin .POT files.

If you can help with translation your help would be very much appreciated.
https://crowdin.com/project/opencpn
You will find the project listed as Inland ECDIS Manual.
If you need advice about getting started please ask.

Mike

[Rasbats]

Forgot to say ...
There may be readers already using OpenCPN on the EU River System. If the draft manual is missing an important piece of information or you see an error please post here or PM me. But KISS please.

Mike

[Rasbats]

For translators:
btn:
This is markup to format the text that follows.
For example: btn:[Cancel]
It is the Cancel bit that needs translation.
image:2.2.jpg[]
No need for translation.
http://www.gla-rrnav.org/radionaviga...tual_aton.html[Further explanations.]
Only Further explanations needs translation.

There are probably other bits of markup that need treating with caution. Please ask if not sure.

Thanks.
Mike

[bcn]

The German translation is under work now. Started with the AIS part.


Mike, can you have please a look in order to check how the lay-out shows up finally?


I've noticed some minor typos in the EN original. Missing letter etc..

[rgleason]

Mike the manual looks excellent.

[Rasbats]

bcn did great work on the German translation. The manual has been updated for this work.

Some translations got missed because of not wanting to mess up markup:
[Options] [Ships]
AIS Targets

These are button and menu selections. With the German user interface they should appear as:
[Optionen][Shiffe]
AIS-Ziele

A similar situation needs to be avoided when French and Dutch translations are made.

TODO: Need to get the left hand index showing in the relevant language. May need another document in Crowdin.

TODO: Header loses the OpenCPN logo and the title bar at the top of the German and Dutch manual. Why?

Mike

[bcn]

DE translation corrected now - takes some steps to understand what to translate and which mark-ups to ignore..

[Gilletarom]

Originally Posted by bcn

DE translation corrected now - takes some steps to understand what to translate and which mark-ups to ignore..

I started but:

- I move very slowly

- I'm quite perplexed about what should be translated or not.

[bcn]

Originally Posted by Gilletarom

- I'm quite perplexed about what should be translated or not.

Have a look at the German translation:
- don't translate pictures
- with btn[] (=button) only translate the sentence with the brackets
- don't translate URLs

[Rasbats]

TODO: Need to get the left hand index showing in the relevant language. May need another document in Crowdin.

TODO: Header loses the OpenCPN logo and the title bar at the top of the German and Dutch manual. Why?

Header problem now fixed for the logo. The text of the title bar will appear in de, fr, nl when nav.adoc is translated. Only the text in [] in nav.adoc needs translation. Thanks bcn, I see you have already done this.

Left hand index also depends on nav.adoc.

As a test I will grab the de nav.adoc and build the manual again.

For a complete update I have to download 24 files from Crowdin. Trying to avoid doing this too many times and there will be delays.

Mike

[Rasbats]

Left hand index is good for de. The de nav.adoc translation works. I need to make some changes here to get the title bar showing a translation.

Mike

[Rasbats]

All ...

Nearly ready for use:

https://opencpn-manuals.github.io/in.../en/index.html

Much work by bcn, gilletarom, verkerbr. Thanks.

If de, fr, nl readers who use the OpenCPN interface for these languages see any text in the manual that does not make sense please PM/email me. It is intended that the manual follows the sequence of buttons/options that are needed to achieve various tasks.

Some screenshots, especially AIS, retain the en user interface.

A new release of OpenCPN should show "Use Inland ECDIS v2.4" at which point we can ask that OpenCPN is included in the recommended software for use as an Inland ECDIS in the Information Mode on EU inland waterways.

See the manual Introduction for how and why this manual was produced.

Mike

[verkerkbr]

Hi Mike,


Inland barges rely almost all on inland Radar sets. Not the ones that are supported in the Radar plugin.

What is the output from this professinal radars ? Is this output standardised ? Can the output be used as an overlay in OpenCPN ?

Otherwise there must be a warning that these inland sets cannot be used.

The manual gives instructions how to set the ranges of the radar distance rings. But that only works for the digital supported yacht radars.

Bram

[bcn]

OpenCPN complies with "InlandECDIS in Information Mode". A Radar overlay would be a complement and would not qualify to any other thing.


Another confusion here: there a scales predefined by the standard and those are based on typical radar ranges. In order to work with the same view the crew is used to. Does not imply that a Radar is in use at all at that time or system.



To use Radar in a "production environment" we would need to comply with the requirements for the "Navigation Mode", what is not pretended. In that case some hardware holomogations are in place.
As far as I remember, Koden and Furuno are for example Radars used here. There is a list of homologated devices and systems at some place.

Koden does work over Ethernet as Furuno do, but up to now nobody has played with that type of equipment.

[Rasbats]

Bram ...

https://unece.org/fileadmin/DAM/tran...-156-Rev3e.pdf

4.2 Display Ranges (Scales)
(a) In information mode, it is recommended to use the same ranges as specified in navigation mode. All scales and ranges are allowed;

I think R+ and R- should be interpreted as Range and not Radar.

Page 30 of the rules has the ranges specified.

I think we should use the link above in the manual instead of the mandate on the information page.

Mike