Translate

Languages can be barriers to understanding. We want to make sure that Tuist is accessible to as many people as possible. If you speak a language that Tuist doesn't support, you can help us by translating the various surfaces of Tuist.

Since maintaining translations is a continuous effort, we add languages as we see contributors willing to help us maintain them. The following languages are currently supported:

• English
• Korean
• Japanese
• Russian
• Chinese
• Spanish
• Portuguese

REQUEST A NEW LANGUAGE

If you believe Tuist would benefit from supporting a new language, please create a new topic in the community forum to discuss it with the community.

How to translate

We have an instance of Weblate running at translate.tuist.dev. You can head to the documentation project website, create an account, and start translating.

Translations are synchronized back to the source repository using GitHub pull requests which maintainers will review and merge.

DON'T MODIFY THE RESOURCES IN THE TARGET LANGUAGE

Weblate segments the files to bind source and target languages. If you modify the source language, you'll break the binding, and the reconciliation might yield unexpected results.

Guidelines

The following are the guidelines we follow when translating.

Custom containers and GitHub alerts

When translating custom containers or GitHub Alerts, only translate the title and the content but not the type of alert.

Example with GitHub Alert

    > [!WARNING] 루트 변수
    > 매니페스트의 루트에 있어야 하는 변수는...

    // Instead of
    > [!주의] 루트 변수
    > 매니페스트의 루트에 있어야 하는 변수는...
    ```

Example with custom container

    ::: warning 루트 변수\
    매니페스트의 루트에 있어야 하는 변수는...
    :::

    # Instead of
    ::: 주의 루트 변수\
    매니페스트의 루트에 있어야 하는 변수는...
    :::

Heading titles

When translating headings, only translate tht title but not the id. For example, when translating the following heading:

# Add dependencies {#add-dependencies}

It should be translated as (note the id is not translated):

# 의존성 추가하기 {#add-dependencies}