Skip to main content
Paths tell GitLocalize where to find translatable files and where to write the translations it generates. Every repository has at least one source path and one target path. Target paths accept placeholders: Target paths serve double duty: GitLocalize writes translations there, and also scans the same locations when importing translations that already exist in the repository.

​
Default configuration

Translatable files are taken from the repository root, including subfolders. Translations are written per language — Korean under /ko/..., German under /de/....

​
Directory-based paths

Sources come from /src/site/content/en. Korean translations are read from and written to /src/site/content/translations-ko, German to /src/site/content/translations-de.

​
File-based paths

A path can name a single file rather than a directory:

​
Mixed-type paths

A directory source can pair with a filename-based target, keeping translations beside their sources:
The German translation of a4a_spec.md is written to the same guides-and-tutorials directory as a4a_spec@de.md.

​
Custom language codes

By default %lang% resolves to GitLocalize’s own code for each language. Each language can override it — pt-BR instead of pt, or jp instead of ja — so output lands where the repository expects it. Codes are set when the repository is connected, or later under Manage Languages in the Languages view. Both are available to Admins and the Owner.
Setting custom language codes in Manage Languages
Changing a language code changes where translations are written. Files already written to the old path are not moved.