Contribute translations

[peter88213]

Would you like to maintain a language pack with translations in your language? Then you can start a sub-thread here and announce your intention in a comment. I might be able to help you set up a repository for the language pack and take the first steps.

[oldstonegryzzly]

Italiano

Hi,
I've completed the Italian translation for Novelibre (it.po) and uploaded it to my GitHub repository. You can find it here:

https://github.com/oldstonegryzzly/po-novelibre-it/blob/main/it.po

Feedback and suggestions are welcome!
Thanks,
Sandro

[peter88213]

In the meantime, I added a heading to the start of this thread to indicate the language.
The Italian language pack has now the version number 1.0.0.

• I fixed one translation: "Forward" = "Inoltrare"
• I "translated" the help file URL, so the Online user guide command leads to the Italian help pages on https://peter88213.github.io/nv_it/
• I created basic help pages where the technical terms of the novelibre user interface are translated using the translations provided by @oldstonegryzzly. However, the rest of the text is still in English and should be translated sooner or later.

[peter88213]

The GitHub pages of the language pack repository now serve as an Italian-language entry point for novelibre. I have also enabled the discussion pages and the wiki for those who want to contribute to the Italian-language documentation without translating the existing help pages.

[oldstonegryzzly]

Wait, wait... :-) sorry, I'm just seeing the message. As soon as I have a few hours to devote to the project, I'll do it.

Also, using the software, I noticed that some of the translated words don't match the context. I'll change them... let's just say my translation is still in beta ;-)

Regards.

Sandro

[peter88213]

That's great. Now the nv_it language package is available as a versioned plugin, so the nv_updater plugin can check for updates of the language pack.
The versioning system is as follows:

• The version number is <major number>.<minor number>.<patchlevel>.
• The major and minor version numbers of a language pack are the same as those of the corresponding novelibre version.
• The patchlevel is increased whenever translations are updated or plugin translations are added.
• Before building a new release via tools/build.py, the version number is to be entered in this script, editing the VERSION string.

I prepared the it.po files for all plugins. You will find them in the subdirectories of modules. Before building a new release,
all it.po files must be complete.

• New translations are to be entered in the it.po files.
• Changed translations are to be entered in the dictionary/msg_dict.json file. This dictionary is used by the build scripts
  for entering all known translations. It is also used for automatic generation of language-specific help text templates.

The Italian help text pages are located in docs/help, waiting for completion.

• Anyone who wants to can edit the existing .md files to complete the translation.
• I'm still in the process of creating the missing template pages for the plugins. I'll let you know when I'm done (*).
  However, this may take a few more days because I want to finish the new version 5.43 of novelibre first (see Add Cut/Copy/Paste commands to the tree view context menu #74):

Over the last few days, I have expanded and optimized the build mechanism for the language pack with the help of data for the Italian translation. The current status now also corresponds to the template repository nv_xx, which can be used to generate new language packs for additional languages with little effort.

If this all seems rather complicated to you right now: basically, it's just a matter of first completing all it.po files in the subdirectories of modules. Once that's done, I can generate the new release.

Cheers,
Peter

---

(*) Update

Now all help page templates are ready. As soon as the plugin translations are complete, just run the tools/prepare_help_pages.py script to replace the placeholders with the translated terms.

[peter88213]

I noticed that some of the translated words don't match the context. I'll change them...

It would be sufficient for me if you could provide an exchange list in your reply, following the pattern

"old term 1": "new term 1",
"old term 2": "new term 2",

etc.

I will then enter the changes in the central dictionary and revise the existing help texts. More specifically, I will write a script that will handle these processes in the future.
You don't need to enter this in the it.po file; it will be done automatically when the release is built.