Mercurial > babel > old > babel-test
comparison doc/catalogs.txt @ 83:6b6aa2f9e93d
Add unit tests for extracting translator comments from python sources.
| author | cmlenz |
|---|---|
| date | Sun, 10 Jun 2007 17:37:50 +0000 |
| parents | 1e89661e6b26 |
| children | 4ff9cc26c11b |
comparison
equal
deleted
inserted
replaced
| 82:0b5d604399b8 | 83:6b6aa2f9e93d |
|---|---|
| 183 :return: an iterator over ``(lineno, funcname, message, comments)`` | 183 :return: an iterator over ``(lineno, funcname, message, comments)`` |
| 184 tuples | 184 tuples |
| 185 :rtype: ``iterator`` | 185 :rtype: ``iterator`` |
| 186 """ | 186 """ |
| 187 | 187 |
| 188 .. note:: Any strings in the tuples produced by this function must be either | |
| 189 ``unicode`` objects, or ``str`` objects using plain ASCII characters. | |
| 190 That means that if sources contain strings using other encodings, it | |
| 191 is the job of the extractor implementation to do the decoding to | |
| 192 ``unicode`` objects. | |
| 193 | |
| 188 Next, you should register that function as an entry point. This requires your | 194 Next, you should register that function as an entry point. This requires your |
| 189 ``setup.py`` script to use `setuptools`_, and your package to be installed with | 195 ``setup.py`` script to use `setuptools`_, and your package to be installed with |
| 190 the necessary metadata. If that's taken care of, add something like the | 196 the necessary metadata. If that's taken care of, add something like the |
| 191 following to your ``setup.py`` script: | 197 following to your ``setup.py`` script: |
| 192 | 198 |