> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v27-it-it/guida-utente-di-parallels-desktop-per-mac-27/installare-o-aggiornare-parallels-desktop/impostazione-della-lingua.md).

# Impostazione della lingua

Parallels Desktop per Mac 27 supporta le seguenti lingue: inglese, francese, tedesco, italiano, spagnolo, ceco, polacco, portoghese (brasiliano), giapponese, coreano, cinese semplificato e cinese tradizionale.

Per impostazione predefinita, i menu di Parallels Desktop sono visualizzati nella stessa lingua impostata nell'interfaccia del Mac, a condizione che sia una delle lingue indicate sopra.

È possibile modificare la lingua tramite la seguente procedura:

1. Esci da Parallels Desktop.
2. Scegli **menu Apple** > **Preferenze di Sistema** > **Generale** > **Lingua e regione**.
3. Scorri fino in fondo fino alla sezione **Applicazioni**.
4. In **Parallels Desktop**, tramite il menu a discesa, seleziona una delle lingue dell'interfaccia supportate da Parallels Desktop.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pdfm-ug/v27-it-it/guida-utente-di-parallels-desktop-per-mac-27/installare-o-aggiornare-parallels-desktop/impostazione-della-lingua.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.