기여하기

This guide uses French (fr) as an example, but other language codes can be used. Replace /fr in this guide with the code for your desired language.

The currently available languages can be checked on the online translation interface or in the underlying git repository.

Simple Contribution

The preferred way to contribute to the translation effort is via the web-based interface, currently hosted on Weblate.

Suggestions for translations can be contributed without logging in. They will be reviewed by the translation team before being published.

Weblate also provides tools such as the glossary to improve translation consistency.

Advanced Operations

If the web-based interface does not suit your needs, PO-files can be downloaded, edited locally, and uploaded back to the platform.

경고

Conflicts may arise if updates occur while editing locally. Resolving conflicts manually will be required. Direct commits to the translation repository are no longer permitted.

참고

Uploading or integrating PO files can take several minutes. If a server timeout error appears after ten minutes, refresh the page to confirm whether the upload succeeded.

Installing

Before proceeding with translation tasks, ensure the manual builds correctly by following the Getting Started section.

Language Files

Run the following command from the manual’s root directory:

make checkout_locale

You will be prompted to specify the language folder to download. For example, type fr for French and press Return. The command creates a locale/fr subdirectory after downloading.

Example directory structure:

You should have a directory layout like this:

blender-manual
   |- locale/
   |  |- fr/
   |  |  |- LC_MESSAGES/
   |- manual/

참고

When using Git from the command line, switch to the locale directory for updates instead of the blender-manual directory.

Alternatively, download the PO files directly from Weblate by navigating to the Files menu on the language’s page.

PO-File Editor

To edit the PO files, install a PO-file editor to modify the translation files. Poedit is recommended, but other editors are also suitable.

Building with Translations

To build the manual with translations applied run the following commands in a terminal:

  • Linux/macOS:

    make -e BF_LANG=fr
    
  • Windows:

    set BF_LANG=fr
    make html
    

Editing Translation Files

The PO files in the LC_MESSAGES folder include:

  • blender_manual.po: The main file containing user manual translations.

  • sphinx.po: A smaller file for translating the website theme.

  1. Use the PO editor to open these files. Each entry represents a section of the manual.

  2. Translate any untranslated strings using the input field provided by the editor.

  3. Save changes and upload the modified .po files back to Weblate.

Sort entries in the editor by source or translation status to make navigation easier.

중요

Build the manual after translating to check for syntax errors, which will appear as warnings will appear during the build process.

유지보수

Keeping Track of Fuzzy Strings

When the manual is updated, outdated translations are marked as fuzzy. To track these run:

make report_po_progress

For a detailed report, run:

python tools/translations/report_translation_progress.py locale/fr/

This lists files with fuzzy or empty strings. For more options, see:

python tools/translations/report_translation_progress.py --help

Updating PO Files

Administrators regularly update PO files to match the latest English manual (typically weekly). The last update can be checked on the Blender Manual Translations project page.

Translators can update files locally using:

make update_po

However, uploading these files to Weblate is not permitted.

더 보기

Adding a Language