According to Marjolein Katsma:
> However, ht://Dig is used in other language environments than just English.
> Being able to do *compile time* configuration (without having to dig into
> the code to find just where and how this error screen is coded) for such an
> error screen so it could at least speak the end-user's language would be
> *very* useful.
My point was that on a properly set up system, the end-user should never
see that error message - the most rudimentary testing by the person setting
up ht://Dig should flush out any of these error conditions. Geoff brought
up a point that I wasn't aware of - older versions of htsearch didn't fall
back to the default config file if the user/form specified config file was
null. That did open the door to possible user error causing this message,
though most likely an error in a search form would have been the cause.
That shouldn't happen in the current version.
I agree that multi-language support is important, but without major changes
to the code, and translation of all the documentation, I don't think a non-
English speaking person would be able to set up and configure ht://Dig
anyway.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
----------------------------------------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the body of the message.
