odoo
/
odoo
2
0
Fork 0
Code Pull Requests Releases Activity
odoo/addons/web/i18n/web.pot

2037 lines
40 KiB
Plaintext
Raw Normal View History

[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
# Translation of OpenERP Server.
# This file contains the translation of the following modules:
# * web
[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 ""
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
"Project-Id-Version: OpenERP Server 7.0alpha\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2012-11-24 01:23+0000\n"
"PO-Revision-Date: 2012-11-24 01:23+0000\n"
"Last-Translator: <>\n"
"Language-Team: \n"
[I18N] Update translation templates (web,kanban) for the minor recent term changes bzr revid: odo@openerp.com-20120209180523-b41ubljpsdz17jrm
2012-02-09 18:05:23 +00:00
"MIME-Version: 1.0\n"
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: \n"
"Plural-Forms: \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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:249
#, python-format
msgid "Restore Database"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:134
#, python-format
msgid "Default language:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:326
#, python-format
msgid "Loading"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:590
#, python-format
msgid "%d minutes ago"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:1069
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "You must choose at least one record."
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:618
#, python-format
msgid "Still loading...<br />Please be patient."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:619
#, python-format
msgid "Don't leave yet,<br />it's still loading..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1834
#, python-format
msgid "%(field)s %(operator)s \"%(value)s\""
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1886
#: code:addons/web/static/src/js/search.js:1920
#: code:addons/web/static/src/js/search.js:1944
#, python-format
msgid "less or equal than"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:596
#, python-format
msgid "%d months ago"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:774
#, python-format
msgid "Invalid Search"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:597
#, python-format
msgid "about a year ago"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:118
#: code:addons/web/static/src/xml/base.xml:168
#: code:addons/web/static/src/xml/base.xml:283
#, python-format
msgid "Master password:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1270
#, python-format
msgid "Button"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:275
#, python-format
msgid "Change Master Password"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:800
#, python-format
msgid "View Log (%s)"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1656
#, python-format
msgid "Remove All"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:593
#, python-format
msgid "a day ago"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1655
#, python-format
msgid "Remove"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1394
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Search %(field)s at: %(value)s"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1738
#, python-format
msgid "Does your file have titles?"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1289
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Method:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:1417
#, python-format
msgid "%(page)d/%(page_count)d"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:549
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Restored"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:592
#, python-format
msgid "%d hours ago"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4175
#: code:addons/web/static/src/js/view_form.js:4306
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Add: "
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:2821
#, python-format
msgid "Search More..."
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1754
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Latin 1"
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:528
#, python-format
msgid "XML ID:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:260
#: code:addons/web/static/src/js/chrome.js:269
#: code:addons/web/static/src/js/chrome.js:449
#: code:addons/web/static/src/js/chrome.js:788
#: code:addons/web/static/src/js/view_form.js:576
#: code:addons/web/static/src/js/view_form.js:1939
#: code:addons/web/static/src/xml/base.xml:1701
#, python-format
msgid "Ok"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:1127
#, python-format
msgid "Uploading..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:126
#, python-format
msgid "Load Demonstration data:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:516
#, python-format
msgid "View"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:2880
#, python-format
msgid "Search: "
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4857
#, python-format
msgid "Save As..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4982
#, python-format
msgid "Could not display the selected image."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:217
#, python-format
msgid "Backup Database"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:906
#, python-format
msgid "Size:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1172
#: code:addons/web/static/src/xml/base.xml:1174
#, python-format
msgid "Save As"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:620
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "You may not believe it,<br />but the application is actually loading..."
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:509
#, python-format
msgid "Database backed up successfully"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1757
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "For use if CSV files have titles on multiple lines, skips more than a single line during import"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:514
#, python-format
msgid "Technical translation"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1552
#, python-format
msgid "Save current filter"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1786
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Here is a preview of the file we could not import:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1746
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Delimiter:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:589
#, python-format
msgid "about a minute ago"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1723
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "1. Import a .CSV file"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:257
#, python-format
msgid "File:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1413
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "-- Actions --"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:251
#: code:addons/web/static/src/xml/base.xml:311
#, python-format
msgid "Restore"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:197
#: code:addons/web/static/src/xml/base.xml:162
#: code:addons/web/static/src/xml/base.xml:308
#, python-format
msgid "Duplicate"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/formats.js:180
#, python-format
msgid "(%d records)"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1293
#, python-format
msgid "not a valid number"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:922
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Change default:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:506
#, python-format
msgid "Toggle Form Layout Outline"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:683
#: code:addons/web/static/src/js/views.js:1069
#, python-format
msgid "Warning"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:517
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Edit SearchView"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:207
#: code:addons/web/static/src/xml/base.xml:239
#: code:addons/web/static/src/xml/base.xml:261
#, python-format
msgid "Master Password:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1975
#, python-format
msgid "is true"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1871
#: code:addons/web/static/src/js/search.js:1881
#: code:addons/web/static/src/js/search.js:1915
#: code:addons/web/static/src/js/search.js:1939
#, python-format
[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 "is equal to"
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:926
#, python-format
msgid "On change:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:3883
#, python-format
msgid "Add an item"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1568
#, python-format
msgid "Advanced Search"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1166
#: code:addons/web/static/src/xml/base.xml:1323
#, python-format
msgid "Select"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1872
#: code:addons/web/static/src/js/search.js:1882
#: code:addons/web/static/src/js/search.js:1916
#: code:addons/web/static/src/js/search.js:1940
#, python-format
msgid "is not equal to"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:549
#, python-format
msgid "Database restored successfully"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:590
#, python-format
msgid "Add..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:400
#, python-format
msgid "Preferences"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:1931
#, python-format
msgid "Confirm"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:622
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Maybe you should consider reloading the application by pressing F5..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:17
#: code:addons/web/static/src/xml/base.xml:112
#: code:addons/web/static/src/xml/base.xml:307
#: code:addons/web/static/src/xml/base.xml:764
#: code:addons/web/static/src/xml/base.xml:1325
#, python-format
[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 ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:186
#, python-format
msgid "Drop Database"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1883
#: code:addons/web/static/src/js/search.js:1917
#: code:addons/web/static/src/js/search.js:1941
#, python-format
msgid "greater than"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1884
#: code:addons/web/static/src/js/search.js:1918
#: code:addons/web/static/src/js/search.js:1942
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "less than"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:2184
#, python-format
msgid "Download \"%s\""
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:410
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Version"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:540
#, python-format
msgid "Latest Modification Date:"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1455
#, python-format
msgid "M2O search fields do not currently handle multiple default values"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:581
#, python-format
msgid "Delete this attachment"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:413
#, python-format
msgid "OpenERP is a trademark of the"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:885
#, python-format
msgid "(nolabel)"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:337
#, python-format
msgid "Unlimited"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:972
#: code:addons/web/static/src/xml/base.xml:350
#, python-format
msgid "More"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:73
#, python-format
msgid "Username"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:2912
#, python-format
msgid "Add %s"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1724
#, python-format
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."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:77
#, python-format
msgid "Form"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:784
#: code:addons/web/static/src/xml/base.xml:511
#, python-format
msgid "Fields View Get"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1273
#, python-format
msgid "(no string)"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:146
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Admin password:"
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:150
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Confirm password:"
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:594
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "%d days ago"
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[EXP] export translatable strings to templates bzr revid: xmo@openerp.com-20120206163406-vf12k01nxqbhnt3q
2012-02-06 16:34:06 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1802
#, python-format
msgid "Name:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1728
#, python-format
msgid "CSV File:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1743
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Advanced"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:416
#, python-format
msgid "OpenERP.com"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:325
#, python-format
msgid "New Password:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1628
#, python-format
msgid "Import-Compatible Export"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1640
#, python-format
msgid "Fields to export"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/data_export.js:374
#, python-format
msgid "Please select fields to export..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1557
#, python-format
msgid "Share with all users"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:595
#, python-format
msgid "about a month ago"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_tree.js:11
#, python-format
msgid "Tree"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1549
#, python-format
msgid "Custom Filters"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:287
#, python-format
msgid "New master password:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:503
#, python-format
msgid "Debug View#"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1976
#, python-format
msgid "is false"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1285
#, python-format
msgid "Button Type:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1629
#, python-format
msgid "Export all Data"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:414
#, python-format
msgid "OpenERP SA Company"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:1137
#, python-format
msgid "Do you really want to delete this attachment ?"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:1018
#, python-format
msgid "Unknown m2m command "
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1014
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#, python-format
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Select date"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1555
#, python-format
msgid "Custom Filter"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:399
#, python-format
msgid "About OpenERP"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:196
#: code:addons/web/static/src/js/view_list.js:356
#: code:addons/web/static/src/xml/base.xml:1713
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Delete"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:160
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
msgid "Duplicate Database"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:1674
#, python-format
msgid "Unknown field %s in domain %s"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:277
#: code:addons/web/static/src/xml/base.xml:335
#, python-format
msgid "Change Password"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:817
#, python-format
msgid "Incorrect value for field %(fieldname)s: [%(value)s] is %(message)s"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:305
#, python-format
msgid "Database Management"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4982
#, python-format
msgid "Image"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:81
#, python-format
msgid "Manage Databases"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1377
#, python-format
msgid "Advanced Search..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:172
#, python-format
msgid "Original database name:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1279
#, python-format
msgid "not a valid integer"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:82
#: code:addons/web/static/src/xml/base.xml:436
#, python-format
msgid "Powered by"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4926
#: code:addons/web/static/src/js/view_list.js:2172
#, python-format
msgid "Download"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1376
#: code:addons/web/static/src/xml/base.xml:922
#, python-format
msgid "Yes"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:1666
#, python-format
msgid "Unknown operator %s in domain %s"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:512
#: code:addons/web/static/src/xml/base.xml:1416
#, python-format
msgid "Manage Filters"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:77
#, python-format
msgid "Log in"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:350
#, python-format
msgid "Invalid database name"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1642
#, python-format
msgid "Save fields list"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1869
#, python-format
msgid "contains"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:414
#, python-format
msgid "Group"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1377
#, python-format
msgid "No"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:3779
#, python-format
msgid "The o2m record must be saved before an action can be used"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:879
#, python-format
msgid "Unhandled widget"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:591
#, python-format
msgid "about an hour ago"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:934
#, python-format
msgid "Selection:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1773
#, python-format
msgid "--- Don't Import ---"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4124
#: code:addons/web/static/src/js/view_form.js:4265
#: code:addons/web/static/src/xml/base.xml:1356
#: code:addons/web/static/src/xml/base.xml:1654
#, python-format
msgid "Add"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:122
#: code:addons/web/static/src/xml/base.xml:176
#: code:addons/web/static/src/xml/base.xml:265
#, python-format
msgid "New database name:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1219
#, python-format
msgid "...Upload in progress..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1717
#, python-format
msgid "Import"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:534
#, python-format
msgid "Creation Date:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1573
#, python-format
msgid "Add a condition"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:617
#, python-format
msgid "Still loading..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1619
#, python-format
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."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4822
#, python-format
msgid "File upload"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:3778
#, python-format
msgid "Action Button"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:829
#, python-format
msgid "All users"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:598
#, python-format
msgid "%d years ago"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:291
#, python-format
msgid "Confirm new master password:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:1071
#, python-format
msgid "Save default"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:621
#, python-format
msgid "Take a minute to get a coffee,<br />because it's loading..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:408
#, python-format
msgid "Activate the developer mode"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:324
#, python-format
msgid "Loading (%d)"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4857
#, python-format
msgid "The field is empty, there's nothing to save !"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:515
#, python-format
msgid "Manage Views"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:509
#, python-format
msgid "Backed"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1559
#, python-format
msgid "Use by default"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1554
#, python-format
msgid "Filter name"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:4821
#, python-format
msgid "The selected file exceed the maximum file size of %s."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1110
#, python-format
msgid "GroupBy"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1750
#, python-format
msgid "Encoding:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:683
#, python-format
msgid "You must select at least one record."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1757
#, python-format
msgid "Lines to skip"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:2834
#, python-format
msgid "Create \"<strong>%s</strong>\""
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/data_export.js:361
#, python-format
msgid "Please select fields to save export list..."
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/data_export.js:126
#, python-format
msgid "Please enter save field list name"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:1064
#, python-format
msgid "Set Default"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:930
#, python-format
msgid "Relation:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:588
#, python-format
msgid "less than a minute ago"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:774
#, python-format
msgid "triggered from search view"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:413
#, python-format
msgid "Copyright © 2004-TODAY OpenERP SA. All Rights Reserved."
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:977
#, python-format
msgid "Filter"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:902
#, python-format
msgid "Widget:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:803
#, python-format
msgid "Condition:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1638
#, python-format
msgid "Available fields"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1626
#, python-format
msgid "Export Type:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:1712
#, python-format
msgid "Unsupported operator %s in domain %s"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1784
#, python-format
msgid "The import failed due to:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:219
#: code:addons/web/static/src/xml/base.xml:310
#, python-format
msgid "Backup"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:509
#, python-format
msgid "JS Tests"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:518
#, python-format
[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 "Edit Action"
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:525
#, python-format
[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 "ID:"
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:926
#, python-format
msgid "Filter on: %s"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:971
#, python-format
msgid "Print"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:822
#, python-format
msgid "Only you"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:519
#, python-format
msgid "Edit Workflow"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:2844
#, python-format
msgid "Create and Edit..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:2880
#: code:addons/web/static/src/js/view_form.js:3731
#, python-format
msgid "Create: "
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:586
#: code:addons/web/static/src/xml/base.xml:1249
#, python-format
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgid "/web/binary/upload_attachment"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:510
#, python-format
msgid "View Fields"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1423
#, python-format
msgid "(Any existing filter with the same name will be replaced)"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:1934
#: code:addons/web/static/src/xml/base.xml:1326
#: code:addons/web/static/src/xml/base.xml:1809
#, python-format
msgid "Cancel"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/data_export.js:11
#: code:addons/web/static/src/js/view_form.js:1070
#: code:addons/web/static/src/xml/base.xml:1343
#, python-format
msgid "Close"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1667
#, python-format
msgid "Name"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/coresetup.js:616
#: code:addons/web/static/src/xml/base.xml:9
#, python-format
msgid "Loading..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:572
#, python-format
msgid "Do you really want to remove these records?"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:890
#, python-format
[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 "Field:"
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:910
#, python-format
msgid "Context:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:537
#, python-format
msgid "Latest Modification by:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:726
#: code:addons/web/static/src/xml/base.xml:767
#: code:addons/web/static/src/xml/base.xml:1331
#: code:addons/web/static/src/xml/base.xml:1561
#, python-format
msgid "Save"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1961
#, python-format
msgid "is not"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:520
#, python-format
msgid "Print Workflow"
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[IMP] get translated JS strings outside of QWeb attributes as the corresponding extractor does not actually work, export POTs bzr revid: xmo@openerp.com-20120214142954-4ndkj63pog39ts0k
2012-02-14 14:29:54 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1934
#: code:addons/web/static/src/js/search.js:1960
#, python-format
msgid "is"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/data_export.js:6
#, python-format
msgid "Export Data"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:284
#: code:addons/web/static/src/js/chrome.js:1121
#, python-format
msgid "Client Error"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:914
#, python-format
msgid "Domain:"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:505
#, python-format
msgid "View Log (perm_read)"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1753
#, python-format
msgid "UTF-8"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1280
#, python-format
msgid "Special:"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:788
#, python-format
msgid "Warning, the record has been modified, your changes will be discarded.\n"
"\n"
"Are you sure you want to leave this page ?"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:531
#, python-format
msgid "Creation User:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:68
#: code:addons/web/static/src/xml/base.xml:194
#: code:addons/web/static/src/xml/base.xml:226
#, python-format
msgid "Database:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:786
#, python-format
msgid "Default:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:1318
#, python-format
msgid "Undefined"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1734
#, python-format
msgid "Import Options"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:82
#: code:addons/web/static/src/xml/base.xml:437
#, python-format
msgid "OpenERP"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:416
#, python-format
msgid "For more information visit"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:773
#, python-format
msgid "Do you really want to delete this record?"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1334
#, python-format
msgid "Save & Close"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1807
#, python-format
msgid "Quick Add"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1132
#: code:addons/web/static/src/xml/base.xml:1189
#, python-format
msgid "Uploading ..."
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:426
#, python-format
msgid "%d / %d"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1808
#, python-format
msgid "Add All Info..."
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:75
#: code:addons/web/static/src/xml/base.xml:312
#, python-format
msgid "Password"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1632
#, python-format
msgid "Export Formats"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1731
#, python-format
msgid "2. Check your file format"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/chrome.js:1015
#, python-format
msgid "About"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/views.js:842
#, python-format
msgid "Model %s fields"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1380
#, python-format
msgid "Search Again"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1664
#: code:addons/web/static/src/xml/base.xml:1403
#, python-format
msgid "Filters"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1404
#, python-format
msgid "-- Filters --"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:516
#: code:addons/web/static/src/xml/base.xml:761
#: code:addons/web/static/src/xml/base.xml:1127
#, python-format
msgid "Edit"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1179
#: code:addons/web/static/src/xml/base.xml:1181
#, python-format
msgid "Clear"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:188
#: code:addons/web/static/src/xml/base.xml:309
#, python-format
msgid "Drop"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:8
#, python-format
msgid "List"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:918
#, python-format
msgid "Modifiers:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1414
#, python-format
msgid "Add Advanced Filter"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1699
#, python-format
msgid "Save as:"
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:1312
#, python-format
msgid "Grouping on field '%s' is not possible because that field does not appear in the list view."
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[MERGE] jQuery.timeago translation support, re-extract POTs bzr revid: xmo@openerp.com-20120702071428-0y2wuvn8wajvi6we
2012-07-02 07:14:28 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:507
#, python-format
msgid "Set Defaults"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1245
#, python-format
msgid "Search %(field)s for: %(value)s"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1870
#, python-format
msgid "doesn't contain"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:729
#: code:addons/web/static/src/xml/base.xml:769
#: code:addons/web/static/src/xml/base.xml:1340
#, python-format
msgid "Discard"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1226
#, python-format
msgid "Delete this file"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:415
#, python-format
msgid "Licenced under the terms of"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1415
#, python-format
msgid "Save Filter"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_form.js:2999
#: code:addons/web/static/src/js/view_form.js:3642
#: code:addons/web/static/src/js/view_form.js:3759
#: code:addons/web/static/src/js/view_form.js:4199
#: code:addons/web/static/src/js/view_form.js:4324
#, python-format
msgid "Open: "
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1293
#, python-format
msgid "Action ID:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:110
#, python-format
msgid "Create Database"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1380
#, python-format
msgid "Search"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:415
#, python-format
msgid "GNU Affero General Public License"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1744
#, python-format
msgid "Separator:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1705
#, python-format
[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 "Saved exports:"
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:401
#, python-format
msgid "Log out"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1086
#, python-format
msgid "Group by: %s"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:330
#, python-format
msgid "Confirm Password:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:728
#: code:addons/web/static/src/xml/base.xml:768
#: code:addons/web/static/src/xml/base.xml:1325
#: code:addons/web/static/src/xml/base.xml:1333
#: code:addons/web/static/src/xml/base.xml:1579
#, python-format
msgid "or"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/search.js:1885
#: code:addons/web/static/src/js/search.js:1919
#: code:addons/web/static/src/js/search.js:1943
#, python-format
msgid "greater or equal than"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:320
#, python-format
msgid "Old Password:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:301
#, python-format
msgid "Back to Login"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1421
#, python-format
msgid "Filter Name:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/view_list.js:355
#: code:addons/web/static/src/xml/base.xml:1614
#, python-format
msgid "Export"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/formats.js:113
#, python-format
msgid "Bytes,Kb,Mb,Gb,Tb,Pb,Eb,Zb,Yb"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1246
#, python-format
msgid "File"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:898
#, python-format
msgid "Type:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
#. openerp-web
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1574
#, python-format
msgid "Apply"
[I18N] Update translation template with newly exported attributes Includes @title, @alt and @label attributes for all qweb template elements. Web addons without any such attributes have not been re-exported. bzr revid: odo@openerp.com-20120207093155-laswlg40wgz6itlx
2012-02-07 09:31:55 +00:00
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:894
#, python-format
msgid "Object:"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/xml/base.xml:1335
#, python-format
msgid "Save & New"
[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
msgstr ""
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#. module: web
[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
[I18N] Update translation template in preparation for 7.0 release bzr revid: odo@openerp.com-20121124023937-bqm6b5wdsyiyetxi
2012-11-24 02:39:37 +00:00
#: code:addons/web/static/src/js/data_export.js:12
#, python-format
msgid "Export To File"
[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
msgstr ""