Dear John, thanks for the report.
Dear Jeff, thanks for the suggestion.
Looking through our code we had an old swunicod.[h,cpp] unit sitting
around which had a method to convert from UTF32 to UTF8. This unit was
only used in one obscure filter (RTFHTML). I've removed this unit and
moved the code over as the implementation of the empty method which John
pointed out.
I didn't evaluate the logic of the actual implementation. I am going
off the assumption that it worked :) If we have any troubles with it
(John could you test your use case), then we can change the
implementation to use Jeff's suggestion.
Troy
On 09/14/2013 07:18 AM, John Austin wrote:
I've been testing the latest SWORD code for some time now, with
xulsword, on both Windows and Linux, and it's working great. But I did
just discover that Lucene searches in some non-versekey modules fail
because utilstr.cpp's wcharToUTF8() has not yet been coded. It's got
"TODO: finish this logic" in the code. So search returns incorrect
results in some modules (non-Latin dictionary and general book
modules). Maybe somebody's got a quick solution? Sorry to post another
issue so late- but I just discovered the problem yesterday and figured
it's better to mention it than not to.
But other than this, xulsword has been working very happily without
issue using SWORD 1.7, which is terrific. A new version of xulsword is
also to be released soon.
-John
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
