[Test] Italian User Interface

[Diama]

Here is my italian translation.
If someone is familiar with the Italian language, can this translation test?
Create folder "lang" and extract in folder "it".

[admin]

Sorry, but your pack is not ready for testing. It has tons of technical issues, some of which would make Atlantis crash.

It needs to be manually revised by a human according to the instructions from the "read me" file.

[Diama]

I have now manually reviewed the translation and no longer seems to have the initial problems.
I tested it in every way and there are no crash to malfunctions.
Now I can say that the translation is really good.
If there are Italian users interested, he urges them to try it and report any improvements.
Unfortunately, the author does not seem to appreciate this work.

[admin]

Sorry, but no one urged anyone to test your pack. The opposite is true: there is nothing to test.

You can create language packs of any quality for your personal use. However, in order to be included in the official repository, a language pack must meet certain quality standards.

When done properly, automatic translation can be the first step toward creating a language pack. After that, all the resource files from the pack must be thoroughly revised by a native speaker familiar with Atlantis and the text processing terminology. File by file. Line by line.

You have used the automatic tools to do the translation. And to be honest, you do not even need to be a native speaker to do this part. Nevertheless, the problems started at this first stage. You have not read the instructions from the “read me” file from the translation kit, and your automatic tools translated literally everything, including identifiers, “original” text and technical comments. As a result, the structure of most files from the pack has been ruined.

Let’s take item #140 from General.txt from the translation kit. Only the text highlighted in red was supposed to be translated:

------------------------------------

140;SSave

;caption of the "Save" button

;original:
;-------
;Save
;-------

;translated:
;-------
Save
;-------

------------------------------------

Now look at the corresponding item from your translated file:

------------------------------------

140;SSalva

;didascalia del pulsante "Salva".

;original:
;-------
;Salva
;-------

;translated:
;-------
Salva
;-------

------------------------------------

Even if someone decided to revise your automatically generated file, this would be hard to do. How can one know that “Salva” is a correct translation if there is no original text for reference? The only way to make sure that your translation is correct is to open the original file and locate the resource in question. Which makes revising your files much harder. Maybe even harder than translating everything from scratch.

I am not recommending your pack not only for testing, but even for further revision by a human. Creating a brand new translation seems to be a better option. I am saying this because I have checked your pack and I know how few efforts have been put into its creation. There is not the smallest sign that your pack was revised by a human. I will give two more examples:

1. Right off the bat (or to be more correct, right from the pack) your “General.txt” tells everything about the quality of the pack. The first two items in the file (yes, with ruined original content):

------------------------------------

100;RID_ProductTitle[false]

;il nome dell'app (la versione completa)

;original:
;-------
;Atlantis Word Processor
;-------

;translated:
;-------
Elaboratore di testi Atlantide
;-------





101;RID_ProductTitle[true]

;il nome dell'app (la versione Lite)

;original:
;-------
;Elaboratore di testi Atlantis Lite
;-------

;translated:
;-------
Elaboratore di testi Atlantis Lite
;-------

------------------------------------

So how did you decide to translate “Atlantis” - as “Atlantide” or “Atlantis”?

2. I have encountered three (!) different translations of “Clippy Bank” in your files – “appunti”, “Banca Clippy”, and “Clippy Bank”.

The amount of ... issues in your pack is ridiculous.

The UI language pack cannot be created in a couple of hours and with such a level of negligence, especially if you do not stick to the instructions.

[Diama]

Updated!
I have adjusted everything it was reported.
Technical issues, including identifiers, “original” text and technical comments, Atlantide, Clippy Bank, ...
Notify me if there are other problems.