| 37 | | add lines to `setup.cfg`, or if it doesn't exist, create it |
| 38 | | This will tell the translation helper programs where to look and store message catalog files. Since this is a per plugin translation, you need to customize the code to the plugins name wherever it reads `foo` in the example. |
| | 35 | Add some lines to `setup.cfg` or, if it doesn't exist by now, create it with the following content: |
| | 36 | {{{ |
| | 37 | [extract_messages] |
| | 38 | add_comments = TRANSLATOR: |
| | 39 | msgid_bugs_address = |
| | 40 | output_file = foo/locale/messages.pot |
| | 41 | keywords = _ ngettext:1,2 N_ tag_ |
| | 42 | width = 72 |
| | 43 | |
| | 44 | [init_catalog] |
| | 45 | input_file = foo/locale/messages.pot |
| | 46 | output_dir = foo/locale |
| | 47 | domain = foo |
| | 48 | |
| | 49 | [compile_catalog] |
| | 50 | directory = foo/locale |
| | 51 | domain = foo |
| | 52 | |
| | 53 | [update_catalog] |
| | 54 | input_file = foo/locale/messages.pot |
| | 55 | output_dir = foo/locale |
| | 56 | domain = foo |
| | 57 | }}} |
| | 58 | This will tell the translation helper programs where to look for and store message catalog files. Since this is a per plugin translation you need to change wherever it reads `foo` in the example to the existing plugin directory that is a short form of plugin's name in most cases. |
| | 59 | |
| | 60 | In the `extract_messages` section there are other lines you may like to change. Starting with `add_comments` there is the place to announce yourself as the translator by adding your name after the default `TRANSLATOR:` label. To allow for direct feedback regarding your translation add a valid e-mail address or a mailing list dedicated to translation issues to `msgid_bugs_address`. |
