This way, we can notice when there are new translations ready, because they have the `approved-1` label.

## Merge Translation PRs

Translations are generated automatically with LLMs and scripts.

There's one GitHub Action that can be manually run to add or update translations for a language: [`translate.yml`](https://github.com/fastapi/fastapi/actions/workflows/translate.yml).

    logging.debug(f"Using translations map: {lang_to_discussion_map}")

    # Messages to create or check
    new_translation_message = f"Good news everyone! 😉 There's a new translation PR to be reviewed: #{pr.number} by @{pr.user.login}. 🎉 This requires 2 approvals from native speakers to be merged. 🤓"

### List of English terms and their preferred German translations

# Test translation fixer tool { #test-translation-fixer }

## Code blocks with and without comments { #code-blocks-with-and-without-comments }

This is a test page for the translation fixer tool.

### Code blocks with comments { #code-blocks-with-comments }

The following code blocks include comments in different styles.
Fixer tool should fix content, but preserve comments correctly.

```python
# This is a sample Python code block

* Retranslate, having the good translation in place. The ideal result would be that the LLM makes no changes anymore to the translation. That means that the general prompt and your language specific prompt are as good as they can be (It will sometimes make a few seemingly random changes, the reason is that [LLMs are not deterministic algorithms](https://doublespeak.chat/#/handbook#deterministic-output)).

- Never change ellipsis in code, URLs, or CLI examples.

### Preferred translations / glossary

- Should avoid using simplified Chinese characters and terms. Always examine if the translation can be easily comprehended by the Traditional Chinese readers.
- For some Python-specific terms like "pickle", "list", "dict" etc, we don't have to translate them.
- Use the following preferred translations when they apply in documentation prose:

- request (HTTP): 請求

 */
package org.apache.maven.configuration;

import java.io.File;

/**
 * A path translator that resolves relative paths against a specific base directory.
 *
 */
public class BasedirBeanConfigurationPathTranslator implements BeanConfigurationPathTranslator {

    private final File basedir;

    /**
     * Creates a new path translator using the specified base directory.
     *

## Top Translation Reviewers

These users are the **Top Translation Reviewers**. 🕵️

Translation reviewers have the [**power to approve translations**](contributing.md#translations) of the documentation. Without them, there wouldn't be documentation in several other languages.

<div class="user-list user-list-center">

This guide explains how to add internationalization (i18n) support for a new language in Fess.

## Overview

Fess uses a two-tier language support system:

1. **Full UI Translation** (13 languages): Complete user interface translation with label and message files
2. **Search/Analysis Support** (40+ languages): Language-specific text analysis for search indexing

Cgo's most interesting translation is for functions.  If xxx is a C
function, then cgo rewrites C.xxx into a new function _C_xxx that
calls the C xxx in a standard pthread.  The new function translates
its arguments, calls xxx, and translates the return value.

Translation of parameters and the return value follows the type
translation above except that arrays passed as parameters translate