Re: [development] t() function concept/bug/patch proposal

In summary - the current concept of t() is officially that it only supports fixed, module defined strings, not 'user-defined' (which means anything else, e.g., a title, a taxonomy term, etc.). In particular, when given an empty string as an argument, it wastes an expensive sql lookup (and really bombs if those are in an init function before the db caching is started).

i support that ... one way to move this along is to make a patch (it is really simple) and get it reviewed and into the cvs commit queue. then a decision is needed. otherwise, you are seeking a policy change with no effects and that merits little time.