it: update translation

[henrythebuilder]

Context: #537

Update the Italian translation (po/it.po) from latest source and update first three sections:

• Summary
• Welcome
• Day 1: Morning

Enrico

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[detro]

@henrythebuilder thank you for this, it's quite long so it's going to take a while for me to go through it, so bear with me.

Meanwhile, could you please go through the CLA process? Please see https://github.com/google/comprehensive-rust/pull/974/checks?check_run_id=15059836270

[henrythebuilder]

@henrythebuilder thank you for this, it's quite long so it's going to take a while for me to go through it, so bear with me.

Meanwhile, could you please go through the CLA process? Please see https://github.com/google/comprehensive-rust/pull/974/checks?check_run_id=15059836270

Thanks for response.
I did the procedure for the CLA process: 'Individual agreements' done.

[henrythebuilder]

The changes seem to be many but it should be kept in mind that some have remained the same and others have only been modified in part. It should be noted that the initial refresh procedure ('Generating the PO Template' + 'Refreshing an Existing Translation') modified the initial file on which I worked.
However, if it helps, I attach the 'patch' file for the new changes compared to the original 'regenerated' (it-update-translation.patch.txt)

[mgeisler]

@henrythebuilder thank you for this, it's quite long so it's going to take a while for me to go through it, so bear with me.

Meanwhile, could you please go through the CLA process? Please see https://github.com/google/comprehensive-rust/pull/974/checks?check_run_id=15059836270

@detro, just in case you haven't seen it: you can review the commits one-by-one and then you get the changes are much more manageable:

[henrythebuilder]

Need help:
I got news by email that the PR integration failed -> PR run failed: Test, Attempt #2 - it: update translation (9496e96)
Errors look like this: 'msgid' and 'msgstr' entries do not both end with '\n'
The error seems easy to fix by inserting a '\n' where needed, but it must be taken into account that in the translation the subdivision of the pragraph in English (with '\n') does not always coincide with that of the translated language.
So I ask you for support on how to handle this issue.
thanks in advance

edit: I made a new commit in the 'it-translation' branch as fix attempts!

[detro]

This is excellent @henrythebuilder. Thank you so much for doing this, and thanks for partitioning your work into manageable commits, so to make the review easier.

I have mostly found a few typos and maybe one or two suggestions: should be easy to address or tweak.

In regards to the error you got:

'msgid' and 'msgstr' entries do not both end with '\n'

I admit I'm very much new to the .po format, and I leave it to @mgeisler to suggest if the workaround you put in place is the right one. But I do agree with you that it seems odd and might end up with odd formatting (i.e. line breaks where they are not needed).

Anyway, once those small issues are solved, I'd be happy to approve.

Thanks again for this.

[henrythebuilder]

I updated the branch henrythebuilder:it-translation!

[henrythebuilder]

Thanks

[detro]

Thank You Enrico ;)

[mgeisler]

In regards to the error you got:

'msgid' and 'msgstr' entries do not both end with '\n'

I admit I'm very much new to the .po format, and I leave it to @mgeisler to suggest if the workaround you put in place is the right one. But I do agree with you that it seems odd and might end up with odd formatting (i.e. line breaks where they are not needed).

@henrif75 is now helping with all things related to the translations.

Here, the problem is that source text (msgid) and translation (msgstr) fields don't match in the way they use newlines. It's a very simply filter implemented with msgfmt and it doesn't actually know about the Markdown syntax used here. For us, an extra newline is mostly harmless since we split the Markdown text on \n\n+ anyway — but when translating a GUI program, it would looks very weird if "File" becomes "File\n" in the translation.