Update lang_it.json

[bovirus (bovirus)]

Gabriel Dufresne (@GabrielDuf)

• I have read the contributing guidelines, and I agree with the Code of Conduct.
• Have you checked that there aren't other open pull requests for the same changes?
• Have you tested that the committed code can be executed without errors?
• Have you confirmed that this issue is caused by UniGetUI itself, and not by the package manager or the package involved?
  If the same issue can be reproduced outside UniGetUI with the relevant package manager or with the package itself, please report it there first. UniGetUI should only be used to track issues that are specific to UniGetUI's behavior or integration.

---

Italian language update.
Please merge. Thanks.

[bovirus (bovirus)]

Gabriel Dufresne (@GabrielDuf)

Could you please merge this?

Thanks.

[mapi68]

Gabriel Dufresne (@GabrielDuf) This translation introduces several clear errors instead of fixing them. A few examples:

• "UniGetUI Log" → "regsitro di UniGetUI" — typo, missing letter ("registro" spelled wrong).
• "UniGetUI collects anonymous usage data..." → "Per migliorare l'esperienza dell'utenteUniGetUI raccoglie dati di uso anonim ." — missing space between words, truncated word ("anonim" instead of "anonimi"), broken sentence.
• "...vai nele impostazioni di sicurezza..." — typo, should be "nelle".
• "...con percorsi personalizzate" — gender agreement error, should be "percorsi personalizzati" (masculine plural noun with feminine plural adjective).

On top of that, terms like "screenshot" and "log" were translated into "schermate" and "registro". These are standard, widely accepted words in Italian tech/IT vocabulary and are commonly left untranslated in this context; changing them makes the UI feel less natural, not more correct.

We're here to remove errors from the translations, not add new ones. Given the number and nature of these issues, I'd suggest a full revert of lang_it.json to the previous version.

[bovirus (bovirus)]

mapi68

Sorry for the errors. Fixed.

The original Italian translation for many strings could be a word-to-word translation from English to Italian and not a translation that follow up the flow and the rules of an Italian translation. Ex:
Many times use article not necessary.
Use English phrase flow instead Italian phrase flow.

Basing oin my long experience about IT support and translation jobs I believe that terms like "log" and "screenshot" are not italian terms and we have in Italian terms like "registro" and "schermata" that are widely accepted in a modern translation context.

I believe that it's important to innovate.
And if there are some issues the solution is not go back but fix the issues.