Closed (fixed)
Project:
Translation template extractor
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Jun 2007 at 19:36 UTC
Updated:
11 Jul 2007 at 17:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
hass commentedhere is a patch for this bug.
Aside what about "project"? shouldn't we unset this, too?
Comment #2
gábor hojtsyIs datestamp a valid key for the .info files? We might be better off with defining a whitelist of strings to use as the .info file keys proliferate in Drupal 6.
Project is displayed on the module grouping fieldsets on the modules page, so they are subject of translation.
Comment #3
hass commentedyes, "datestamp" is a new valid key. It will be added for "update_status" module by build system since... mid April / May?
Comment #4
hass commentedi learned about another allowed key named "update status url"... we should definitively create a white list! this is much easier to maintain
Comment #5
gábor hojtsyOK, can you help collect a whitelist? The most obvious ones are: 'name', 'description' and 'package'. Are there any other keys used, which should be translatable?
Comment #6
hass commentedYour list sounds ok, but i'm not sure about "package"...
Comment #7
gábor hojtsyPackage names are displayed with t(), see line 1837 of system.module (Drupal 6.x-dev). I committed a simple whitelist with these three values. Let me know if you have any other issues with potx, I hope we rectified all problems you encountered so far. Thanks for your rigorous reviews and fix suggestions!
Comment #8
(not verified) commented