[sword-devel] Windows Unicode woes
greg.hellings at gmail.com
Mon Apr 15 13:30:57 MST 2013
I have hacked and hacked at this. I seem to have something working. If
people who use Xiphos can test it out with
http://dl.thehellings.com/xiphos-3.1.5-win32-sword-patch.exe (this will
look a bit uglier than you might be used to as I have built it with an
unstyled GTK+3 interface rather than the more familiar styled GTK+2 you're
used to in Windows builds of Xiphos)
while people with a love of the command line can test it out by downloading
the latest sword-utils from
that suit your fancy.
Anyone who wants to see my code can find it on github at
http://github.com/greg-hellings/sword in the util_open branch. Testing on
Linux/Unix/Mac would also be appreciated. I have done a cursory test on all
the major operating systems and I don't appear to have broken basic
Testing with paths - especially on Windows - which include non-Unicode
characters would be greatly appreciated. If I get positive feedback on the
behavior of these test binaries I'll make the patch up nice and proper and
submit it in its final form.
The only odd behavior I've noticed is there seems to be occasional
performance pauses while performing file operations. I'm not sure if I'm
just imaginging that or if my patch has occasional performance impacts.
I've also been testing in a VM, so it's entirely possible that I was just
seeing variable system load messing with it.
Please - any feedback, even "it worked for me" and "me too" (or "not for
me") would be most appreciated.
On Wed, Feb 6, 2013 at 8:41 AM, Greg Hellings <greg.hellings at gmail.com>wrote:
> I began porting the GLib wrapper functions for open, mkdir, access, etc
> and stripping out the dependence on Glib-specific functions in order to
> work around the engine's woes with Windows Unicode paths. I filed an API
> bug for it and attached the patch I have so far. It's by no means complete
> and I haven't had the opportunity to test my results on Windows but at
> least it's something.
> A brief look through the bug tracker shows 57 issues that are open against
> the API project. Some of these I know are already resolved but are pending
> 1.7.0 release. Others have patches attached but have gone without comment
> or addressing.
> I don't have permissions to do anything about those which are resolved and
> several of those with attached patches I don't have permission to commit
> into the engine. Are any of these bugs the ones still holding up 1.7.0?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel