a lot of time. Also, I don't present the user with some useless and annoying error number as if I were writing a program for Windows 95 ... Remember, the *Nix philosophy is toI dont think function names mean anything more to the user than error codes really.
assume that the user is intelligent and knows what he or she is doing. So let's present
the user with intelligent and useful information, not useless error codes!
If a programming language allows non-ascii identifiers, such as perl for example,
we must assume the programmer to be sufficiently versant in the human and
computer languages of the codebase. We cannot assume the same of the users.
The main point is that there be a non-localized part which is useful to the programmer,
and a localized part which is useful to the user.
The localized part can make the user realize that what went wrong might be his fault,
or how to fix/avoid/workaround the problem. The invariant part is what the user might
user to search for help or report problems to a programmer who perhaps doesnt speak
the same language he does.
It helps if the invariant part makes a good search key: Its alot harder to find the right
hits for "GetToken" than for something like "Application: GetToken-LexAn-ErrUnrec".
(Not only that, but in bigger functions there may be some value in knowing where
in the function you hit the error without relying upon the localizable portion.)
-- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
