lp://staging/~josepato-o/openobject-server/openobject-server-timezone

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

4010. By Jose Patricio Villarreal on 2012-11-16

it takes in consideration the diff file of the branch lp:~clearcorp-drivers/openobject-server/6.1-ccorp and adds to the function get_server_timezone() the return of teh config[timezone]

4009. By Jose Patricio Villarreal on 2012-11-16

download

4008. By Olivier Dony (Odoo) on 2012-02-07

[IMP] ir.filters: correct misleading tooltip

Currently, filters without any assigned user
are only usable by the system, e.g. for
driving marketing campaign segments
(in the marketing_campaign module).

4007. By Stephane Wirtel (OpenERP) on 2012-02-07

[FIX] Insert the data files of Babel

4006. By Launchpad Translations on behalf of openerp on 2012-02-05

Launchpad automatic translations update.

4005. By Launchpad Translations on behalf of openerp on 2012-02-04

Launchpad automatic translations update.

4004. By Launchpad Translations on behalf of openerp on 2012-02-03

Launchpad automatic translations update.

4003. By Xavier (Open ERP) on 2012-02-02

[FIX] in load_information_from_description_file, f can be a StringIO (in case of zipped module) and StringIO are not contextmanagers.

So rollback the context management thingie

4002. By Olivier Dony (Odoo) on 2012-02-02

[IMP] tools.translate: be more lenient and accept standart gettext source annotations

 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 for openerp-web's translations
  have the GetText format hardcoded, so it's a good idea
  to be more lenient and allow the standards annotations too.
  We can use a default 'code' type for such cases.

  For openerp-web translations the type does not matter,
  as the translations will be directly loaded by the
  web engine from the PO files and served in Javascript
 to the browser, with no typing needed.

  This patch simply avoids failing to parse updated PO files
  that will contain standard GetText annotations for the
  openerp-web related terms.

4001. By Xavier (Open ERP) on 2012-01-31

[ADD] values restriction pattern for notebook/@tabpos