On Thu, 10 Sep 2015, David Matthews wrote:
The Windows-Unicode branch has now been merged into master. The
-DUNICODE -D_UNICODE options are automatically included in the Windows
build. There isn't currently a programmatic way to change the code-page
but I may add a function to do that.
On Mon, 7 Sep 2015, David Matthews wrote:
The experimental code is in the Windows-Unicode branch and requires
./configure CPPFLAGS="-DUNICODE -D_UNICODE"
to build the Unicode version. The resulting poly takes a --codepage option
to set the code-page to be used for conversion. Probably "utf8"
This was something that came out of a discussion with Makarius about
using the native Windows version with Isabelle but it's probably of
general interest to anyone who uses or might use the native Windows version.
The current master version uses the ANSI interface to Windows API calls
rather
IMHO, any move which get us closer to unicode everywhere is a good
move. Any discomfort this may cause in the immediate is well worth to
endure.
Cheers
On Mon, Sep 7, 2015 at 2:29 PM, David Matthews
wrote:
> This was something that came out of a discussion