[Checkins] SVN: zope.app.form/trunk/s made section level underlinings consistent in order to fix the PyPI page

[Thomas Lotze]

Log message for revision 90930:
  made section level underlinings consistent in order to fix the PyPI page

Changed:
  U   zope.app.form/trunk/setup.py
  U   zope.app.form/trunk/src/zope/app/form/browser/form.txt
  U   zope.app.form/trunk/src/zope/app/form/browser/i18n.txt
  U   zope.app.form/trunk/src/zope/app/form/browser/source.txt

-=-
Modified: zope.app.form/trunk/setup.py
===================================================================
--- zope.app.form/trunk/setup.py	2008-09-08 07:32:41 UTC (rev 90929)
+++ zope.app.form/trunk/setup.py	2008-09-08 07:56:42 UTC (rev 90930)
@@ -29,8 +29,7 @@
       long_description=(
           read('README.txt')
           + '\n\n' +
-          'Detailed Documentation\n'
-          '----------------------\n'
+          'Detailed documentation:\n'
           + '\n\n' +
           read('src', 'zope', 'app', 'form', 'browser', 'README.txt')
           + '\n\n' +

Modified: zope.app.form/trunk/src/zope/app/form/browser/form.txt
===================================================================
--- zope.app.form/trunk/src/zope/app/form/browser/form.txt	2008-09-08 07:32:41 UTC (rev 90929)
+++ zope.app.form/trunk/src/zope/app/form/browser/form.txt	2008-09-08 07:56:42 UTC (rev 90930)
@@ -96,7 +96,7 @@
 
 
 Using the `browser:form` directive
-----------------------------------
+==================================
 
 Let's now see how the form directive works. The first task is to load the
 necessary meta-configuration:

Modified: zope.app.form/trunk/src/zope/app/form/browser/i18n.txt
===================================================================
--- zope.app.form/trunk/src/zope/app/form/browser/i18n.txt	2008-09-08 07:32:41 UTC (rev 90929)
+++ zope.app.form/trunk/src/zope/app/form/browser/i18n.txt	2008-09-08 07:56:42 UTC (rev 90930)
@@ -52,7 +52,7 @@
 
 
 Translated
-----------
+==========
 
 And now the add form in German:
 
@@ -119,7 +119,7 @@
 
 
 Source widgets
---------------
+==============
 
 Titles of terms are translated by the source widgets. Let's create a source
 for which the terms create message ids:

Modified: zope.app.form/trunk/src/zope/app/form/browser/source.txt
===================================================================
--- zope.app.form/trunk/src/zope/app/form/browser/source.txt	2008-09-08 07:32:41 UTC (rev 90929)
+++ zope.app.form/trunk/src/zope/app/form/browser/source.txt	2008-09-08 07:56:42 UTC (rev 90930)
@@ -64,7 +64,7 @@
 
 
 Iterable Source Widgets
------------------------
+=======================
 
 Iterable sources are expected to be simpler than queriable sources, so
 they represent a good place to start.  The most important aspect of
@@ -490,7 +490,7 @@
 
 
 Source Widget Query Framework
------------------------------
+=============================
 
 An important aspect of sources is that they may have too many values
 to enumerate.  Rather than listing all of the values, we, instead,
@@ -1058,7 +1058,7 @@
 
 
 Using vocabulary-dependent widgets with sources
-------------------------------------------------
+===============================================
 
 if you have a widget that uses old-style vocabularies but don't have the
 time to rewrite it for sources, all is not lost! The wrapper