odoo/addons/web_kanban/i18n/web_kanban.pot

161 lines
3.4 KiB
Plaintext
Raw Normal View History

# Translation of OpenERP Server.
# This file contains the translation of the following modules:
# * web_kanban
[IMP] refactored translation system to merge web translations with addons translations - Moved the web *.po files to /i18n to be consistent with the addons convention. Using /po was considered for a while because it played better with LP's auto- detection of PO Templates, but that is not necessary anymore, we now have full control on LP templates. - In order to support addons that contain translations for both the web addon and the regular addon part, both kinds of translations are now merged in a single addon/i18n/addon.pot file. Terms that are used by the web part are now marked with a PO annotation: #. openerp-web so the web client can recognize them and only load the relevant translations in the browser memory. This is important because a complete PO file can be rather large, e.g. account/i18n/de.po = 400KB. - The web translation export scripts were updated to behave properly for addons that have a non-web part, and will merge the web translation in the original POT file, annotating the web translations as needed. These scripts are Unix-only and meant to be used by OpenERP packagers when needed. - The GetText spec says that PO auto-comments indicating the source location have this form: #: /path/to/file:lineno However OpenERP's POT export system defaults to a modified version of this format with an extra 'type' field: #: type:/path/to/file:lineno The babel extractors we use have the GetText format hardcoded so a small patch is needed on the server to make it more lenient and accept the standard source annotation, defaulting to 'code' type. This does not matter for openerp-web, but makes sure the server will not fail to load the new PO files that contain openerp-web translations with standard annotations. The patch for making the server more lenient was checked in trunk at revision 4002 rev-id odo@openerp.com-20120202143210-05p1w24t6u77cyv8 - The existing translation sync and export wizards for regular addons have not been updated to consider web addons, so for the time being we will have to export regular addons terms first, and run the web export script (gen_translations.sh) on the addons directory afterwards. This could be improved later. As soon as this change is merged we will have to perform a full update of addons translation templates 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 ""
"Project-Id-Version: OpenERP Server 7.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2014-08-14 00:11+0000\n"
"PO-Revision-Date: 2014-08-14 00:11+0000\n"
"Last-Translator: <>\n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"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
#. module: web_kanban
[IMP] refactored translation system to merge web translations with addons translations - Moved the web *.po files to /i18n to be consistent with the addons convention. Using /po was considered for a while because it played better with LP's auto- detection of PO Templates, but that is not necessary anymore, we now have full control on LP templates. - In order to support addons that contain translations for both the web addon and the regular addon part, both kinds of translations are now merged in a single addon/i18n/addon.pot file. Terms that are used by the web part are now marked with a PO annotation: #. openerp-web so the web client can recognize them and only load the relevant translations in the browser memory. This is important because a complete PO file can be rather large, e.g. account/i18n/de.po = 400KB. - The web translation export scripts were updated to behave properly for addons that have a non-web part, and will merge the web translation in the original POT file, annotating the web translations as needed. These scripts are Unix-only and meant to be used by OpenERP packagers when needed. - The GetText spec says that PO auto-comments indicating the source location have this form: #: /path/to/file:lineno However OpenERP's POT export system defaults to a modified version of this format with an extra 'type' field: #: type:/path/to/file:lineno The babel extractors we use have the GetText format hardcoded so a small patch is needed on the server to make it more lenient and accept the standard source annotation, defaulting to 'code' type. This does not matter for openerp-web, but makes sure the server will not fail to load the new PO files that contain openerp-web translations with standard annotations. The patch for making the server more lenient was checked in trunk at revision 4002 rev-id odo@openerp.com-20120202143210-05p1w24t6u77cyv8 - The existing translation sync and export wizards for regular addons have not been updated to consider web addons, so for the time being we will have to export regular addons terms first, and run the web export script (gen_translations.sh) on the addons directory afterwards. This could be improved later. As soon as this change is merged we will have to perform a full update of addons translation templates 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
#: code:addons/web_kanban/static/src/js/kanban.js:698
#, python-format
msgid "Edit column"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:80
#, python-format
msgid "Show more... ("
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/js/kanban.js:10
#, 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 "Kanban"
msgstr ""
#. module: web_kanban
[IMP] refactored translation system to merge web translations with addons translations - Moved the web *.po files to /i18n to be consistent with the addons convention. Using /po was considered for a while because it played better with LP's auto- detection of PO Templates, but that is not necessary anymore, we now have full control on LP templates. - In order to support addons that contain translations for both the web addon and the regular addon part, both kinds of translations are now merged in a single addon/i18n/addon.pot file. Terms that are used by the web part are now marked with a PO annotation: #. openerp-web so the web client can recognize them and only load the relevant translations in the browser memory. This is important because a complete PO file can be rather large, e.g. account/i18n/de.po = 400KB. - The web translation export scripts were updated to behave properly for addons that have a non-web part, and will merge the web translation in the original POT file, annotating the web translations as needed. These scripts are Unix-only and meant to be used by OpenERP packagers when needed. - The GetText spec says that PO auto-comments indicating the source location have this form: #: /path/to/file:lineno However OpenERP's POT export system defaults to a modified version of this format with an extra 'type' field: #: type:/path/to/file:lineno The babel extractors we use have the GetText format hardcoded so a small patch is needed on the server to make it more lenient and accept the standard source annotation, defaulting to 'code' type. This does not matter for openerp-web, but makes sure the server will not fail to load the new PO files that contain openerp-web translations with standard annotations. The patch for making the server more lenient was checked in trunk at revision 4002 rev-id odo@openerp.com-20120202143210-05p1w24t6u77cyv8 - The existing translation sync and export wizards for regular addons have not been updated to consider web addons, so for the time being we will have to export regular addons terms first, and run the web export script (gen_translations.sh) on the addons directory afterwards. This could be improved later. As soon as this change is merged we will have to perform a full update of addons translation templates 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
#: code:addons/web_kanban/static/src/js/kanban.js:551
#, 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 "Undefined"
msgstr ""
#. module: web_kanban
[IMP] refactored translation system to merge web translations with addons translations - Moved the web *.po files to /i18n to be consistent with the addons convention. Using /po was considered for a while because it played better with LP's auto- detection of PO Templates, but that is not necessary anymore, we now have full control on LP templates. - In order to support addons that contain translations for both the web addon and the regular addon part, both kinds of translations are now merged in a single addon/i18n/addon.pot file. Terms that are used by the web part are now marked with a PO annotation: #. openerp-web so the web client can recognize them and only load the relevant translations in the browser memory. This is important because a complete PO file can be rather large, e.g. account/i18n/de.po = 400KB. - The web translation export scripts were updated to behave properly for addons that have a non-web part, and will merge the web translation in the original POT file, annotating the web translations as needed. These scripts are Unix-only and meant to be used by OpenERP packagers when needed. - The GetText spec says that PO auto-comments indicating the source location have this form: #: /path/to/file:lineno However OpenERP's POT export system defaults to a modified version of this format with an extra 'type' field: #: type:/path/to/file:lineno The babel extractors we use have the GetText format hardcoded so a small patch is needed on the server to make it more lenient and accept the standard source annotation, defaulting to 'code' type. This does not matter for openerp-web, but makes sure the server will not fail to load the new PO files that contain openerp-web translations with standard annotations. The patch for making the server more lenient was checked in trunk at revision 4002 rev-id odo@openerp.com-20120202143210-05p1w24t6u77cyv8 - The existing translation sync and export wizards for regular addons have not been updated to consider web addons, so for the time being we will have to export regular addons terms first, and run the web export script (gen_translations.sh) on the addons directory afterwards. This could be improved later. As soon as this change is merged we will have to perform a full update of addons translation templates 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
#: code:addons/web_kanban/static/src/js/kanban.js:717
#, python-format
msgid "Are you sure to remove this column ?"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:47
#, python-format
msgid "Edit"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/js/kanban.js:192
#, python-format
msgid "Add column"
[IMP] refactored translation system to merge web translations with addons translations - Moved the web *.po files to /i18n to be consistent with the addons convention. Using /po was considered for a while because it played better with LP's auto- detection of PO Templates, but that is not necessary anymore, we now have full control on LP templates. - In order to support addons that contain translations for both the web addon and the regular addon part, both kinds of translations are now merged in a single addon/i18n/addon.pot file. Terms that are used by the web part are now marked with a PO annotation: #. openerp-web so the web client can recognize them and only load the relevant translations in the browser memory. This is important because a complete PO file can be rather large, e.g. account/i18n/de.po = 400KB. - The web translation export scripts were updated to behave properly for addons that have a non-web part, and will merge the web translation in the original POT file, annotating the web translations as needed. These scripts are Unix-only and meant to be used by OpenERP packagers when needed. - The GetText spec says that PO auto-comments indicating the source location have this form: #: /path/to/file:lineno However OpenERP's POT export system defaults to a modified version of this format with an extra 'type' field: #: type:/path/to/file:lineno The babel extractors we use have the GetText format hardcoded so a small patch is needed on the server to make it more lenient and accept the standard source annotation, defaulting to 'code' type. This does not matter for openerp-web, but makes sure the server will not fail to load the new PO files that contain openerp-web translations with standard annotations. The patch for making the server more lenient was checked in trunk at revision 4002 rev-id odo@openerp.com-20120202143210-05p1w24t6u77cyv8 - The existing translation sync and export wizards for regular addons have not been updated to consider web addons, so for the time being we will have to export regular addons terms first, and run the web export script (gen_translations.sh) on the addons directory afterwards. This could be improved later. As soon as this change is merged we will have to perform a full update of addons translation templates 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 ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/js/kanban.js:1094
#, python-format
msgid "Create: "
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:24
#, python-format
msgid "Add a new column"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/js/kanban.js:689
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:45
#, python-format
msgid "Fold"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:98
#, python-format
msgid "Add"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:35
#, python-format
msgid "Quick create"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/js/kanban.js:930
#, python-format
msgid "Are you sure you want to delete this record ?"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/js/kanban.js:689
#, python-format
msgid "Unfold"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:99
#, python-format
msgid "Cancel"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:80
#, python-format
msgid "remaining)"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/js/kanban.js:433
#, python-format
msgid "An error has occured while moving the record to this group: "
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:22
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:98
#, python-format
msgid "or"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:40
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:55
#, python-format
msgid "99+"
msgstr ""
#. module: web_kanban
#. openerp-web
#: code:addons/web_kanban/static/src/xml/web_kanban.xml:48
#, python-format
msgid "Delete"
msgstr ""