Understanding Transifex

Translators use Transifex to translate the strings in the standard’s schema, codelist and documentation files from the source language (English) to other languages.

Projects and resources

Transifex is organized into projects, like OCDS 1.1. Projects contain resources, which contain strings to be translated.

Strings to be translated

From CSV codelists

In OCDS, the strings in the codelists resource are extracted from the CSV files in schema/codelists/*.csv. They provide the content for the codelist tables on the codelists page.

In OC4IDS, the strings in the infrastructure-codelists resource are extracted from the CSV files in schema/project-level/codelists/*.csv. They provide the content for the codelist tables on the codelist reference page.

From JSON Schema

In OCDS, the strings in the schema resource are extracted from the JSON files in schema. They provide the content for:

In OC4IDS, the strings in the infrastructure-schema resource are extracted from the JSON files in schema. They provide the content for:

From OC4IDS mappings

In OC4IDS, the strings in the infrastructure-mappings resource are extracted from the CSV files in mapping. They provide the content for the mapping tables on the pages in the CoST IDS and OCDS mapping section.

From Markdown files

With the exceptions of the above resources, each resource sources its strings to be translated from a single Markdown (.md) documentation file in the docs directory tree. These files provide the content for https://standard.open-contracting.org/latest/en/.

For example, the resource getting_started–contracting_process sources strings from docs/getting_started/contracting_process.md and provides the content for https://standard.open-contracting.org/latest/es/getting_started/contracting_process/.