In my ongoing attempt to try to get the .po extraction fixes into Drupal and let the whole framework be compatible with .po extraction, here is another piece. These are quite straightforward changes (except that I had no idea of whether I should rely on that the $taxonomy->multiple property will always be a 0/1 integer, so I converted it into an int as needed).

Tested, and seem to work on my local CVS copy of Drupal.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Gábor Hojtsy’s picture

Category: drupal » 5567
FileSize
10 KB

More fixes:

 - some cleanup for locale.module's help
 - fixing t() issues in forum.module and statistics.module
 - previous taxonomy patch also included, so it can be
   reviewed / applied in one pass

Since these are also quite simple patches, I don't think there will be any opposition against them... And they raise the level of .po awareness in Drupal :)

Gábor Hojtsy’s picture

Title: Translation issues in taxonomy.module » Translation issues in various modules
Component: taxonomy.module » other
Category: 5567 » bug

Doh, followups are not posted to the ML if 'Category' is not set, and 'Category' could be set to '<none>'... So bringing this bug to attention with specifying a category :)

Dries’s picture

Committed to HEAD. Thanks again. I've made a couple of small changes: I deleted some redundant break statements, replaced some double quotes by single quotes, etc.

Anonymous’s picture