path: root/import-translations
Commit message (Collapse)AuthorAgeFilesLines
* import-translations: add support for Onion Circuits translatations' Git repo ↵intrigeri2016-05-311-7/+23
| | | | | | | | | layout. For some reason, this one has $LANG/onioncircuits.pot instead of the usual $LANG.po. refs: #11160
* import-translations: add Onion Circuits.intrigeri2016-03-311-0/+3
* Avoid set -u issue when testing if variable is set or not.anonym2016-02-111-1/+1
| | | | | | | | | | | | | | Whenever there's a risk that we will reference a shell variable in a script run with `set -u` (including libraries that we sources from such scripts) we must reference the variable in a way so it gets a default value, i.e. `${VAR:-}` to give it the empty string as the default (which is what generally makes sense). In particular, it's quite clear that in all cases where we do something like `[ -n "${VAR}" ]` or `[ -z "${VAR}" ]`, where an expected value is the empty string, which could mean that the variable is not initialized, we should give such a default (as the empty string).
* Install tails-installer instead of liveusb-creator.intrigeri2015-11-111-2/+2
| | | | Refs: #8561
* Adjust import-translations' post-import step for Tails Installer, to match ↵intrigeri2015-10-021-1/+1
| | | | how its i18n system works nowadays.
* Stop taking pt-br translations from Git, apart from the web site.Tails developers2014-04-171-1/+1
* Import perl5lib translations from the correct branch.Tails developers2014-03-081-1/+1
* Translate tails-perl5lib in import-translations.Tails developers2014-03-071-0/+3
* Add support for tails-iuk to import-translations.Tails developers2013-12-281-0/+3
* Use readlink instead, looks better.WinterFairy2013-12-071-1/+1
* Added support to import-translations for custom apps.WinterFairy2013-12-061-11/+36
| | | | | | | Just run this script when cd'ed into e.g. the greeter repository or persistence-setup repository, and it will import the translations for these projects instead.
* Run `intltool-update --dist' in import-translations too.Tails developers2013-11-301-0/+6
| | | | | | | Else, many noisy and useless changes appear in PO files. If one commits right after this stage without running refresh-translations first, despite what the release process documentation says, this would make the Git history hard to understand.
* Reset --hard instead of merging, just in case TTP rewrite their history some ↵Tails developers2013-11-301-1/+1
| | | | day.
* Refactor import-translations.Tails developers2013-11-301-25/+23
| | | | | Don't use cd, define most parameters as variables on top of the file, make the whole thing generally more elegant.
* Also use "set -u" for more robustness.Tails developers2013-11-301-0/+1
* Don't run intltool-update after importing translations: we do it in ↵Tails developers2013-11-301-8/+1
| | | | refresh-translations.
* Add an import-translation script.WinterFairy2013-11-291-0/+48
This will make the importation of completed translations from Transifex automated. It does not import "fr" or "pt_BR", as they are translated in git instead. This script is based on a similar script from TorButton.