From: Dom Lachowicz (domlachowicz@yahoo.com)
Date: Wed Jul 23 2003 - 09:38:51 EDT
Hi Raphael,
--- Raphael Finkel <raphael@cs.uky.edu> wrote:
> The most important blockers, in my view, for the
> Win32 build are 4754
> and 1314. Together, they make the Win32 build
> unusable for many
> languages. 4754 is the bug that prevents non-Ascii
> characters from
> appearing on menus, making internationalization
> worthless. 1314 is the
> bug that prevents WM_UNICHAR keyboard input from
> being accepted, making
> it impossible to enter non-Ascii characters into
> text. If these could
> be fixed, I would finally be able to recommend
> AbiWord to the
> Yiddish-writing community.
We did attempt to address this problem, but
ultimately, we gave up on it for the 2.0 timeframe.
Basically, the correct solution involves using the
unicows.dll from Microsoft to emulate UNICODE input
and output on non-NT platforms (95,98,ME). This is the
only correct solution to this problem, as far as I'm
concerned.
2.0 will work no better, nor no worse for these kinds
of users. It's unfortunate, but it's also a fact of
life.
We hope to have AbiWord 2.2 using unicows.dll so that
we can use true unicode support for all of our input
and output on Win32. Right now, it's too close to 2.0
to even consider such a thing.
I personally would'nt blame us. I'd blame MSFT for
shipping "broken" APIs for the past 9 years or so. But
that's just me.
Best regards,
Dom
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
This archive was generated by hypermail 2.1.4 : Wed Jul 23 2003 - 09:52:59 EDT