Someone missed to setup unix file encoding on his box and this has been commited...
msgid "<p>Properly categorizing your project will help ensure that users can find it easily. Please follow these steps:</p>\r\n <ul>\r\n <li>Select <em>one</em> of the first-level terms (%types) as the project type.</li>\r\n <li>Then choose <em>one or more</em> categories below this term to classify your project. For example, for %type, you would choose from the various %type types: %categories, and so on.</li>\r\n </ul>"
msgid "<p>The project module makes special use of the taxonomy (category) system. A special vocabulary, %vocabulary_name, has been created automatically.</p>\r\n <p>To take full advantage of project categorization, add at least two levels of terms to this vocabulary. The first level will be the basic project types, e.g., \"modules\", \"themes\", \"translations\".</p>\r\n <p>Subterms of each of these types will be the categories that users can select to classify the projects. For example, \"modules\" might have sub-terms including \"mail\" and \"XML\".</p>\r\n <p>Use the <a href=\"!taxonomy-admin\">vocabulary admin page</a> to view and add terms.</p>"
Patch follows...
Comments
Comment #1
hass commentedHere is the patch...
Aside Gabor said something about not using multiline strings... see http://drupal.org/node/144951
Comment #2
dwwthe pot files for project are ancient, and just need to be regenerated completely, not patched. and yeah, there are probably a ton of t()-related errors. patches for those are most welcome.
Comment #3
hass commentedI cannot create an error free POT without the above patch! therefor i fixed the modules code (the patch above), regenerated the POT and committed the complete POT for the patched version. The latest POT is up-to-date, some hours old - no more.
Comment #4
hass commentedComment #5
hass commentedmoved into patch http://drupal.org/node/155727