[drupal-devel] Internationalization, Usability and changes in
the coding conventions
carl_mcdade at yahoo.com
Sun Feb 20 08:05:47 UTC 2005
In english maybe it effects just usability but in cases like this I
don't think that usability and translation are exclusive of each other.
If you can't get good translation in a particular situation then it
effects usability immediately.
Use of message_access() is not wrong, but it is legacy it would seem. In
my opinion any opportunity to replace legacy code and make things
simplier should be taken. They don't come around often.
Gabor Hojtsy wrote:
>> According to Killes bug report the use of message_access is legacy
>> should not be there. Yet it is there in some core and contributed
>> modules. Shouldn't that be fixed? Even moving them up into the module
>> level from common.inc message() to t() would be a help in promoting
>> usability and translation.
> It is not an error to use message_access(), nor does it introduce
> translation problems as you tried to suggest. It does introduce
> useability problems in the sense that it does not provide the specific
> reasons for some failure.
More information about the drupal-devel