Skip to content

Introduce translation guidelines #1810

@suryabdev

Description

@suryabdev

An old PR #794 removed the translation guide section because it pointed to an invalid link.
It may have be a leftover section from when the smolagents code was in the transformers repo.

The transformers repo includes a TRANSLATING.md file that outlines a nice process.

TLDR ☝️

  1. An issue (if it does not exist) is created listing the files that should be translated for each target language.
  2. Once a file is translated, it is checked off the list.
  3. Another native speaker approves translation PRs after proofreading (Example). Maintainers then merge the change.
  4. The issue acts as tracker.

So far, smolagents has Chinese, Korean and Hindi translations (Spanish soon #1806!). Maybe we could follow the same process as transformers.

I created a draft PR #1811 to copy over the TRANSLATING.md file and added a GitHub issue template, as done in transformers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions