Commit 9ff0c1dc authored by Kazuhiko Shiozaki's avatar Kazuhiko Shiozaki

2009-01-20 Guillaume

* Field titles and descriptions clean up.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25213 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent e9dcebfa
......@@ -218,7 +218,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Text area field</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......@@ -262,7 +262,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Comment</string> </value>
<value> <string>Comments</string> </value>
</item>
<item>
<key> <string>unicode</string> </key>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Text area field</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......@@ -260,7 +260,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Comment</string> </value>
<value> <string>Comments</string> </value>
</item>
<item>
<key> <string>unicode</string> </key>
......
......@@ -218,7 +218,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Text area field</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......@@ -262,7 +262,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Comment</string> </value>
<value> <string>Comments</string> </value>
</item>
<item>
<key> <string>unicode</string> </key>
......
......@@ -95,6 +95,10 @@
<key> <string>default_now</string> </key>
<value> <int>1</int> </value>
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The date at which the event was created</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
<value> <int>1</int> </value>
......
......@@ -85,6 +85,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The name of a document in ERP5</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
<value> <int>1</int> </value>
......
......@@ -242,7 +242,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>To</string> </value>
<value> <string>Reply to</string> </value>
</item>
<item>
<key> <string>truncate</string> </key>
......
......@@ -218,7 +218,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Text area field</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......@@ -262,7 +262,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Comment</string> </value>
<value> <string>Comments</string> </value>
</item>
<item>
<key> <string>unicode</string> </key>
......
......@@ -85,7 +85,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Text area field</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......@@ -105,7 +105,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Comment</string> </value>
<value> <string>Comments</string> </value>
</item>
<item>
<key> <string>whitespace_preserve</string> </key>
......
......@@ -110,7 +110,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>content of the event</string> </value>
<value> <string>The content of the document considered as a text string</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......@@ -134,7 +134,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Body</string> </value>
<value> <string>Text</string> </value>
</item>
</dictionary>
</value>
......
......@@ -108,6 +108,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Tells who requested the ticket</string> </value>
</item>
<item>
<key> <string>extra_context</string> </key>
<value>
......@@ -122,6 +126,10 @@
<key> <string>form_id</string> </key>
<value> <string>Ticket_viewFieldLibrary</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Requester</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -77,7 +77,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>define to which project ticket is related</string> </value>
<value> <string>The accountable project on the requester side.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -148,7 +148,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>defined to whi the invoice will be sent</string> </value>
<value> <string>Defines to who the invoice will be sent</string> </value>
</item>
<item>
<key> <string>extra_context</string> </key>
......@@ -166,7 +166,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Billable Client</string> </value>
<value> <string>Client</string> </value>
</item>
</dictionary>
</value>
......
......@@ -72,6 +72,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The person or organization for which the services are being provided.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_destination_title</string> </value>
......@@ -84,6 +88,10 @@
<key> <string>target</string> </key>
<value> <string>Click to edit the target</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Location</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -74,7 +74,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Price for one unit.</string> </value>
<value> <string>The unit price at which a product or service is traded. This price is a net price which has been applied all pricing conditions defined in supply documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......@@ -90,7 +90,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Unit Price</string> </value>
<value> <string>Price</string> </value>
</item>
</dictionary>
</value>
......
......@@ -72,6 +72,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Reference of a document in ERP5, whatever the module considered. Exceptions to this rule can exist, and if so, terms will be described in the appropriate business field of this glossary. For example, the reference of a Payment Transaction has a specific name, as well as the Reference of Purchase and Sale Invoice Transactions. See the appropriate Glossary for further information.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_reference</string> </value>
......@@ -84,6 +88,10 @@
<key> <string>target</string> </key>
<value> <string>Click to edit the target</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Reference</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -144,6 +144,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Title of the entity which is responsible of accepting the ticket request</string> </value>
</item>
<item>
<key> <string>extra_context</string> </key>
<value>
......@@ -158,6 +162,10 @@
<key> <string>form_id</string> </key>
<value> <string>Ticket_viewFieldLibrary</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Supervisor</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -146,7 +146,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>defined who will provide the bill</string> </value>
<value> <string>Defines who will provide the bill</string> </value>
</item>
<item>
<key> <string>extra_context</string> </key>
......
......@@ -144,6 +144,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The person who is handling the ticket.</string> </value>
</item>
<item>
<key> <string>extra_context</string> </key>
<value>
......@@ -158,6 +162,10 @@
<key> <string>form_id</string> </key>
<value> <string>Ticket_viewFieldLibrary</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Operations Manager</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -72,6 +72,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The date at which the ticket was created.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_start_date</string> </value>
......@@ -84,6 +88,10 @@
<key> <string>target</string> </key>
<value> <string>Click to edit the target</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Begin Date</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -72,6 +72,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The date at which the ticket is supposed to stop.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_stop_date</string> </value>
......@@ -84,6 +88,10 @@
<key> <string>target</string> </key>
<value> <string>Click to edit the target</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>End Date</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -89,7 +89,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Tell who requested the ticket</string> </value>
<value> <string>Tells who requested the ticket</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -87,7 +87,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>defined to whi the invoice will be sent</string> </value>
<value> <string>Defines to who the invoice will be sent</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......@@ -118,7 +118,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Billable Client</string> </value>
<value> <string>Client</string> </value>
</item>
</dictionary>
</value>
......
......@@ -85,6 +85,10 @@
<key> <string>catalog_index</string> </key>
<value> <string>title</string> </value>
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The person or organization for which the services are being provided.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_relation_field</string> </value>
......
......@@ -74,6 +74,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Reference of a document in ERP5, whatever the module considered. Exceptions to this rule can exist, and if so, terms will be described in the appropriate business field of this glossary. For example, the reference of a Payment Transaction has a specific name, as well as the Reference of Purchase and Sale Invoice Transactions. See the appropriate Glossary for further information.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_string_field</string> </value>
......
......@@ -90,6 +90,10 @@
<key> <string>default_module</string> </key>
<value> <string>organisation</string> </value>
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Title of the entity which is responsible of accepting the ticket request</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_relation_field</string> </value>
......
......@@ -87,7 +87,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>defined who will provide the bill</string> </value>
<value> <string>Defines who will provide the bill</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -85,6 +85,10 @@
<key> <string>catalog_index</string> </key>
<value> <string>title</string> </value>
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The person who is handling the ticket.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_relation_field</string> </value>
......
......@@ -74,6 +74,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The date at which the ticket was created.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_date</string> </value>
......
......@@ -74,6 +74,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The date at which the ticket is supposed to stop.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_date</string> </value>
......
......@@ -78,7 +78,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>A description of the event</string> </value>
<value> <string>General description of a document in ERP5. Descriptions are not supposed to be internal, and in a case of certain documents such as invoices for example, will be seen by your customers.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......@@ -92,6 +92,10 @@
<key> <string>target</string> </key>
<value> <string>Click to edit the target</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Description</string> </value>
</item>
<item>
<key> <string>whitespace_preserve</string> </key>
<value> <int>0</int> </value>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>A description of the event</string> </value>
<value> <string>General description of a document in ERP5. Descriptions are not supposed to be internal, and in a case of certain documents such as invoices for example, will be seen by your customers.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -200,7 +200,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string></string> </value>
<value> <string>The name of a document in ERP5</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
330
\ No newline at end of file
333
\ No newline at end of file
......@@ -212,7 +212,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Base Price</string> </value>
<value> <string>Unit Base Price</string> </value>
</item>
<item>
<key> <string>whitespace_preserve</string> </key>
......
......@@ -77,7 +77,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Comments which can be read by internal users but which, unlike description, are not printed out on official documents.</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -200,7 +200,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The reference for the client.</string> </value>
<value> <string>The reference of the client.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -77,7 +77,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The organisation or person to whom merchandise or service is delivered over or provided to.</string> </value>
<value> <string>The organisation or person who is delivered goods or services in this operation</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The date until which the offer is valid.</string> </value>
<value> <string>The date when the document expires.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -196,7 +196,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Number of units involved in base prices</string> </value>
<value> <string>Number of units involved in base prices. If Priced Quantity is 1, it means that this is a unit price. If 2, the price is given for two units, etc...</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -192,7 +192,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Default quantity</string> </value>
<value> <string>Default Quantity of a resource in ERP5. It can be a product or it can be time quantity like hours or minutes for example. Quantity can be found in almost every business field of ERP5 and will always have this meaning, unless the term is different or precise, such as Priced Quantity for example.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -382,7 +382,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string></string> </value>
<value> <string>A resource in ERP5 can be a product or a service. This term will be found in orders for instance, or accounting and inventories.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......@@ -475,7 +475,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Resource</string> </value>
<value> <string>Product or Service</string> </value>
</item>
<item>
<key> <string>truncate</string> </key>
......
......@@ -212,7 +212,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Base Price</string> </value>
<value> <string>Unit Base Price</string> </value>
</item>
<item>
<key> <string>whitespace_preserve</string> </key>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Comments which can be read by internal users but which, unlike description, are not printed out on official documents.</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>General description which may be printed out on official documents and read by suppliers and clients.</string> </value>
<value> <string>General description of a document in ERP5. Descriptions are not supposed to be internal, and in a case of certain documents such as invoices for example, will be seen by your customers.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -200,7 +200,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The reference for the client.</string> </value>
<value> <string>The reference of the client.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -378,7 +378,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The organisation or person to whom merchandise or service is delivered over or provided to.</string> </value>
<value> <string>The organisation or person who is delivered goods or services in this operation</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -256,7 +256,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The date until which the offer is valid.</string> </value>
<value> <string>The date when the document expires.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -196,7 +196,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Number of units involved in base prices</string> </value>
<value> <string>Number of units involved in base prices. If Priced Quantity is 1, it means that this is a unit price. If 2, the price is given for two units, etc...</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -192,7 +192,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Default quantity</string> </value>
<value> <string>Default Quantity of a resource in ERP5. It can be a product or it can be time quantity like hours or minutes for example. Quantity can be found in almost every business field of ERP5 and will always have this meaning, unless the term is different or precise, such as Priced Quantity for example.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -382,7 +382,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string></string> </value>
<value> <string>A resource in ERP5 can be a product or a service. This term will be found in orders for instance, or accounting and inventories.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......@@ -475,7 +475,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Resource</string> </value>
<value> <string>Product or Service</string> </value>
</item>
<item>
<key> <string>truncate</string> </key>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>General description which may be printed out on official documents and read by suppliers and clients.</string> </value>
<value> <string>General description of a document in ERP5. Descriptions are not supposed to be internal, and in a case of certain documents such as invoices for example, will be seen by your customers.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -176,7 +176,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Default quantity</string> </value>
<value> <string>Default Quantity of a resource in ERP5. It can be a product or it can be time quantity like hours or minutes for example. Quantity can be found in almost every business field of ERP5 and will always have this meaning, unless the term is different or precise, such as Priced Quantity for example.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -310,7 +310,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string></string> </value>
<value> <string>A resource in ERP5 can be a product or a service. This term will be found in orders for instance, or accounting and inventories.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......@@ -403,7 +403,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Resource</string> </value>
<value> <string>Product or Service</string> </value>
</item>
<item>
<key> <string>truncate</string> </key>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>General description which may be printed out on official documents and read by suppliers and clients.</string> </value>
<value> <string>General description of a document in ERP5. Descriptions are not supposed to be internal, and in a case of certain documents such as invoices for example, will be seen by your customers.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -72,6 +72,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>A resource in ERP5 can be a product or a service. This term will be found in orders for instance, or accounting and inventories.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_resource_title</string> </value>
......@@ -84,6 +88,10 @@
<key> <string>target</string> </key>
<value> <string>Click to edit the target</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Product or Service</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -196,7 +196,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>index used to sort document</string> </value>
<value> <string>Sort Index will either give a calculation order or a sorting order of a document in a list that contains many documents.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......@@ -240,7 +240,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>listbox_int_index</string> </value>
<value> <string>Sort Index</string> </value>
</item>
<item>
<key> <string>whitespace_preserve</string> </key>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>General description which may be printed out on official documents and read by suppliers and clients.</string> </value>
<value> <string>General description of a document in ERP5. Descriptions are not supposed to be internal, and in a case of certain documents such as invoices for example, will be seen by your customers.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -382,7 +382,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string></string> </value>
<value> <string>A resource in ERP5 can be a product or a service. This term will be found in orders for instance, or accounting and inventories.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......@@ -475,7 +475,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Resource</string> </value>
<value> <string>Product or Service</string> </value>
</item>
<item>
<key> <string>truncate</string> </key>
......
......@@ -79,6 +79,10 @@
<key> <string>css_class</string> </key>
<value> <string>figure</string> </value>
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Sort Index will either give a calculation order or a sorting order of a document in a list that contains many documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_integer_value</string> </value>
......@@ -93,7 +97,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Index</string> </value>
<value> <string>Sort Index</string> </value>
</item>
</dictionary>
</value>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The internal reference.</string> </value>
<value> <string>Reference of a document in ERP5, whatever the module considered. Exceptions to this rule can exist, and if so, terms will be described in the appropriate business field of this glossary. For example, the reference of a Payment Transaction has a specific name, as well as the Reference of Purchase and Sale Invoice Transactions. See the appropriate Glossary for further information.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -92,6 +92,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>A resource in ERP5 can be a product or a service. This term will be found in orders for instance, or accounting and inventories.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_relation_field</string> </value>
......
......@@ -77,7 +77,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The organisation or person to whom merchandise or service is delivered over or provided to.</string> </value>
<value> <string>The organisation or person who is delivered goods or services in this operation</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -81,7 +81,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>index used to sort document</string> </value>
<value> <string>Sort Index will either give a calculation order or a sorting order of a document in a list that contains many documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......@@ -97,7 +97,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Index</string> </value>
<value> <string>Sort Index</string> </value>
</item>
</dictionary>
</value>
......
......@@ -92,6 +92,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The unit price at which a product or service is traded. This price is a net price which has been applied all pricing conditions defined in supply documents.</string> </value>
</item>
<item>
<key> <string>enabled</string> </key>
<value> <int>1</int> </value>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The internal reference.</string> </value>
<value> <string>Reference of a document in ERP5, whatever the module considered. Exceptions to this rule can exist, and if so, terms will be described in the appropriate business field of this glossary. For example, the reference of a Payment Transaction has a specific name, as well as the Reference of Purchase and Sale Invoice Transactions. See the appropriate Glossary for further information.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -101,7 +101,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The product or service which is traded.</string> </value>
<value> <string>A resource in ERP5 can be a product or a service. This term will be found in orders for instance, or accounting and inventories.</string> </value>
</item>
<item>
<key> <string>enabled</string> </key>
......
......@@ -369,7 +369,7 @@ AAA=</string> </value>
</table:table>\n
</style:header>\n
<style:footer>\n
<text:p text:style-name="Footer">Generated with ERP5 \xe2\x80\x93 Open Source ERP suite (www.erp5.org)</text:p>\n
<text:p text:style-name="Footer">Generated with ERP5 Open Source ERP suite (www.erp5.org)</text:p>\n
</style:footer>\n
</style:master-page>\n
<style:master-page style:name="Endnote" style:page-layout-name="pm2"/>\n
......
......@@ -369,7 +369,7 @@ AAA=</string> </value>
</table:table>\n
</style:header>\n
<style:footer>\n
<text:p text:style-name="Footer">Generated with ERP5 \xe2\x80\x93 Open Source ERP suite (www.erp5.org)</text:p>\n
<text:p text:style-name="Footer">Generated with ERP5 Open Source ERP suite (www.erp5.org)</text:p>\n
</style:footer>\n
</style:master-page>\n
<style:master-page style:name="Endnote" style:page-layout-name="pm2"/>\n
......
......@@ -218,7 +218,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Comments which can be read by internal users but which, unlike description, are not printed out on official documents.</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -3,11 +3,8 @@
<record id="1" aka="AAAAAAAAAAE=">
<pickle>
<tuple>
<tuple>
<string>Products.Formulator.StandardFields</string>
<string>StringField</string>
</tuple>
<none/>
<global name="StringField" module="Products.Formulator.StandardFields"/>
<tuple/>
</tuple>
</pickle>
<pickle>
......
......@@ -99,7 +99,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The person or organisation in charge of paying for the client.</string> </value>
<value> <string>The organisation or person in charge of paying for the client.</string> </value>
</item>
<item>
<key> <string>enabled</string> </key>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>index used to sort document</string> </value>
<value> <string>Sort Index will either give a calculation order or a sorting order of a document in a list that contains many documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......@@ -92,7 +92,7 @@
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Index</string> </value>
<value> <string>Sort Index</string> </value>
</item>
</dictionary>
</value>
......
......@@ -87,7 +87,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Defines an additional term for making payment after the end of the month.</string> </value>
<value> <string>Defines the additional term (in days) allowed to the customer to pay his order</string> </value>
</item>
<item>
<key> <string>enabled</string> </key>
......
......@@ -87,7 +87,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The term (number of days) for making payment</string> </value>
<value> <string>The term (days) allowed to the customer for the payment of the order</string> </value>
</item>
<item>
<key> <string>enabled</string> </key>
......
......@@ -99,7 +99,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The person or organisation in charge of receiving the payment for the supplier.</string> </value>
<value> <string>The organisation or person in charge of receiving the payment for the supplier.</string> </value>
</item>
<item>
<key> <string>enabled</string> </key>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The reference for the client.</string> </value>
<value> <string>The reference of the client.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -77,7 +77,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The internal reference.</string> </value>
<value> <string>Reference of a document in ERP5, whatever the module considered. Exceptions to this rule can exist, and if so, terms will be described in the appropriate business field of this glossary. For example, the reference of a Payment Transaction has a specific name, as well as the Reference of Purchase and Sale Invoice Transactions. See the appropriate Glossary for further information.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The reference for the supplier.</string> </value>
<value> <string>The reference of the supplier.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -75,6 +75,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_text_area_field</string> </value>
......
......@@ -92,7 +92,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The person or organisation in charge of paying for the client.</string> </value>
<value> <string>The organisation or person in charge of paying for the client.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -108,6 +108,10 @@
</list>
</value>
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The organisation or person in charge of paying for the client.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_relation_field</string> </value>
......
......@@ -111,7 +111,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The organisation or person to whom merchandise or service is delivered over or provided to.</string> </value>
<value> <string>The organisation or person who is delivered goods or services in this operation</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The date until which the offer is valid.</string> </value>
<value> <string>The date when the document expires.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -92,7 +92,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The person or organisation in charge of receiving the payment for the supplier.</string> </value>
<value> <string>The organisation or person in charge of receiving the payment for the supplier.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
......@@ -216,7 +216,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Comments which can be read by internal users but which, unlike description, are not printed out on official documents.</string> </value>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>editable</string> </key>
......
......@@ -274,7 +274,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>The organisation or person to whom merchandise or service is delivered over or provided to.</string> </value>
<value> <string>The organisation or person who is delivered goods or services in this operation</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -200,7 +200,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>A one line title which describes a product, an order, a supply, a trade condition. It may be used in official documents.</string> </value>
<value> <string>The name of a document in ERP5</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -72,6 +72,10 @@
<key> <string>values</string> </key>
<value>
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>Comments which can be read by internal users but unlike description, are not printed out on official documents.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
<value> <string>my_comment</string> </value>
......@@ -84,6 +88,10 @@
<key> <string>target</string> </key>
<value> <string>Click to edit the target</string> </value>
</item>
<item>
<key> <string>title</string> </key>
<value> <string>Comments</string> </value>
</item>
</dictionary>
</value>
</item>
......
......@@ -194,7 +194,7 @@
</item>
<item>
<key> <string>description</string> </key>
<value> <string>Default quantity</string> </value>
<value> <string>Default Quantity of a resource in ERP5. It can be a product or it can be time quantity like hours or minutes for example. Quantity can be found in almost every business field of ERP5 and will always have this meaning, unless the term is different or precise, such as Priced Quantity for example.</string> </value>
</item>
<item>
<key> <string>display_maxwidth</string> </key>
......
......@@ -76,7 +76,7 @@
<dictionary>
<item>
<key> <string>description</string> </key>
<value> <string>The internal reference.</string> </value>
<value> <string>Reference of a document in ERP5, whatever the module considered. Exceptions to this rule can exist, and if so, terms will be described in the appropriate business field of this glossary. For example, the reference of a Payment Transaction has a specific name, as well as the Reference of Purchase and Sale Invoice Transactions. See the appropriate Glossary for further information.</string> </value>
</item>
<item>
<key> <string>field_id</string> </key>
......
569
\ No newline at end of file
570
\ No newline at end of file
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment