The dictionary keys are stored in in uppercase if language-applicable. So when you search for Aaron, the lexicon driver algo does a binary search for AARON. If its toupper fails, then a logical binary search for Aaron would effectively produce Baal, (a > Z) so Aaron would logically be filed after AZUTHUTH, and before BAAL.

We now provide a way for non-ICU builds of sword to supply to toupper function that sword uses. The Bibletime guys do this with a Qt call. That way, they still get real UTF-8 toupper calls, without the need to include ICU.

We probably broke the non-ICU/non-supplied toupper code. I'll have a look at it soon. (or Joachim could see why the old logic isn't getting called in this configuration (hint-wink).

Hope this give you some idea of where we're broken,

        -Troy.



William Thimbleby wrote:
Troy, I'm using the non-ICU version. I could call toupper but I don't at the moment and I'm not sure what it has to do with the problem.

On 17 May 2004, at 08:15, Troy A. Griffitts wrote:

William,
We've changed some code recently that handles 'toupper' functions so that we better support i18n. I would guess that your configuration needs us to do some bugfixing. What config are you using? (ICU/no-ICU). Does your windowing framework support any kind of simple UTF8 toupper string function-- there is an easy way to supply a utf8_toupper call if you have one available and don't wish to include the entire ICU dependency.


    -Troy.



William Thimbleby wrote:

Hi,
I seem to have a problem with the cvs version and selecting contents from dictionaries. A key always seems to jump to the next key that starts with a different initial letter. (eg. Aaron, Attus, Aziel -> Baal (1), Baal(1) -> Cab... in ISBE) this doesn't happen with numbers, such as the strongs dictionaries.
Is this a bug? or something I have to fix?
--thanks
Will
_______________________________________________
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire.org/mailman/listinfo/sword-devel


_______________________________________________
sword-devel mailing list
[EMAIL PROTECTED]
http://www.crosswire.org/mailman/listinfo/sword-devel


_______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel

_______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel

Reply via email to