etc/translation.vars

PROJECT=I2P
VERSION=website
BABELCFG=etc/babel.cfg
POTDIR=pots
PROJDIR=i2p2www
TRANSDIR=$PROJDIR/translations

if [ -x env/bin/pybabel ]; then
    PYBABEL=env/bin/pybabel
elif [ $(which pybabel) ]; then
    PYBABEL=$(which pybabel)
else
    echo "ERROR: pybabel was not found. Please run setup_venv.sh" >&2
    exit 1
fi
Added script for updating existing translations 2013-01-18 11:01:32 +00:00			`PROJECT=I2P`
			`VERSION=website`
Moved setup, translation config files into subdir 2013-08-15 08:30:01 +00:00			`BABELCFG=etc/babel.cfg`
Split translation strings between multiple domains This breaks translation processing; multi-domain support needs to be added to Flask-Babel. The changes made here put the "important" strings that are used most often into the priority domain, and split the content from different sub-urls into separate domains. Multi-domain support will be implemented such that translations for a specific request are pulled both from the domain which corresponds to the request url and the priority domain. This does mean that there may be duplication of translation strings between domains, but that is unavoidable (and the translators prefer working with smaller resource files). 2013-07-13 11:01:05 +00:00			`POTDIR=pots`
Added script for updating existing translations 2013-01-18 11:01:32 +00:00			`PROJDIR=i2p2www`
			`TRANSDIR=$PROJDIR/translations`
prefer the venv pybabel but allow the system one to be used (if found) 2013-08-31 23:58:20 +00:00
			`if [ -x env/bin/pybabel ]; then`
			`PYBABEL=env/bin/pybabel`
			`elif [ $(which pybabel) ]; then`
			`PYBABEL=$(which pybabel)`
			`else`
			`echo "ERROR: pybabel was not found. Please run setup_venv.sh" >&2`
			`exit 1`
			`fi`