[IMP] backport of rev odo@openerp.com-20120202143210-05p1w24t6u77cyv8 of trunk: tools.translate: be more lenient and accept standart gettext source annotations
[IMP] backport of rev d670d44c3ca8bd4cd53a3b09f8bf8fc35e4843cc@openerp.com-20120202143210-05p1w24t6u77cyv8 of trunk: tools.translate: be more lenient and accept standart gettext source annotations

Original commit information:
------------------------------------------------------------
revno: 4002
revision-id: d670d44c3ca8bd4cd53a3b09f8bf8fc35e4843cc@openerp.com-20120202143210-05p1w24t6u77cyv8
parent: 0f311f41b2be8e2b5de98776566d712cdc154ca4@openerp.com-20120131154023-lbxqpdirjk9df694
committer: Olivier Dony <d670d44c3ca8bd4cd53a3b09f8bf8fc35e4843cc@openerp.com>
branch nick: trunk
timestamp: Thu 2012-02-02 15:32:10 +0100
message:
  [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.

xrg/openerp-server,xrg/openerp-server