On 6/19/07, Gabor Hojtsy gabor@hojtsy.hu wrote:
Cog Rusty wrote:
...snip...
On the other hand, sometimes a string same as a module's name appears in a menu, which we would like to translate. The current absence of a t() in the module names which appear in "/admin/build/modules" is a good thing because it allows us to translate a module name everywhere else if we want to.
Allows us? How does it allow us?
I mean you can translate an identical string which appears in a menu, and the module name itself in /admin/build/modules can remain unaffected.
BTW I am not against putting the original module name to a visible place. Module names and module file names are already not in concert, lots of them use abbreviations or expanded names. Like core has translation.module which is named "Content translation". With the multiple directories where modules can reside (and given you don't know the file name for sure) also makes hard to find a module on your own installation for starters, not even reaching to a project page.
To help this situation, we can put a 'title="'. t('Original module name: %name, location: %path', array('%name' => $name, '%path' => $path)) . '"' onto the module list items for example (and let the module names be translated).
This could work. In the meanwhile I posted a reply to the issue (http://drupal.org/node/152375) where I try to visualize this in practice.
Gabor