Re: [sword-devel] wcharToUTF8 not yet coded

2013-09-15 Thread Troy A. Griffitts
Thanks for testing and for the report about ftplibftpt.cpp. I hadn't tried a non-curl build, but should have. Committed your fix. Thank you! On 09/15/2013 06:02 PM, John Austin wrote: I just checked the implementation with xulsword and it works great in Linux. Search results for modules with

Re: [sword-devel] wcharToUTF8 not yet coded

2013-09-15 Thread John Austin
I just checked the implementation with xulsword and it works great in Linux. Search results for modules with non-Latin keys are returning correct results now. I'm glad that the code was handy. I did find that the recent change to ftplibftpt.cpp caused this compiler error with gcc 4.6.3: make

Re: [sword-devel] wcharToUTF8 not yet coded

2013-09-14 Thread Troy A. Griffitts
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 c

Re: [sword-devel] wcharToUTF8 not yet coded

2013-09-14 Thread Jeff Barnes
Sent from my iPhone On Sep 14, 2013, at 1: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 utilst

[sword-devel] wcharToUTF8 not yet coded

2013-09-13 Thread John Austin
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 log