7ebc5bdba3
- Moved the web *.po files to /i18n to be consistent
with the addons convention. Using /po was considered
for a while because it played better with LP's auto-
detection of PO Templates, but that is not necessary
anymore, we now have full control on LP templates.
- In order to support addons that contain translations
for both the web addon and the regular addon part,
both kinds of translations are now merged in a single
addon/i18n/addon.pot file. Terms that are used by
the web part are now marked with a PO annotation:
#. openerp-web
so the web client can recognize them and only load
the relevant translations in the browser memory.
This is important because a complete PO file can
be rather large, e.g. account/i18n/de.po = 400KB.
- The web translation export scripts were updated to
behave properly for addons that have a non-web
part, and will merge the web translation in the
original POT file, annotating the web translations
as needed. These scripts are Unix-only and meant
to be used by OpenERP packagers when needed.
- The GetText spec says that PO auto-comments indicating
the source location have this form:
#: /path/to/file:lineno
However OpenERP's POT export system defaults to a modified
version of this format with an extra 'type' field:
#: type:/path/to/file:lineno
The babel extractors we use have the GetText format
hardcoded so a small patch is needed on the server
to make it more lenient and accept the standard
source annotation, defaulting to 'code' type.
This does not matter for openerp-web, but makes sure
the server will not fail to load the new PO files
that contain openerp-web translations with standard
annotations.
The patch for making the server more lenient was
checked in trunk at revision 4002
rev-id odo@openerp.com-20120202143210-05p1w24t6u77cyv8
- The existing translation sync and export wizards for
regular addons have not been updated to consider
web addons, so for the time being we will have
to export regular addons terms first, and run the
web export script (gen_translations.sh) on the
addons directory afterwards. This could be improved
later.
As soon as this change is merged we will have to
perform a full update of addons translation
templates in order to include the web terms as well.
bzr revid: odo@openerp.com-20120202145603-ffo0il0qnfp3r6gt
|
||
|---|---|---|
| addons | ||
| bin | ||
| debian | ||
| doc | ||
| history | ||
| install | ||
| openerp | ||
| win32 | ||
| .bzrignore | ||
| LICENSE | ||
| LICENSE.web | ||
| MANIFEST.in | ||
| Makefile | ||
| README | ||
| README.web | ||
| babel.cfg | ||
| gen_translations.sh | ||
| gunicorn.conf.py | ||
| logging.json | ||
| npybabel.py | ||
| openerp-server | ||
| openerp-web | ||
| openerp-web.cfg | ||
| setup.cfg | ||
| setup.nsi | ||
| setup.py | ||
| setup_rpm.sh | ||
README
pydot - Python interface to Graphviz's Dot language Ero Carrera (c) 2004-2007 ero@dkbza.org This code is distributed under the MIT license. Requirements: ------------- pyparsing: pydot requires the pyparsing module in order to be able to load DOT files. GraphViz: is needed in order to render the graphs into any of the plethora of output formats supported. Installation: ------------- Should suffice with doing: python setup.py install Needless to say, no installation is needed just to use the module. A mere: import pydot should do it, provided that the directory containing the modules is on Python module search path.