S63_PI Beta Test 0.4.0

[Gilletarom]

Originally Posted by AISEAG

Hello Gerhard,

take off the "s" from "le dossiers des applications"

Thanks

Serge

Oups ... Et le pire c'est que je me suis relu ....

Merci Serge.

[Gilletarom]

Hello dave,

Originally Posted by bdbcat

Gilletarom....
.......
4. So, what we want to know is this: disregarding language file problems, if s63_pi.dll is in the correct place, can you load and view the s64 test set charts?
.....
Dave

Then :
For authority to operate the S63, S63 I moved the folder and I put it manually in the "plugins" folder.

In this case, I can activate the plugin S63. Then I set up the UserPermit. Then I set up the InstallPermit.

After which I loaded "PERMIT.TXT" file 8b, using the button "Import cells permit ...".

The charts are loaded. But I have no border line card. And nothing in the bar chart.

See screen copy.

[CarCode]

The Mac OS X installer for S63 plugin can be downloaded here:
http://topperdiek.de/dl/S63-Plugin.pkg

But it will work only with an updated Info.plist file in Contents folder because the original Mac version from opencpn.org has no version number. So copy Info.plist (discard .doc) from the attachment to Contents of the OpenCPN folder.
Dave:
The CFBundleIdentifier string must be org.opencpn and not opencpn.org (Apples domain notification).

First 2 pictures for a french version without updated Info.plist file.

Pictures 3 to 10 with updated Info.plist file. User password needed.

Gerhard

[bcn]

ES

"S63 Plugin for OpenCPN"
Plugin S63 para OpenCPN

"OpenCPN version 3.3.1606 not found."
OpenCPN versión 3.3.1606 no encontrado

"Please install first OpenCPN version 3.3.1606 in Applications folder."
Instale por favor primero OpenCPN versión 3.3.1606 en la carpeta de Aplicaciones

[CarCode]

http://topperdiek.de/dl/S63-Plugin.pkg updated with spanisch strings.

Gerhard

[bdbcat]

Gilletarom...

1. You have discovered this: If you manually adjust the S63_pi install location, as for a parallel OCPN install, then you should choose something like

C:\Program Files\OpenCPN 3.3.1606\plugins

as the install location. Note the trailing "plugins" specification.
Perhaps the installer can be made to verify that one has selected a good location, and give info if needed.

2. After installing the PERMIT.TXT file, you must use the function "Import Charts/Updates" to actually bring the S63 chart cells into the OCPN database. In this file dialog, you will choose the "ENC_ROOT" directory which will be found in the same general tree as the PERMIT.TXT file was found.

Sorry for the fussyness. Soon to be better.

Thanks
Dave

[bdbcat]

Gilletarom...

Correction to my previous:

If you manually adjust the S63_pi install location, as for a parallel OCPN install, then you should choose something like

        C:\Program Files\OpenCPN 3.3.1606\plugins\s63_pi

as the install location. Note the trailing "plugins\s63_pi" specification.

Thanks
Dave

[Gilletarom]

Originally Posted by bdbcat

Gilletarom...

        C:\Program Files\OpenCPN 3.3.1606\plugins\s63_pi

as the install location. Note the trailing "plugins\s63_pi" specification.

Dave

Hello Dave,

Phew ... I managed ... In truth, you managed to make me succeed.. So thank you.

I must say that I understood, in the first three versions of the S63 plugin, should be retained / plugins / in the installation path. But with the 04 version, I forgot that. Gilletarom --->

Originally Posted by bdbcat

2. After installing the PERMIT.TXT file, you must use the function "Import Charts/Updates" to actually bring the S63 chart cells into the OCPN database. In this file dialog, you will choose the "ENC_ROOT" directory which will be found in the same general tree as the PERMIT.TXT file was found.

On the "import" button, I had tried. But I was not down in the tree until ENC_ROOT folder.

I must say that OpenCPN has accustomed me down, automatically, in the tree, looking chart files.

On the other hand, for example with the 8b test cells import is permitted once. But loading maps is done 3 times because there are 3 folder ENC_ROOT (In cases B1, B2 and B3).

This is really not practical. It seems to me that the error made ​​Gilletarom will also make the mistake that many alpha users.

In my opinion, a specific aid plugin S63, well written and translated into all languages ​​is welcome. Help available with a "Help" button.

Best regards, Gilletarom.

[CarCode]

Gilletarom,

hopefully there will be a detailed How-to at o-charts.org once buying s63 charts for everyone will be possible. So we have to wait until then. Right now it is still a beta test.

Gerhard

[bcn]

The case of the S-64 test sets with several end-root folders is a bit special and should not happen in a "real" environment.

When you buy a chart set you will have one permit.txt file and one folder with the files you bought under "enc root". In the case of ChartWorld for example these come in two zip files that contain some more data.

It seems that there are some differences how the different vendors do interpret the S-63 but we should see always those two items.
There will be some learning while we encounter these stuff, I suppose.

Hubert

[bdbcat]

Hello testers....

We now come to the time to make translations of the S63_pi Windows Installer text messages.

The format is not like the OCPN .pot system. It is more similar to the OCPN Windows installer message system, translated long ago.

I have take the liberty of creating some translations already. But these need checking by a native language speaker. And some languages are not done at all....

So, you may access the "template" files at
https://github.com/bdbcat/s63_pi/tre...nguage%20files

Each of these files corresponds to a specific language. Each file contains a commented line of English, with the translated text following. For example, here is an entry from the French file:

#LangString Page_TypeInst_Subtitle_Exists ${LANG_ENGLISH} "@CPACK_PACKAGE_NAME@ @CPACK_PACKAGE_VERSION@ is already installed."
LangString Page_TypeInst_Subtitle_Exists ${LANG_FRENCH} "@CPACK_PACKAGE_NAME@ @CPACK_PACKAGE_VERSION@ est déjà installé."

You will see clearly the format of the translated text, especially the term "${LANG_FRENCH}. Also, please be sure to use UTF-8 encoding for the file editing.

So, the job is to download the Langstrings_{your language}.nsh.in, enter the translated text, and submit the resulting ".in" file here, or email to me directly. These files will end up in the public git repository, and may be maintained as any other source file.

We shall have a Beta 0.5.0 fairly soon, in order to fix the known problems with the Windows installer, and other small bugs. I would like to include these updated installer translations if possible.

Thanks, and Good Luck
Dave

[bcn]

Spanish is ok.

Hubert

[bcn]

The German as well.

There are no S63-Pi specific literals. Is this ok?

Hubert

[bdbcat]

Hubert...

The macros "@CPACK_PACKAGE_NAME@" and "@CPACK_PACKAGE_VERSION@" are substituted at build time, and become, magically, "S63_PI" and "0.4.0".

Voila.
Dave

[CarCode]

German checked and is ok.

Dave:
The CFBundleIdentifier string must be "org.opencpn" and not "opencpn.org" (Apples domain notification). Please update the Info.plist when you compile also a new OpenCPN version for Mac OS X.

Gerhard