},
      "russian_stemmer": {
        "type":       "stemmer",
        "language":   "russian"
      },
      "spanish_stop": {
        "type":       "stop",
        "stopwords":  "_spanish_"
      },
      "spanish_keywords": {
        "type":       "keyword_marker",
        "keywords": ["¡Hola", "mundo", "búsqueda"]
      },
      "spanish_stemmer": {
        "type":       "stemmer",

      },
      "russian_stemmer": {
        "type":       "stemmer",
        "language":   "russian"
      },
      "spanish_stop": {
        "type":       "stop",
        "stopwords":  "_spanish_"
      },
      "spanish_keywords": {
        "type":       "keyword_marker",
        "keywords": ["¡Hola", "mundo", "búsqueda"]
      },
      "spanish_stemmer": {
        "type":       "stemmer",

      },
      "russian_stemmer": {
        "type":       "stemmer",
        "language":   "russian"
      },
      "spanish_stop": {
        "type":       "stop",
        "stopwords":  "_spanish_"
      },
      "spanish_keywords": {
        "type":       "keyword_marker",
        "keywords_path": "${fess.dictionary.path}es/protwords.txt"
      },
      "spanish_stemmer": {

      },
      "russian_stemmer": {
        "type":       "stemmer",
        "language":   "russian"
      },
      "spanish_stop": {
        "type":       "stop",
        "stopwords":  "_spanish_"
      },
      "spanish_keywords": {
        "type":       "keyword_marker",
        "keywords":   ["¡Hola"]
      },
      "spanish_stemmer": {
        "type":       "stemmer",

the ones with the label for your language. For example, for Spanish, the label is [`lang-es`](https://github.com/fastapi/fastapi/pulls?q=is%3Aopen+sort%3Aupdated-desc+label%3Alang-es+label%3Aawaiting-review).

You can also review already merged translation PRs. To do this, go to the [closed pull requests](https://github.com/fastapi/fastapi/pulls?q=is%3Apr+is%3Aclosed) and filter by your language label. For example, for Spanish, you can use [`lang-es`](https://github.com/fastapi/fastapi...

For example, if you were translating to Spanish, you would write:

/// note | Nota

Some examples in Spanish:

Source (English):

/// tip

Result (Spanish):

/// tip | Consejo

Source (English):

/// details | Preview

Result (Spanish):

/// details | Vista previa

### Tab blocks

* Do not finish the title with a period (`.`).
* When the PR is for a translation, start with the `🌐` and then `Add {language} translation for` and then the translated file path. For example:

```Markdown
🌐 Add Spanish translation for `docs/es/docs/teleporting.md`
```

Once the PR is merged, a GitHub Action ([latest-changes](https://github.com/tiangolo/latest-changes)) will use the PR title to update the latest changes automatically.

          - update-outdated
          - add-missing
          - update-and-add
          - remove-removable
      language:
        description: Language to translate to as a letter code (e.g. "es" for Spanish)
        type: string
        required: false
        default: ""
      en_path:
        description: File path in English to translate (e.g. docs/en/docs/index.md)
        type: string
        required: false

    )

    // (I) Russian (Cyrillic)
    testEncodeDecode(
      unicode = "почемужеонинеговорятпорусски",
      punycode = "xn--b1abfaaepdrnnbgefbadotcwatmq2g4l",
    )

    // (J) Spanish
    testEncodeDecode(
      unicode = "PorquénopuedensimplementehablarenEspañol",
      punycode = "xn--PorqunopuedensimplementehablarenEspaol-fmd56a",
    )

    // (K) Vietnamese
    testEncodeDecode(

Translate to Spanish (español).

Use the informal grammar (use "tú" instead of "usted").

For instructions or titles in imperative, keep them in imperative, for example "Edit it" to "Edítalo".

---

For the next terms, use the following translations:

* framework: framework (do not translate to "marco")
* performance: rendimiento
* program (verb): programar
* code (verb): programar
* type hints: anotaciones de tipos