On Thu, Feb 12, 2015 at 11:08 AM, Peter Von Kaehne <ref...@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. >
I thought, from my discussions with Troy in the past, that this was the intended behavior - locale first, with English only as a fallback. But I don't know that it defaults to understanding "any valid prefix" under those rules. Perhaps you could throw some test cases into our test suite so that it's easy for someone to hack on this? It does sound like an unintentional behavior to me. --Greg > Or am I missing something? > > Frustratedly > > Peter > > _______________________________________________ > 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
