> 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/v26-fr-fr/guide-de-lutilisateur-de-parallels-desktop-pour-mac-26/installer-ou-mettre-a-niveau-parallels-desktop/determiner-la-langue.md).

# Déterminer la langue

Parallels Desktop pour Mac 26 prend en charge les langues suivantes : français, allemand, anglais, espagnol, italien, polonais, portugais (Brésil), tchèque, chinois simplifié, chinois traditionnel, coréen et japonais.

Par défaut, Parallels Desktop affiche ses menus dans la même langue que l'interface de votre Mac, à condition qu'il s'agisse de l'une des langues répertoriées ci-dessus.

Vous pouvez changer de langue en procédant comme suit :

1. Quittez Parallels Desktop.
2. Choisissez le **menu Apple** > **Préférences système** > **Général** > **Langue et région**.
3. Faites défiler la fenêtre jusqu'en bas et recherchez la section intitulée **Applications**.
4. Dans **Parallels Desktop**, utilisez le menu déroulant pour sélectionner l'une des langues d'interface prises en charge par 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 dynamically 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/v26-fr-fr/guide-de-lutilisateur-de-parallels-desktop-pour-mac-26/installer-ou-mettre-a-niveau-parallels-desktop/determiner-la-langue.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 `build a script that syncs our docs to a CMS` 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.