From: Daniel Glassey (danglassey-abi@ntlworld.com)
Date: Fri Oct 10 2003 - 11:52:10 EDT
Just an update, it's still at an early stage with plenty of bugs (though
not many regressions from the ansi build that I can see) but I've put a
setup.exe at
http://www.crosswire.org/~dglassey/setup_abiword.exe
It now does unicode gui on non-win9x, win9x will continue to use the
system codepage and will probably get lots of '?' where it doesn't
recognise the char.
Since I don't have win9x it would be great if someone can try it out to
see how it goes. I don't expect it will have affected keyboard input on
win9x (it's still just as broken on winxp) but someone needs to check
before I can commit such a big change.
I'm now hopeful it should be possible to build ansi and unicode on the
same tree without loads of ifdefs so I'm going to try that and then post
more binaries before thinking about committing.
Daniel Glassey wrote:
> Hi,
> btw it isn't quite ready for it yet but in order to try and avoid
> regressions we will need testers on as many versions of windows as
> possible in different intl bits. (My win9x box has died so alas I can't
> do any checking on win9x so I need help with this).
>
> oh, and one more thing, once we have this working, I'd like to suggest
> that we make it that translations are _only_ to be in utf8 encoding (I
> think it will simplify things a lot on windows to be able to assume what
> encoding they are in) or would that cause problems on other platforms,
> or would it be a problem for translators?
ok, please ignore that, I hadn't looked far enough into the strings to
see that the stringset converts them to the default encoding anyway
which we can set to utf-8.
Regards,
Daniel
CVS Commit:
src/config/abi_defs.mk
src/config/platforms/win32.mk
nsis/Makefile.abi
src/wp/ap/main/win/Makefile
add _option_ to build windows version as unicode (it is not the default
yet, don't worry)
This archive was generated by hypermail 2.1.4 : Fri Oct 10 2003 - 12:11:57 EDT