[Monetdb-developers] [Monetdb-checkins] MonetDB5/src/mal mal_authorize.mx, , 1.73, 1.74 mal_client.mx, , 1.195, 1.196 mal_debugger.mx, , 1.263, 1.264 mal_exception.mx, , 1.54, 1.55 mal_factory.mx, , 1.87, 1.88 mal_interpreter.mx, , 1.302, 1.303 mal_linker.mx, , 1.110, 1.111 mal_profiler.mx, , 1.128, 1.129 mal_sabaoth.mx, , 1.53, 1.54 mal_scenario.mx, , 1.123, 1.124 mal_session.mx, , 1.195, 1.196

Fabian Groffen Fabian.Groffen at cwi.nl
Sat May 16 22:55:11 CEST 2009


On 16-05-2009 22:49:17 +0200, Martin Kersten wrote:
> Fabian Groffen wrote:
> > On 16-05-2009 22:28:29 +0200, Martin Kersten wrote:
> >>> Why not do it the gettext way, in that case?
> >> Yes, i am fully aware of gettext.
> >> It is a multi-step process, first condense.....
> >> and gettext() performs translations based on strings
> >> e.g. the ones now identified.
> > 
> > So after gettext you have to reverse this step again...
> no, gettext performs a string-based lookup only.
> There is no requirement that this should be an abbreviated one

_("the string that is translated")

Point was, readability and less obfuscation.

> > Perhaps this is *not* a good thing to throw in just before a code freeze?
> Yes, a concerted check on error messages is needed.
> There are a limited number of changes

Another thing, if you need the same message a lot of times, you can
probably be more specific to *improve* your error messages.




More information about the developers-list mailing list