[Checkins] SVN: z3c.recipe.i18n/trunk/ Let the .txt files be rendered nicely by docutils.

Uli Fouquet uli at gnufix.de
Wed Sep 24 09:00:41 EDT 2008


Log message for revision 91424:
  Let the .txt files be rendered nicely by docutils.

Changed:
  U   z3c.recipe.i18n/trunk/README.txt
  U   z3c.recipe.i18n/trunk/setup.py
  U   z3c.recipe.i18n/trunk/src/z3c/recipe/i18n/README.txt

-=-
Modified: z3c.recipe.i18n/trunk/README.txt
===================================================================
--- z3c.recipe.i18n/trunk/README.txt	2008-09-24 12:45:09 UTC (rev 91423)
+++ z3c.recipe.i18n/trunk/README.txt	2008-09-24 13:00:40 UTC (rev 91424)
@@ -1,2 +1,6 @@
+***************
+z3c.recipe.i18n
+***************
+
 This Zope 3 recipes offers different tools which allows to extract i18n 
 translation messages from egg based packages.

Modified: z3c.recipe.i18n/trunk/setup.py
===================================================================
--- z3c.recipe.i18n/trunk/setup.py	2008-09-24 12:45:09 UTC (rev 91423)
+++ z3c.recipe.i18n/trunk/setup.py	2008-09-24 13:00:40 UTC (rev 91424)
@@ -22,7 +22,7 @@
 
 def read(*rnames):
     text = open(os.path.join(os.path.dirname(__file__), *rnames)).read()
-    return xml.sax.saxutils.escape(text)
+    return text
 
 setup(
     name = 'z3c.recipe.i18n',
@@ -33,6 +33,7 @@
     long_description=(
         read('README.txt')
         + '\n\n' +
+        '**********************\n'
         'Detailed Documentation\n'
         '**********************'
         + '\n\n' +

Modified: z3c.recipe.i18n/trunk/src/z3c/recipe/i18n/README.txt
===================================================================
--- z3c.recipe.i18n/trunk/src/z3c/recipe/i18n/README.txt	2008-09-24 12:45:09 UTC (rev 91423)
+++ z3c.recipe.i18n/trunk/src/z3c/recipe/i18n/README.txt	2008-09-24 13:00:40 UTC (rev 91424)
@@ -10,7 +10,7 @@
 
 The 'i18n' recipe can be used to generate the required scripts for extract
 message ids from egg based packages. The i18nmerge allows to merge them into
-a *.po file. And the i18nstats script gives you an overview about the state
+a .po file. And the i18nstats script gives you an overview about the state
 of the translated files.
 
 Note
@@ -73,7 +73,7 @@
 Test
 ****
 
-Lets define some (bogus) eggs that we can use in our application:
+Lets define some (bogus) eggs that we can use in our application::
 
   >>> mkdir('outputDir')
   >>> mkdir('demo1')
@@ -90,7 +90,7 @@
   ... setup(name = 'demo2', install_requires='demo1')
   ... ''')
 
-Lets create a minimal `buildout.cfg` file:
+Lets create a minimal `buildout.cfg` file::
 
   >>> write('buildout.cfg',
   ... '''
@@ -107,7 +107,7 @@
   ... zcml = <include package="z3c.recipe.tests" file="extract.zcml" />"
   ... ''' % globals())
 
-Now, Let's run the buildout and see what we get:
+Now, Let's run the buildout and see what we get::
 
   >>> print system(join('bin', 'buildout')),
   Installing i18n.
@@ -116,7 +116,7 @@
   Generated script '/sample-buildout/bin/i18nmergeall'.
   Generated script '/sample-buildout/bin/i18nstats'.
 
-After running buildout, the bin folder contains the different i18n script:
+After running buildout, the bin folder contains the different i18n script::
 
   >>> ls('bin')
   -  buildout-script.py
@@ -132,14 +132,14 @@
 i18nextract
 -----------
 
-The i18nextract.py contains the following code:
+The i18nextract.py contains the following code::
 
   >>> cat('bin', 'i18nextract-script.py')
   <BLANKLINE>
   import sys
   sys.path[0:0] = [
   ...
-    ]
+   ]
   <BLANKLINE>
   import os
   sys.argv[0] = os.path.abspath(sys.argv[0])
@@ -154,7 +154,7 @@
 i18nmergeall
 ------------
 
-The i18nmergeall.py contains the following code:
+The i18nmergeall.py contains the following code::
 
   >>> cat('bin', 'i18nmergeall-script.py')
   #!C:\Python24\python.exe
@@ -172,7 +172,7 @@
 i18nstats
 ---------
 
-The i18nstats.py contains the following code:
+The i18nstats.py contains the following code::
 
   >>> cat('bin', 'i18nstats-script.py')
   #!C:\Python24\python.exe
@@ -191,7 +191,7 @@
 Full Sample
 -----------
 
-Lets create a `buildout.cfg` file using all available arguments:
+Lets create a `buildout.cfg` file using all available arguments::
 
   >>> write('buildout.cfg',
   ... '''
@@ -217,7 +217,7 @@
   ... environment = testenv
   ... ''' % globals())
 
-Now, Let's run the buildout and see what we get:
+Now, Let's run the buildout and see what we get::
 
   >>> print system(join('bin', 'buildout')),
   Uninstalling i18n.
@@ -227,7 +227,7 @@
   Generated script '/sample-buildout/bin/i18nmergeall'.
   Generated script '/sample-buildout/bin/i18nstats'.
 
-After running buildout, the bin folder contains the different i18n script:
+After running buildout, the bin folder contains the different i18n script::
 
   >>> ls('bin')
   -  buildout-script.py
@@ -243,7 +243,7 @@
 i18nextract
 -----------
 
-The i18nextract.py contains the following code:
+The i18nextract.py contains the following code::
 
   >>> cat('bin', 'i18nextract-script.py')
   <BLANKLINE>
@@ -266,7 +266,7 @@
 i18nmergeall
 ------------
 
-The i18nmergeall.py contains the following code:
+The i18nmergeall.py contains the following code::
 
   >>> cat('bin', 'i18nmergeall-script.py')
   #!C:\Python24\python.exe
@@ -284,7 +284,7 @@
 i18nstats
 ---------
 
-The i18nstats.py contains the following code:
+The i18nstats.py contains the following code::
 
   >>> cat('bin', 'i18nstats-script.py')
   #!C:\Python24\python.exe



More information about the Checkins mailing list