fix structured text format for HelpSys

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@14593 20353a03-c40f-0410-a6d1-a30d3c3de9de

product/ERP5Type/help/001-overview.stx

-ERP5 is based on a Rapid Application Developpment (RAD)
-framework: **ERP5Type**. ERP5Type allows to reduce by 50% or more
-the number of lines of code needed to develop a Zope / CMF application.
-It provides an efficient way to create complex forms. It implements
-categories and relations. It also includes a flexible and fast
-cataloging mechanism for ERP documents based on simple SQL queries.
-**With ERP5Type, the Zope object database can be queried using
-simple or complex SQL queries and implements relations.**
-
-In this chapter, we shall introduce the ERP5 RAD.
+Overview
+
+  ERP5 is based on a Rapid Application Developpment (RAD) framework:
+  **ERP5Type**. ERP5Type allows to reduce by 50% or more the number of lines of
+  code needed to develop a Zope / CMF application.  It provides an efficient
+  way to create complex forms. It implements categories and relations. It also
+  includes a flexible and fast cataloging mechanism for ERP documents based on
+  simple SQL queries. 
+  
+  **With ERP5Type, the Zope object database can be queried using simple or
+  complex SQL queries and implements relations.**
+  
+  In this chapter, we shall introduce the ERP5 RAD.
 
 ERP5Type: professional ERP applications in a matter of minutes
 

product/ERP5Type/help/PropertySheets.stx

-ERP systems involve many different attribute names which
-can be used in different contexts. For example, a resource
-may have a default global price. A path may define a default price
-for specific source.
+PropertySheets
   
-ERP5 uses PropertySheets in order to provide an explicit data model
-which is used independently from interfaces. The role of interfaces
-is to define common explicit behaviour which can be implemented through
-by different classes. The role of property sheets is
-to define common **attribute sets** which can be stored on instances
-of different documents.
+  ERP systems involve many different attribute names which
+  can be used in different contexts. For example, a resource
+  may have a default global price. A path may define a default price
+  for specific source.
   
-PropertySheets also hold explicit information about of the ERP data structure.
-For example, some documents may not hold themselves pricing information
-but rather acquire it through the order or the sourcing contract they depend from.
+  ERP5 uses PropertySheets in order to provide an explicit data model
+  which is used independently from interfaces. The role of interfaces
+  is to define common explicit behaviour which can be implemented through
+  by different classes. The role of property sheets is
+  to define common **attribute sets** which can be stored on instances
+  of different documents.
   
-ERP5 implements this feature through **explicit acquisition**. The value
-of attributes can be obtained by looking up the value of that attribute
-on another related document or by calling a method on another related document.
+  PropertySheets also hold explicit information about of the ERP data structure.
+  For example, some documents may not hold themselves pricing information
+  but rather acquire it through the order or the sourcing contract they depend from.
   
-Explicit acquisition requires to define relations between documents. The general
-model adopted by ERP5 is a **categorization** model which is equivalent to
-a DACG model (Direct Acyclic Colored Graph). Thanks to Zope acquisition, this model
-is theoretically equivalent to a relationnal model.
+  ERP5 implements this feature through **explicit acquisition**. The value
+  of attributes can be obtained by looking up the value of that attribute
+  on another related document or by calling a method on another related document.
   
-We will explain bellow how those three concepts (attribute sets, categorization and
-explicit acquisition) relate and how to define new Property Sheets in ERP5.
+  Explicit acquisition requires to define relations between documents. The general
+  model adopted by ERP5 is a **categorization** model which is equivalent to
+  a DACG model (Direct Acyclic Colored Graph). Thanks to Zope acquisition, this model
+  is theoretically equivalent to a relationnal model.
   
-Attribute Sets
+  We will explain bellow how those three concepts (attribute sets, categorization and
+  explicit acquisition) relate and how to define new Property Sheets in ERP5.
+  
+  Attribute Sets
   
     ERP5 uses Attribute  Sets based on an approach which was originally developped
     by Max M. for its Zope Easy Product (http://www.zope.org/Members/maxm/HowTo/easyProduct).
@@ -228,7 +230,7 @@ Attribute Sets
     
     *Implementation*: functions createDefaultAccessors and
   
-Categories
+  Categories
   
   
     First of all, a certain number
@@ -314,7 +316,7 @@ Categories
     in Utils.py
   
   
-Categories and relations
+  Categories and relations
   
     Categories allow to implement document categorization but also relations.
     In ERP5, categories are managed by a portal tool names **portal_categories**.
@@ -352,7 +354,7 @@ Categories and relations
     **All relations are therefore treated in ERP5 as categories**
   
   
-Explicit Relational Acquisition
+  Explicit Relational Acquisition
   
   
     One of the purpose of property sheets is to create
@@ -420,21 +422,21 @@ Explicit Relational Acquisition
       _getReferenceList
   
   
-FAQ
+  FAQ
   
     Do I need to create an attribute for a category ?
   
     It depends : if some information can be in a different application,
     you need to holde the information somewhere, ....
   
-Possible scenario
+  Possible scenario
   
     copy_value
     mask_value
     sync_value
   
     
-Future
+  Future
     
     Atribute lookup should be put outside property sheet
     into a tool ?