1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
====================
Internationalization
====================
Kajiki provides supporting infrastructure for internationalizing and localizing
templates. This includes functionality for extracting localizable strings from
templates, as well as translation of localizable strings.
Basics
=======
To internationalize and translate templates, other templating solutions require
that you wrap all localizable strings in a `gettext()` function call
(usually aliased to `_()` for brevity). In this case, you would write your
templates similar to the following:
.. code-block:: xml
<p>${_('Hello, world!')}</p>
This approach, however, adds lots of noise to your templates. Kajiki does not
require that you wrap localizable strings since it automatically finds all
"translatable text" in XML templates (any text outside of an XML tag).
In order to actually use translation, you must replace the placeholder function
in `kajiki.i18n.gettext` with the actual gettext function. For instance, you
might place the following in your top-level script to enable the Python gettext
module::
from gettext import gettext
from kajiki import i18n
i18n.gettext = gettext
Extraction
=====================
Kajiki also provides support for extracting all localizable strings found in a
template. This functionality is integrated with the excellent message extraction
framework provided by the Babel_ project. Typically, you would notify Babel of
the location of your templates before running the extraction routine:
.. code-block:: none
# Python source
[python:**.py]
# Kajiki Templates
[kajiki:**/templates/**.html]
Please consult the Babel documentation for further details. If all goes well,
the extraction process should create a POT file containing the strings from your
Kajiki templates and your Python source files.
.. _Babel: http://babel.pocoo.org/
|
