[sword-devel] reference parser - yet another bug?

[DM Smith]

JSword had this problem but in the last few days a patch was provided to fix the problem. It helps tremendously, but it is a bandaid.

How JSword does thing is different, but the problem was the same.
There are two different kinds of book names, exact and fuzzy.
An exact match is from a limited dictionary of names.
A fuzzy match is an attempt to find a book name when there isn't an exact match.

When you've got controlled input (i.e. a module) it should look references only based upon that language and exhausting all possibilities (exact then fuzzy) then possibly falling back to English.

-- DM

> On Feb 12, 2015, at 12:08 PM, Peter Von Kaehne <refdoc at gmx.net> wrote:
> 
> Romanian for "Judges" is "Judecatori". Romanian for "Jude" is Iuda.
> 
> So "Ju", "Jud", "Jude", probably even "J" should only ever be understood as "Judecatori".
> 
> But alas, the parser, uses English abbreviations to override at certain and not entirely predictable places. 
> 
> So, Jude will be translated into Jude despite being a valid abbreviation for Judges in the Romanian locale
> 
> If I now add "Jude=Judg" to the locale, I can fix that - but I get the same problem at "Jud". Why? Do I need to disable every single abbreviation which could be read as something in English? Our locale will probably need a massive overhaul if this is desired behaviour.
> 
> I personally think once I changed my locale into a non-English one no other "default" locale should interfere - or at the very least it should function only as a fallback if there is no possible "first locale" interpretation. 
> 
> Or am I missing something?
> 
> Frustratedly
> 
> Peter
> 
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page