|
|
1. L10n person will git clone and build locally a Lektor website with `$ lektor build`. If you see errors, check if there are characters breaking the build. [These tips](https://tails.boum.org/contribute/l10n_tricks/) can help to fix some commons errors.
|
|
|
1. Then, go to `i18n` directory and get the `contents.pot` file.
|
|
|
1. Review the file and check if strings are good, i.e, respecting localization guideline.
|
|
|
1. Checkout the translations branch of the repository, instead of master
|
|
|
- `git checkout translations`
|
|
|
- `git pull`
|
... | ... | @@ -9,6 +6,8 @@ |
|
|
- `git checkout master -- content/`
|
|
|
1. Commit the content changes
|
|
|
1. Build the website a couple of times so the translation template gets updated
|
|
|
1. Review the changes to the translation file and check if strings are good, i.e, respecting localization guidelines:
|
|
|
- git diff i18n/contents.pot
|
|
|
1. Add the translation file: `git add -p i18n/contents.pot`
|
|
|
1. Commit the new file: `git commit -m 'update translation template'`
|
|
|
1. Transifex will pick up the changes on the next hours |
|
|
\ No newline at end of file |