/**
     * Sort parameter for error page fallback.
     * Defines the sorting order if redirection fails.
     */
    public String sort;

    /**
     * Language parameter for error page fallback.
     * Specifies the language preference if redirection fails.
     */
    public String lang;

    /**
     * Additional fields map for error page fallback.

### Target language

Translate to Turkish (Türkçe).

Language code: tr.

### Core principle

Don't translate word-by-word. Rewrite naturally in Turkish as if writing the doc from scratch. Preserve meaning, but prioritize fluency over literal accuracy.

### Grammar and tone

- Use instructional Turkish, consistent with existing Turkish docs.
- Use imperative/guide language (e.g. "açalım", "gidin", "kopyalayalım", "bir bakalım").

        print(f"Error processing {path}: {e}")
        return False
    return True


@cli.command()
def fix_all(ctx: typer.Context, language: str):
    docs = get_all_paths(language)

    all_good = True
    for page in docs:
        doc_path = Path("docs") / language / "docs" / page
        res = process_one_page(doc_path)
        all_good = all_good and res

    if not all_good:

     */
    public PopularWordsRequestBuilder addField(final String field) {
        request.addField(field);
        return this;
    }

    /**
     * Adds a language to filter by.
     * @param lang The language.
     * @return This builder instance.
     */
    public PopularWordsRequestBuilder addLanguage(final String lang) {
        request.addLanguage(lang);
        return this;
    }

We welcome pull requests for your language.

### Translations

- [日本語 (Japanese)](docs/ja/README.md)

### Target language

Translate to Japanese (日本語).

Language code: ja.

### Grammar and tone

- Use polite, instructional Japanese (です/ます調).
- Keep the tone concise and technical (match existing Japanese FastAPI docs).

### Headings

- Follow the existing Japanese style: short, descriptive headings (often noun phrases), e.g. 「チェック」.
- Do not add a trailing period at the end of headings.

### Quotes

        request.setSkipDuplicateWords(skipDuplicateWords);
        return this;
    }

    /**
     * Adds a language to filter by.
     * @param lang The language.
     * @return This builder instance.
     */
    public SuggestRequestBuilder addLang(final String lang) {
        request.addLang(lang);
        return this;
    }

    )

    assert fixed_content == expected_content  # Translated doc remains unchanged
    assert "Error processing docs/lang/docs/doc.md" in result.output
    assert (
        "Code block (lines 16-19) has different language than the original block ('yaml' vs 'toml')"
    ) in result.output


@pytest.mark.parametrize(
    "copy_test_files",
    [(f"{data_path}/en_doc.md", f"{data_path}/translated_doc_wrong_lang_code_2.md")],

- **Version Compatibility:**
With Java serialization, even minor changes to a class (like adding a field) can break compatibility.

- **Cross-Language Compatibility:**
Java serialization is inherently Java-centric and does not support cross-language scenarios well.

- **Type Safety:**
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors.

## Decision

### Target language

Translate to Korean (한국어).

Language code: ko.

### Grammar and tone

- Use polite, instructional Korean (e.g. 합니다/하세요 style).
- Keep the tone consistent with the existing Korean FastAPI docs.
- Do not translate “You” literally as “당신”. Use “여러분” where appropriate, or omit the subject if it sounds more natural in Korean.

### Headings

- Follow existing Korean heading style (short, action-oriented headings like “확인하기”).