Implementing message translation is not that hard. I've already done a lot of
preliminary work in places such as make-msgfile.lex in lib-src/. Finishing up
the work is not that big a task; I already know exactly how it should be
done. Perhaps I'll write up detailed design instructions for this, as I'm
doing for other things. A lot depends on priority: How important do you think
this issue is to your average Japanese/Chinese/etc. user? How does it compare
to some of the other important Mule issues that Martin and I are (trying to
work) on? If I did the design document, would you be willing to do the
necessary bit of C hackery to implement the document? If the design document
is not specific enough for you, I can give you an "implementation document"
which will definitely be specific enough: i.e. I'll show you exactly where the
code needs to be modified, and how. The big question is, would you be willing
to help do the actual implementation, to "be my hands"?
"Stephen J. Turnbull" wrote:
>>>>> "Ben" == Ben Wing <ben(a)666.com>
Ben> If you want to be more adventurous, I'd suggest some more
Ben> general changes to make these type errors clearer. I've
Ben> always hated these. For example:
I've always hated them, too. But I have on occasion written code to
parse the *Messages* buffer for these error messages; somebody may
actually haved saved some code that does that. Somehow this should be
BLUE SKY ALERT: Some day these things should be gettext-ized anyway.
Lots of Japanese don't understand that message no matter how good the
English is ;-) We should think about how the message catalogs should
be done; can we really use gettext? Do we want multilingual
capabilities (same process using multiple languages---I have been in
the situation of trying to figure out Japanese errors from Mule code
and would love to have that capability when the catalogs are
available, but it's probably hard to do).
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
In order to save my hands, I am cutting back on my responses, especially
to XEmacs-related mail. You _will_ get a response, but please be patient.
If you need an immediate response and it is not apparent in your message,
please say so. Thanks for your understanding.