-
Everybody has a working Pootle setup, right?
-
Uncomment plugin line in
requirements/_pootle_fs.txt
-
- Choose
git
backend - Use
git@github.com:translate/pootle_fs_demo.git
URL - Specify
/<language_code>/<dir_path>/<filename>.<ext>
mapping - Add mapping for
es_ES
toes
- Choose
-
The demo itself:
-
fetch
thensync
to ensure we pulled the remote repo translations to Pootle -
Translate something and
sync
(translations are auto-staged) -
Translate something for es then
sync
and check in VCS changes go to es_ES -
Translate something else and alter same string in repo, then
state
to see conflict-
Explain the conflict solving possibilities:
- Pootle overrides
- Filesystem overrides
- Filesystem prevails and Pootle becomes suggestion (default)
- Pootle prevails and filesystem becomes suggestion
-
Run
merge
thensync
(Filesystem prevails and Pootle becomes suggestion)
-
-
Add new file in repo,
fetch
thensync
-
Remove file in repo,
rm
thensync
-
How to figure out what to do:
- Use
state
to know what is going on (or if you are in doubt)
- Use
-
Changes in
templates
are not automatically synced to the project languages, so needs to be done outside Pootle as before Pootle FS.
-
-
Now everybody pairs and tries to replicate. Ask for help if needed.