[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
# Translations template for PROJECT.
|
|
|
|
|
# Copyright (C) 2012 ORGANIZATION
|
|
|
|
|
# This file is distributed under the same license as the PROJECT project.
|
|
|
|
|
# FIRST AUTHOR <EMAIL@ADDRESS>, 2012.
|
|
|
|
|
#
|
|
|
|
|
#, fuzzy
|
|
|
|
|
msgid ""
|
|
|
|
|
msgstr ""
|
|
|
|
|
"Project-Id-Version: PROJECT VERSION\n"
|
|
|
|
|
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
|
2012-02-06 16:34:06 +00:00
|
|
|
|
"POT-Creation-Date: 2012-02-06 17:33+0100\n"
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
|
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|
|
|
|
"Language-Team: LANGUAGE <LL@li.org>\n"
|
|
|
|
|
"MIME-Version: 1.0\n"
|
|
|
|
|
"Content-Type: text/plain; charset=utf-8\n"
|
|
|
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
|
|
|
"Generated-By: Babel 0.9.6\n"
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:162
|
|
|
|
|
#: addons/web/static/src/js/chrome.js:188
|
|
|
|
|
#: addons/web/static/src/js/chrome.js:404
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:366
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:1104
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/xml/base.xml:1637
|
|
|
|
|
msgid "Ok"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:170
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Send OpenERP Enterprise Report"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:184
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Dont send"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:246
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Loading (%d)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/chrome.js:278
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Invalid database name"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:473
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Backed"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:474
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Database backed up successfully"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:517
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Restored"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:517
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Database restored successfully"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:694
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "About"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:773
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Preferences"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:776
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/js/search.js:237
|
|
|
|
|
#: addons/web/static/src/js/search.js:286
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:93
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:769
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:894
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:1099
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/xml/base.xml:738
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1432
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1442
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1451
|
|
|
|
|
msgid "Cancel"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:777
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Change password"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:778
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/js/view_editor.js:71
|
|
|
|
|
#: addons/web/static/src/js/views.js:957 addons/web/static/src/xml/base.xml:737
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1436
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1450
|
|
|
|
|
msgid "Save"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:797
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/xml/base.xml:226
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1671
|
|
|
|
|
msgid "Change Password"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/chrome.js:1084
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "OpenERP - Unsupported/Community Version"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/chrome.js:1116
|
|
|
|
|
msgid "Client Error"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_export.js:6
|
|
|
|
|
msgid "Export Data"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_export.js:19
|
|
|
|
|
#: addons/web/static/src/js/data_import.js:69
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:48
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:380
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:2908
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/js/views.js:958
|
|
|
|
|
msgid "Close"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_export.js:20
|
|
|
|
|
msgid "Export To File"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_export.js:125
|
|
|
|
|
msgid "Please enter save field list name"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_export.js:360
|
|
|
|
|
msgid "Please select fields to save export list..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_export.js:373
|
|
|
|
|
msgid "Please select fields to export..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_import.js:34
|
|
|
|
|
msgid "Import Data"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_import.js:70
|
|
|
|
|
msgid "Import File"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/data_import.js:105
|
|
|
|
|
msgid "External ID"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/formats.js:290
|
|
|
|
|
#: addons/web/static/src/js/view_page.js:240
|
|
|
|
|
msgid "Download"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/formats.js:295
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Download \"%s\""
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:235
|
|
|
|
|
msgid "Filter Entry"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:240
|
|
|
|
|
#: addons/web/static/src/js/search.js:289
|
|
|
|
|
msgid "OK"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:284
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1228
|
|
|
|
|
msgid "Add to Dashboard"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:413
|
|
|
|
|
msgid "Invalid Search"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:413
|
|
|
|
|
msgid "triggered from search view"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:505
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Incorrect value for field %(fieldname)s: [%(value)s] is %(message)s"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:837
|
|
|
|
|
msgid "not a valid integer"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:851
|
|
|
|
|
msgid "not a valid number"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:913
|
|
|
|
|
msgid "Yes"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:914
|
|
|
|
|
msgid "No"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1267
|
|
|
|
|
msgid "contains"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1268
|
|
|
|
|
msgid "doesn't contain"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1269
|
|
|
|
|
#: addons/web/static/src/js/search.js:1283
|
|
|
|
|
#: addons/web/static/src/js/search.js:1302
|
|
|
|
|
#: addons/web/static/src/js/search.js:1321
|
|
|
|
|
#: addons/web/static/src/js/search.js:1342
|
|
|
|
|
msgid "is equal to"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1270
|
|
|
|
|
#: addons/web/static/src/js/search.js:1284
|
|
|
|
|
#: addons/web/static/src/js/search.js:1303
|
|
|
|
|
#: addons/web/static/src/js/search.js:1322
|
|
|
|
|
#: addons/web/static/src/js/search.js:1343
|
|
|
|
|
msgid "is not equal to"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1271
|
|
|
|
|
#: addons/web/static/src/js/search.js:1285
|
|
|
|
|
#: addons/web/static/src/js/search.js:1304
|
|
|
|
|
#: addons/web/static/src/js/search.js:1323
|
|
|
|
|
#: addons/web/static/src/js/search.js:1344
|
|
|
|
|
msgid "greater than"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1272
|
|
|
|
|
#: addons/web/static/src/js/search.js:1286
|
|
|
|
|
#: addons/web/static/src/js/search.js:1305
|
|
|
|
|
#: addons/web/static/src/js/search.js:1324
|
|
|
|
|
#: addons/web/static/src/js/search.js:1345
|
|
|
|
|
msgid "less than"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1273
|
|
|
|
|
#: addons/web/static/src/js/search.js:1287
|
|
|
|
|
#: addons/web/static/src/js/search.js:1306
|
|
|
|
|
#: addons/web/static/src/js/search.js:1325
|
|
|
|
|
#: addons/web/static/src/js/search.js:1346
|
|
|
|
|
msgid "greater or equal than"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1274
|
|
|
|
|
#: addons/web/static/src/js/search.js:1288
|
|
|
|
|
#: addons/web/static/src/js/search.js:1307
|
|
|
|
|
#: addons/web/static/src/js/search.js:1326
|
|
|
|
|
#: addons/web/static/src/js/search.js:1347
|
|
|
|
|
msgid "less or equal than"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1337
|
|
|
|
|
#: addons/web/static/src/js/search.js:1360
|
|
|
|
|
msgid "is"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1361
|
|
|
|
|
msgid "is not"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1373
|
|
|
|
|
msgid "is true"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/search.js:1374
|
|
|
|
|
msgid "is false"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:20
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Manage Views (%s)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:45
|
|
|
|
|
#: addons/web/static/src/js/view_list.js:17
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:100
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:327
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:756
|
|
|
|
|
msgid "Create"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:46
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:483
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:755
|
|
|
|
|
msgid "Edit"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:47
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1589
|
|
|
|
|
msgid "Remove"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:69
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Create a view (%s)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:165
|
|
|
|
|
msgid "Do you really want to remove this view?"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:361
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "View Editor %d - %s"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:364
|
|
|
|
|
msgid "Preview"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:435
|
|
|
|
|
msgid "Do you really want to remove this node?"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:748
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:871
|
|
|
|
|
msgid "Properties"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:751
|
|
|
|
|
#: addons/web/static/src/js/view_editor.js:874
|
|
|
|
|
msgid "Update"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:16
|
|
|
|
|
msgid "Form"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:416
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Warning, the record has been modified, your changes will be discarded."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:625
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Attachments"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:663
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Do you really want to delete the attachment %s?"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:693
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Unknown operator %s in domain %s"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:701
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Unknown field %s in domain %s"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:739
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Unsupported operator %s in domain %s"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:1096
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Confirm"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:1785
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:2442
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:2605
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Open: "
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:1913
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "<em> Search More...</em>"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:1926
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#, python-format
|
|
|
|
|
msgid "<em> Create \"<strong>%s</strong>\"</em>"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:1932
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "<em> Create and Edit...</em>"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:1965
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/js/views.js:685
|
|
|
|
|
msgid "Search: "
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:1965
|
|
|
|
|
#: addons/web/static/src/js/view_form.js:2414
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Create: "
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:2525
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#: addons/web/static/src/xml/base.xml:750
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:772
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1588
|
|
|
|
|
msgid "Add"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_form.js:2585
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Add: "
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_list.js:8
|
|
|
|
|
msgid "List"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_list.js:269
|
|
|
|
|
msgid "Unlimited"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_list.js:305
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "[%(first_record)d to %(last_record)d] of %(records_count)d"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_list.js:524
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Do you really want to remove these records?"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_list.js:1230
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
msgid "Undefined"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
2012-02-06 16:34:06 +00:00
|
|
|
|
#: addons/web/static/src/js/view_list.js:1327
|
[IMP] refactored translation system to merge web translations with addons translations
- 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
2012-02-02 14:56:03 +00:00
|
|
|
|
#, python-format
|
|
|
|
|
msgid "%(page)d/%(page_count)d"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_page.js:8
|
|
|
|
|
msgid "Page"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_page.js:52
|
|
|
|
|
msgid "Do you really want to delete this record?"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/view_tree.js:11
|
|
|
|
|
msgid "Tree"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:565 addons/web/static/src/xml/base.xml:480
|
|
|
|
|
msgid "Fields View Get"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:573
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "View Log (%s)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:600
|
|
|
|
|
#, python-format
|
|
|
|
|
msgid "Model %s fields"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:612 addons/web/static/src/xml/base.xml:487
|
|
|
|
|
msgid "Customize Object"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:620 addons/web/static/src/xml/base.xml:482
|
|
|
|
|
msgid "Manage Views"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:621
|
|
|
|
|
msgid "Could not find current view declaration"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:808
|
|
|
|
|
msgid "Customize"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:810
|
|
|
|
|
msgid "Translate"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:812
|
|
|
|
|
msgid "Technical translation"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:816
|
|
|
|
|
msgid "Other Options"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:819
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1678
|
|
|
|
|
msgid "Import"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:822
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1548
|
|
|
|
|
msgid "Export"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:825
|
|
|
|
|
msgid "View Log"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:834
|
|
|
|
|
msgid "Reports"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:834
|
|
|
|
|
msgid "Actions"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:834
|
|
|
|
|
msgid "Links"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:914
|
|
|
|
|
msgid "You must choose at least one record."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:915
|
|
|
|
|
msgid "Warning"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/js/views.js:952
|
|
|
|
|
msgid "Translations"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:9 addons/web/static/src/xml/base.xml:15
|
|
|
|
|
msgid "#{title}"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:10 addons/web/static/src/xml/base.xml:16
|
|
|
|
|
msgid "#{text}"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:44 addons/web/static/src/xml/base.xml:315
|
|
|
|
|
msgid "Powered by"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:44 addons/web/static/src/xml/base.xml:315
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1755
|
|
|
|
|
msgid "OpenERP"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:52
|
|
|
|
|
msgid "Loading..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:61
|
|
|
|
|
msgid "CREATE DATABASE"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:68 addons/web/static/src/xml/base.xml:211
|
|
|
|
|
msgid "Master password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:72 addons/web/static/src/xml/base.xml:191
|
|
|
|
|
msgid "New database name:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:77
|
|
|
|
|
msgid "Load Demonstration data:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:81
|
|
|
|
|
msgid "Default language:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:91
|
|
|
|
|
msgid "Admin password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:95
|
|
|
|
|
msgid "Confirm password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:109
|
|
|
|
|
msgid "DROP DATABASE"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:116
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:150
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:301
|
|
|
|
|
msgid "Database:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:128
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:162
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:187
|
|
|
|
|
msgid "Master Password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:132
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:328
|
|
|
|
|
msgid "Drop"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:143
|
|
|
|
|
msgid "BACKUP DATABASE"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:166
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:329
|
|
|
|
|
msgid "Backup"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:175
|
|
|
|
|
msgid "RESTORE DATABASE"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:182
|
|
|
|
|
msgid "File:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:195
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:330
|
|
|
|
|
msgid "Restore"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:204
|
|
|
|
|
msgid "CHANGE MASTER PASSWORD"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:216
|
|
|
|
|
msgid "New master password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:221
|
|
|
|
|
msgid "Confirm new master password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:251
|
|
|
|
|
msgid ""
|
|
|
|
|
"Your version of OpenERP is unsupported. Support & maintenance services "
|
|
|
|
|
"are available here:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:251
|
|
|
|
|
msgid "OpenERP Entreprise"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:256
|
|
|
|
|
msgid "OpenERP Enterprise Contract."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:257
|
|
|
|
|
msgid "Your report will be sent to the OpenERP Enterprise team."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:259
|
|
|
|
|
msgid "Summary:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:263
|
|
|
|
|
msgid "Description:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:267
|
|
|
|
|
msgid "What you did:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:297
|
|
|
|
|
msgid "Invalid username or password"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:306
|
|
|
|
|
msgid "Username"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:308
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:331
|
|
|
|
|
msgid "Password"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:310
|
|
|
|
|
msgid "Log in"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:314
|
|
|
|
|
msgid "Manage Databases"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:332
|
|
|
|
|
msgid "Back to Login"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:363
|
|
|
|
|
msgid "LOGOUT"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:388
|
|
|
|
|
msgid "«"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:389
|
|
|
|
|
msgid "»"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:393
|
|
|
|
|
msgid "oe_secondary_menu_item"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:408
|
|
|
|
|
msgid "oe_secondary_submenu_item"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:454
|
|
|
|
|
msgid "Hide this tip"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:455
|
|
|
|
|
msgid "Disable all tips"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:471
|
|
|
|
|
msgid "More…"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:477
|
|
|
|
|
msgid "Debug View#"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:478
|
|
|
|
|
msgid "View Log (perm_read)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:479
|
|
|
|
|
msgid "View Fields"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:483
|
|
|
|
|
msgid "View"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:484
|
|
|
|
|
msgid "Edit SearchView"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:485
|
|
|
|
|
msgid "Edit Action"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:486
|
|
|
|
|
msgid "Edit Workflow"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:492
|
|
|
|
|
msgid "ID:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:495
|
|
|
|
|
msgid "XML ID:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:498
|
|
|
|
|
msgid "Creation User:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:501
|
|
|
|
|
msgid "Creation Date:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:504
|
|
|
|
|
msgid "Latest Modification by:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:507
|
|
|
|
|
msgid "Latest Modification Date:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:543
|
|
|
|
|
msgid "Field"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:632
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:758
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1650
|
|
|
|
|
msgid "Delete"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:757
|
|
|
|
|
msgid "Duplicate"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:795
|
|
|
|
|
msgid "Unhandled widget"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:844
|
|
|
|
|
msgid "Notebook Page \""
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:849
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:908
|
|
|
|
|
msgid "Modifiers:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:875
|
|
|
|
|
msgid "(nolabel)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:880
|
|
|
|
|
msgid "Field:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:884
|
|
|
|
|
msgid "Object:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:888
|
|
|
|
|
msgid "Type:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:892
|
|
|
|
|
msgid "Widget:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:896
|
|
|
|
|
msgid "Size:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:900
|
|
|
|
|
msgid "Context:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:904
|
|
|
|
|
msgid "Domain:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:912
|
|
|
|
|
msgid "On change:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:916
|
|
|
|
|
msgid "Relation:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:920
|
|
|
|
|
msgid "Selection:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1030
|
|
|
|
|
msgid "Open..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1031
|
|
|
|
|
msgid "Create..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1032
|
|
|
|
|
msgid "Search..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1035
|
|
|
|
|
msgid "..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1112
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1163
|
|
|
|
|
msgid "Uploading ..."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1140
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1431
|
|
|
|
|
msgid "Select"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1149
|
|
|
|
|
msgid "Save As"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1155
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1212
|
|
|
|
|
msgid "Clear"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1178
|
|
|
|
|
msgid "Button"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1181
|
|
|
|
|
msgid "(no string)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1188
|
|
|
|
|
msgid "Special:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1193
|
|
|
|
|
msgid "Button Type:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1197
|
|
|
|
|
msgid "Method:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1201
|
|
|
|
|
msgid "Action ID:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1211
|
|
|
|
|
msgid "Search"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1219
|
|
|
|
|
msgid "Filters"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1226
|
|
|
|
|
msgid "Add Advanced Filter"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1227
|
|
|
|
|
msgid "Save Filter"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1229
|
|
|
|
|
msgid "Manage Filters"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1234
|
|
|
|
|
msgid "Filter Name:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1236
|
|
|
|
|
msgid "(Any existing filter with the same name will be replaced)"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1241
|
|
|
|
|
msgid "Select Dashboard to add this filter to:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1245
|
|
|
|
|
msgid "Title of new Dashboard item:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1352
|
|
|
|
|
msgid "Advanced Filters"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1362
|
|
|
|
|
msgid "Any of the following conditions must match"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1363
|
|
|
|
|
msgid "All the following conditions must match"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1364
|
|
|
|
|
msgid "None of the following conditions must match"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1371
|
|
|
|
|
msgid "Add condition"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1372
|
|
|
|
|
msgid "and"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1439
|
|
|
|
|
msgid "Save & New"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1440
|
|
|
|
|
msgid "Save & Close"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1457
|
|
|
|
|
msgid ""
|
|
|
|
|
"adds back padding to row being rendered after edition, if necessary\n"
|
|
|
|
|
" (if not deletable add back padding), otherwise the row being "
|
|
|
|
|
"added is\n"
|
|
|
|
|
" missing columns"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1553
|
|
|
|
|
msgid ""
|
|
|
|
|
"This wizard will export all data that matches the current search criteria"
|
|
|
|
|
" to a CSV file.\n"
|
|
|
|
|
" You can export all data or only the fields that can be "
|
|
|
|
|
"reimported after modification."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1560
|
|
|
|
|
msgid "Export Type:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1562
|
|
|
|
|
msgid "Import Compatible Export"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1563
|
|
|
|
|
msgid "Export all Data"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1566
|
|
|
|
|
msgid "Export Formats"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1572
|
|
|
|
|
msgid "Available fields"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1574
|
|
|
|
|
msgid "Fields to export"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1576
|
|
|
|
|
msgid "Save fields list"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1587
|
|
|
|
|
msgid "TODO: replace ids by 'oe_*' classes"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1590
|
|
|
|
|
msgid "Remove All"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1602
|
|
|
|
|
msgid "Name"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1613
|
|
|
|
|
msgid " "
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1635
|
|
|
|
|
msgid "Save as:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1642
|
|
|
|
|
msgid "Saved exports:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1656
|
|
|
|
|
msgid "Old Password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1661
|
|
|
|
|
msgid "New Password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1666
|
|
|
|
|
msgid "Confirm Password:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1684
|
|
|
|
|
msgid "1. Import a .CSV file"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1685
|
|
|
|
|
msgid ""
|
|
|
|
|
"Select a .CSV file to import. If you need a sample of file to import,\n"
|
|
|
|
|
" you should use the export tool with the \"Import Compatible\" "
|
|
|
|
|
"option."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1689
|
|
|
|
|
msgid "CSV File:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1692
|
|
|
|
|
msgid "2. Check your file format"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1695
|
|
|
|
|
msgid "Import Options"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1699
|
|
|
|
|
msgid "Does your file have titles?"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1705
|
|
|
|
|
msgid "Separator:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1707
|
|
|
|
|
msgid "Delimiter:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1711
|
|
|
|
|
msgid "Encoding:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1714
|
|
|
|
|
msgid "UTF-8"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1715
|
|
|
|
|
msgid "Latin 1"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1718
|
|
|
|
|
msgid "Lines to skip"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1745
|
|
|
|
|
msgid "The import failed due to:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1747
|
|
|
|
|
msgid "Here is a preview of the file we could not import:"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1754
|
|
|
|
|
msgid "Activate the developper mode"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1756
|
|
|
|
|
msgid "Version"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1757
|
|
|
|
|
msgid "Copyright © 2004-TODAY OpenERP SA. All Rights Reserved."
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1758
|
|
|
|
|
msgid "OpenERP is a trademark of the"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1759
|
|
|
|
|
msgid "OpenERP SA Company"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1761
|
|
|
|
|
msgid "Licenced under the terms of"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1762
|
|
|
|
|
msgid "GNU Affero General Public License"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1764
|
|
|
|
|
msgid "For more information visit"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
|
|
#. openerp-web
|
|
|
|
|
#: addons/web/static/src/xml/base.xml:1765
|
|
|
|
|
msgid "OpenERP.com"
|
|
|
|
|
msgstr ""
|
|
|
|
|
|