Flask-Babel is an extension to Flask that adds i18n and l10n support to any Flask application with the help of babel, pytz and its own copy of speaklater. It has built-in support for date formatting including timezones, as well as a very simple and friendly interface to gettext translations.
Install the extension from PyPi:
$ pip install Flask-Babel
Please note that Flask-Babel requires Jinja >=2.5. If you are using an older version you will have to upgrade or disable the Jinja support (see configuration).
Configuration#To get started all you need to do is to instantiate a Babel object after configuring the application:
from flask import Flask from flask_babel import Babel app = Flask(__name__) babel = Babel(app)
To disable jinja support, include configure_jinja=False in the Babel constructor call. The babel object itself can be used to configure the babel support further. Babel has the following configuration values that can be used to change some internal defaults:
BABEL_DEFAULT_LOCALE
The default locale to use if no locale selector is registered. This defaults to 'en'.
BABEL_DEFAULT_TIMEZONE
The timezone to use for user facing dates. This defaults to 'UTC' which also is the timezone your application must use internally.
BABEL_TRANSLATION_DIRECTORIES
A semi-colon (;) separated string of absolute and relative (to the root_path of the application object) paths to translation folders. Defaults to translations.
BABEL_DOMAIN
The message domain used by the application. Defaults to messages.
It can also be a semi-colon (;) separated string of different domains for each of the translation directories, eg:
BABEL_TRANSLATION_DIRECTORIES=/path/to/translations;/another/path/ BABEL_DOMAIN=messages;myapp
For more complex applications you might want to have multiple applications for different users which is where selector functions come in handy. The first time the babel extension needs the locale (locale code/ID) of the current user it will call a localeselector() function, and the first time the timezone is needed it will call a timezoneselector() function.
If any of these methods return None the extension will automatically fall back to what’s in the config. Furthermore for efficiency that function is called only once and the return value then cached. If you need to switch the language between a request, you can refresh() the cache.
Example selector functions:
from flask import g, request
def get_locale():
# if a user is logged in, use the locale from the user settings
user = getattr(g, 'user', None)
if user is not None:
return user.locale
# otherwise try to guess the language from the user accept
# header the browser transmits. We support de/fr/en in this
# example. The best match wins.
return request.accept_languages.best_match(['de', 'fr', 'en'])
def get_timezone():
user = getattr(g, 'user', None)
if user is not None:
return user.timezone
app = Flask(__name__)
babel = Babel(app, locale_selector=get_locale, timezone_selector=get_timezone)
The example above assumes that the current user is stored on the flask.g object.
Several commonly used formatters are added as jinja template filters after calling init_app(). For dates and times, these are:
<datetime>|datetimeformat -> format_datetime
<date>|dateformat -> format_date
<time>|timeformat -> format_time
<timedelta>|timedeltaformat -> format_timedelta
And for numbers, these are:
<number>|numberformat -> format_number
<number>|decimalformat -> format_decimal
<number>|currencyformat -> format_currency
<number>|percentformat -> format_percent
<number>|scientificformat -> format_scientific
To format dates you can use the format_datetime(), format_date(), format_time() and format_timedelta() functions. They all accept a datetime.datetime (or datetime.date, datetime.time and datetime.timedelta) object as first parameter and then optionally a format string. The application should use naive datetime objects internally that use UTC as timezone. On formatting it will automatically convert into the user’s timezone in case it differs from UTC.
To play with the date formatting from the console, you can use the test_request_context() method:
>>> app.test_request_context().push()
Here some examples:
>>> from flask_babel import format_datetime >>> from datetime import datetime >>> format_datetime(datetime(1987, 3, 5, 17, 12)) u'Mar 5, 1987 5:12:00 PM' >>> format_datetime(datetime(1987, 3, 5, 17, 12), 'full') u'Thursday, March 5, 1987 5:12:00 PM World (GMT) Time' >>> format_datetime(datetime(1987, 3, 5, 17, 12), 'short') u'3/5/87 5:12 PM' >>> format_datetime(datetime(1987, 3, 5, 17, 12), 'dd mm yyy') u'05 12 1987' >>> format_datetime(datetime(1987, 3, 5, 17, 12), 'dd mm yyyy') u'05 12 1987'
And again with a different language:
>>> app.config['BABEL_DEFAULT_LOCALE'] = 'de' >>> from flask_babel import refresh; refresh() >>> format_datetime(datetime(1987, 3, 5, 17, 12), 'EEEE, d. MMMM yyyy H:mm') u'Donnerstag, 5. M\xe4rz 1987 17:12'
For more format examples head over to the babel documentation.
Formatting Numbers#To format numbers you can use the format_number(), format_decimal(), format_currency(), format_percent() and format_scientific() functions.
To play with the date formatting from the console, you can use the test_request_context() method:
>>> app.test_request_context().push()
Here are some examples:
>>> from flask_babel import format_number >>> format_number(1099) '1,099'
>>> from flask_babel import format_decimal >>> format_decimal(1.2346) u'1.235'
>>> from flask_babel import format_currency >>> format_currency(1099.98, 'USD') '$1,099.98'
>>> from flask_babel import format_percent >>> format_percent(0.34) '34%'
>>> from flask_babel import format_scientific >>> format_scientific(10000) '1E4'
And again with a different language:
>>> app.config['BABEL_DEFAULT_LOCALE'] = 'de' >>> from flask_babel import refresh; refresh()
>>> format_number(1099) '1.099'
>>> format_decimal(1.2346) '1,235'
>>> format_currency(1099.98, 'USD') '1.099,98\xa0$'
>>> format_percent(0.34) '34\xa0%'
>>> format_scientific(10000) '1E4'
For more format examples head over to the babel documentation.
Using Translations#The other big part next to date formatting are translations. For that, Flask uses gettext together with Babel. The idea of gettext is that you can mark certain strings as translatable and a tool will pick all those up, collect them in a separate file for you to translate. At runtime the original strings (which should be English) will be replaced by the language you selected.
There are two functions responsible for translating: gettext() and ngettext(). The first to translate singular strings and the second to translate strings that might become plural. Here some examples:
from flask_babel import gettext, ngettext gettext(u'A simple string') gettext(u'Value: %(value)s', value=42) ngettext(u'%(num)s Apple', u'%(num)s Apples', number_of_apples)
Additionally if you want to use constant strings somewhere in your application and define them outside of a request, you can use a lazy strings. Lazy strings will not be evaluated until they are actually used. To use such a lazy string, use the lazy_gettext() function:
from flask_babel import lazy_gettext
class MyForm(formlibrary.FormBase):
success_message = lazy_gettext(u'The form was successfully saved.')
So how does Flask-Babel find the translations? Well first you have to create some. Here is how you do it:
Translating Applications#First you need to mark all the strings you want to translate in your application with gettext() or ngettext(). After that, it’s time to create a .pot file. A .pot file contains all the strings and is the template for a .po file which contains the translated strings. Babel can do all that for you.
First of all you have to create a mapping file. For typical Flask applications, this is what you want in there:
[python: **.py] [jinja2: **/templates/**.html]
Save it as babel.cfg or something similar next to your application. Then it’s time to run the pybabel command that comes with Babel to extract your strings:
$ pybabel extract -F babel.cfg -o messages.pot .
If you are using the lazy_gettext() function you should tell pybabel that it should also look for such function calls:
$ pybabel extract -F babel.cfg -k lazy_gettext -o messages.pot .
This will use the mapping from the babel.cfg file and store the generated template in messages.pot. Now we can create the first translation. For example to translate to German use this command:
$ pybabel init -i messages.pot -d translations -l de
-d translations tells pybabel to store the translations in a directory called “translations”. This is the default folder where Flask-Babel will look for translations unless you changed BABEL_TRANSLATION_DIRECTORIES and should be at the root of your application.
Now edit the translations/de/LC_MESSAGES/messages.po file as needed. Check out some gettext tutorials if you feel lost.
To compile the translations for use, pybabel helps again:
$ pybabel compile -d translations
What if the strings change? Create a new messages.pot like above and then let pybabel merge the changes:
$ pybabel update -i messages.pot -d translations
Afterwards some strings might be marked as fuzzy (where it tried to figure out if a translation matched a changed key). If you have fuzzy entries, make sure to check them by hand and remove the fuzzy flag before compiling.
Reloading Translations#The compiled translations will only be loaded initially. This means you have to restart the server whenever you compile translations and want to see those changes. To automatically reload translations you can tell the reloader to watch the compiled .mo files:
$ flask run --extra-files app/translations/en_GB/LC_MESSAGES/messages.mo # or $ export FLASK_RUN_EXTRA_FILES=app/translations/en_GB/LC_MESSAGES/messages.mo $ flask run
See reloader for more details.
Troubleshooting#On Snow Leopard pybabel will most likely fail with an exception. If this happens, check if this command outputs UTF-8:
This is a OS X bug unfortunately. To fix it, put the following lines into your ~/.profile file:
export LC_CTYPE=en_US.utf-8
Then restart your terminal.
API#This part of the documentation documents each and every public class or function from Flask-Babel.
Configuration#Central controller class that can be used to configure how Flask-Babel behaves. Each application that wants to use Flask-Babel has to create, or run init_app() on, an instance of this class after the configuration was initialized.
The default locale from the configuration as an instance of a babel.Locale object.
The default timezone from the configuration as an instance of a pytz.timezone object.
The message domain for the translations as a string.
The message domain for the translations.
Initializes the Babel instance for use with this specific application.
app – The application to configure
default_locale – The default locale to use for this application
default_domain – The default domain to use for this application
default_translation_directories – The default translation directories to use for this application
default_timezone – The default timezone to use for this application
locale_selector – The function to use to select the locale for a request
timezone_selector – The function to use to select the timezone for a request
Returns a list of all the locales translations exist for. The list returned will be filled with actual locale objects and not just strings.
Note
The default locale will always be returned, even if no translation files exist for it.
New in version 0.6.
Returns the correct gettext translations that should be used for this request. This will never fail and return a dummy translation object if used outside the request or if a translation cannot be found.
Returns the locale that should be used for this request as babel.Locale object. This returns None if used outside a request.
Returns the timezone that should be used for this request as a pytz.timezone object. This returns None if used outside a request.
Convert a datetime object to the user’s timezone. This automatically happens on all date formatting unless rebasing is disabled. If you need to convert a datetime.datetime object at any time to the user’s timezone (as returned by get_timezone()) this function can be used.
Convert a datetime object to UTC and drop tzinfo. This is the opposite operation to to_user_timezone().
Return a date formatted according to the given pattern. If no datetime object is passed, the current time is assumed. By default, rebasing happens, which causes the object to be converted to the user’s timezone (as returned by to_user_timezone()). This function formats both date and time.
The format parameter can either be 'short', 'medium', 'long' or 'full' (in which case the language’s default for that setting is used, or the default from the Babel.date_formats mapping is used) or a format string as documented by Babel.
This function is also available in the template context as filter named datetimeformat.
Return a date formatted according to the given pattern. If no datetime or date object is passed, the current time is assumed. By default, rebasing happens, which causes the object to be converted to the users’s timezone (as returned by to_user_timezone()). This function only formats the date part of a datetime object.
The format parameter can either be 'short', 'medium', 'long' or 'full' (in which case the language’s default for that setting is used, or the default from the Babel.date_formats mapping is used) or a format string as documented by Babel.
This function is also available in the template context as filter named dateformat.
Return a time formatted according to the given pattern. If no datetime object is passed, the current time is assumed. By default, rebasing happens, which causes the object to be converted to the user’s timezone (as returned by to_user_timezone()). This function formats both date and time.
The format parameter can either be 'short', 'medium', 'long' or 'full' (in which case the language’s default for that setting is used, or the default from the Babel.date_formats mapping is used) or a format string as documented by Babel.
This function is also available in the template context as filter named timeformat.
Format the elapsed time from the given date to now or the given timedelta.
This function is also available in the template context as filter named timedeltaformat.
Return the given number formatted for the locale in request
number – the number to format
the formatted number
unicode
Return the given decimal number formatted for the locale in the request.
number – the number to format
format – the format to use
the formatted number
unicode
Return the given number formatted for the locale in the request.
number – the number to format
currency – the currency code
format – the format to use
currency_digits – use the currency’s number of decimal digits [default: True]
format_type – the currency format type to use [default: standard]
the formatted number
unicode
Return formatted percent value for the locale in the request.
number – the number to format
format – the format to use
the formatted percent number
unicode
Return value formatted in scientific notation for the locale in request
number – the number to format
format – the format to use
the formatted percent number
unicode
Refreshes the cached timezones and locale information. This can be used to switch a translation between a request and if you want the changes to take place immediately, not just with the next request:
user.timezone = request.form['timezone']
user.locale = request.form['locale']
refresh()
flash(gettext('Language was changed'))
Without that refresh, the flash() function would probably return English text and a now German page.
Temporarily overrides the currently selected locale.
Sometimes it is useful to switch the current locale to different one, do some tasks and then revert back to the original one. For example, if the user uses German on the website, but you want to email them in English, you can use this function as a context manager:
with force_locale('en_US'):
send_email(gettext('Hello!'), ...)
locale – The locale to temporary switch to (ex: ‘en_US’).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4