- icon: fontawesome/brands/linkedin
    link: https://www.linkedin.com/company/fastapi
  - icon: fontawesome/solid/globe
    link: https://tiangolo.com
  alternate:
  - link: /
    name: en - English
  - link: /de/
    name: de - Deutsch
  - link: /es/
    name: es - español
  - link: /fr/
    name: fr - français
  - link: /ja/
    name: ja - 日本語
  - link: /ko/
    name: ko - 한국어

    @Test
    public void testAnalyzeWithDifferentLanguages() {
        // Test analyze with different language settings
        String text = "hello world";
        String field = "content";

        // Test with English
        List<AnalyzeToken> tokensEn = analyzer.analyze(text, field, "en");
        assertNotNull(tokensEn);
        assertEquals(2, tokensEn.size());

        // Test with Japanese

我们欢迎您的语言的 Pull Request。

### 翻译

- [English](../../README.md)
- [日本語 (Japanese)](../ja/README.md)
- [Español (Spanish)](../es/README.md)
- [Português (Brazilian Portuguese)](../pt-BR/README.md)
- [Français (French)](../fr/README.md)

That way, you can edit the documentation/source files and see the changes live.

/// tip

Alternatively, you can perform the same steps that scripts does manually.

Go into the language directory, for the main docs in English it's at `docs/en/`:

```console
$ cd docs/en/
```

Then run `mkdocs` in that directory:

```console
$ mkdocs serve --dev-addr 127.0.0.1:8008
```

///

#### Typer CLI (optional)

/*
 * Tests for Smb2IoctlResponse.
 *
 * Notes:
 * - Comments are in English as requested.
 * - JUnit 5 is used; Mockito is not required here.
 */
package jcifs.internal.smb2.ioctl;

import static org.junit.jupiter.api.Assertions.assertArrayEquals;
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertNotNull;
import static org.junit.jupiter.api.Assertions.assertNull;

    * You can normally quickly detect it by going to the "Files changed" tab in the PR and checking if the updated file(s) starts with `docs/en/docs`. The original version of the docs is always in English, so in `docs/en/docs`.
* `lang-all`: Translations

私たちは、あなたの言語でのプルリクエストを歓迎します。

### 翻訳

- [English](../../README.md)
- [简体中文 (Simplified Chinese)](../zh-CN/README.md)
- [Español (Spanish)](../es/README.md)
- [Português (Brazilian Portuguese)](../pt-BR/README.md)
- [Français (French)](../fr/README.md)

* For new features, the feature should be mentioned in the [Release Notes](platforms/documentation/docs/src/docs/release/notes.md).
* Use American English spelling in code, comments, and documentation (e.g., "color" not "colour", "initialize" not "initialise"). See [ADR-0009](architecture/standards/0009-use-american-english.md) for details.

          "type": "pattern_replace",
          "pattern":"(.*)",
          "replacement":""
        }
      },
      "filter": {
        "stemmer_en_filter": {
          "type": "stemmer",
          "name": "english"
        },
        "english_override": {
          "type":       "stemmer_override",
          "rules_path": "${fess.dictionary.path}en/stemmer_override.txt"
        },
        "possessive_stemmer_en_filter": {

 *     <li><code>ga</code> or <code>final</code></li>
 *     <li><code>sp</code></li>
 *     </ol>
 *     Unknown qualifiers are considered after known qualifiers,
 *     with lexical order (case-insensitive in the English locale).
 *     <code>ga</code> and <code>final</code> sort the same as not having a qualifier.
 *   </li>
 * <li>A hyphen usually precedes a qualifier, and is always less important than digits/number. For example