Italian translationbrowsing

This is my proposal for Notepad++ 6.7.9.2
It’s base on 6.7.9 Italian translation of ices_eyes
I found some parte of GUI not translated andd with strings mnot included in language file. Please check the screenshots.

It’s difficult to keep translations in sync because it requires manual steps and extra code. I don’t know what has been said about translations, but if I were a translator I would do all my work against this file:

It is the absolute latest english.xml from the N++ source code repository (for the 6.x versions).

It contains the strings for sorting and also for “Custom Backup Directory”.

“Global Styles: …” is unfortunately hardcoded into the program and can’t be translated without making changes to the code.

I will see about making the auto-completion GUI a bit wider so the Italian strings fit.

I think the easiest way to get translations into the official N++ repository is to create so called pull requests on Github (see link above). But I get that not everyone has the time or patience to learn about that since it’s a bit programmer-specific.

If I understand how to upload the translation file into the repository, it is not a problem for me to do that. It should take the same time to send every time a mail to Don the new file. But I’m wondering if there’s a way to do that without the need to install a full git client and so on, I’m new to github at the mmoment. Looking into the possibility to have notifications for new commit only for the localization flder!
Some times ago I started also to try do develop a tool to maintain the translations updated with that of the english.xml, but since that was always outdated, or we could have that only after a new version is out, I let it die as a project. An idea I had was to add the translations file on the “pugin manager” plugin, it should not be too difficult to make a piece of code that check the translaion version on the installed files and verify it on the server, as it already do with the plugins…

@ Roberto: the custom backup directory string has chenged its ID, so the problem there is that the italian localization still use the old one. I had no idea of this change, so will fix it. For the other string not localixed, try to see if the nativeLang.xml and italian.xml files match. If not, try to put english and then again italian :)

@jonandr
As first step I believe that should be update the Italian language into the repository with an update Italian version.
I will check the strings and I will update it.
When we will post the new language file please update it into the repository.

@Ices_Eyes
I already tried to change Italian -> English -> Italian to show all changes.
But I found the same problem.

Please take care that the order the lines order between English & Italian language is different.
The Italian use “normal” numeric order than English one use not always numeric id order.
To make a good compare we have to decide if the Italian language have to follow English one order or the English could have a numeric standard order.

I made an attempt to update my (Hungarian) translation using this pull request thing, to check this method. It’s easy. I created a small guide for us beginners. We could create a new topic here including these infos, if you agree. Please let me know your thoughts:

Have a gmail account which will be used to login to this Notepad++ community.
Note: It’s suggested to create a new account dedicated for translation work.

Create account on github.
Note: It’s suggested to use the previously created email.

When you prepare your XML language file in Notepad++, it’s suggested to use the “Edit -> Blank Operations -> Trim Trailing Space” function, to remove needless spaces at end of lines, because the Github will list the space differences, and that’s just unnecessary work when checking the diff.

Many thanks for your detailed guide.
I propose you (if the admins are agree) to create a specific post for your explanation how to update github translation because I believe that can be very useful for many translators.

Did you check if also in your translation Macro -> “Trim trailing and save” remain untranslated (no string in original master English file)

Hi!
I did not mean the Macro named “Trim Trailing and Save”, rather I meant the native Notepad++ function build in the menu:
Edit -> Blank Operations -> Trim Leading and Trailing Space.
The Macro is not translatable indeed, however the menu is.

HOWEVER, I was wrong! I didn’t fully check. Do not use this “Trim Leading and Trailing Space” menu, because it removed also the indent of lines! Only the trailing spaces need to be removed.
So please use “Edit -> Blank Operations -> Trim Trailing Space”!
I’ll modify the user guide.

Roberto, I don’t know what translation version you are using for comparison, but I do not find all the modification you are doing in the latest available. For exam,ple it seems you have deleted the strings
<Item id = “44011” name = “Finestra impostazioni personalizzate…” />
<Item id = “44012” name = “Nascondi margine numeri di riga” />
<Item id = “44013” name = “Nascondi margine segnalibri” />
<Item id = “44014” name = “Nascondi margine cartella” />

But all those strings are menu entry currently available in notepad++, and the translations are needed…

Yeah. But the english.xml file is not always correct, and does not include all the strings available in Notepad++. English strings are embeddend in the code other that in the xml file. So if some strings are not available in the language files they are still visible in the program. I will pull a request of update with my version of 6.9.7.2 translation, that I’m sure have almost any translatable string in it. I had made a cleanupo of the file not so long time ago. :)