1042681 - Recipient autocomplete and AB (quick) searches should be less sensitive about accented local characters ("bar" should match "bàr"): use .localeCompare(... { sensitivity: 'base' })

Status: UNCONFIRMED

(Thunderbird :: Message Compose Window, enhancement)

Description

[Ordim.info]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140722064054

Steps to reproduce:

add a contact name Loïc
then try autocompletion with loic 



Actual results:

no matching result


Expected results:

it should match  Loïc

Comment 1

[:aceman]

Have you confirmed that the capital L is preventing the match?
It looks to me the problem could be the special accented i, that you do not have in your search string.

Comment 2

[Ordim.info]

Sorry my first message was quite ambiguous.
it is the spécial accented i ->  ï 
same thing with ô œ  etc etc

Comment 3

[:aceman]

This seems to work fine for me. I put "Loïc" as Last name of a contact.
I can find it (via autocomplete in composer) using loïc and also oïc . That is on TB34, Win XP. I am not sure anything relevant was changed here between TB31 and 34.

Comment 4

[Ordim.info]

Attachment: thunderbird.png

Hi 
As you can see it does not match. 
Archlinux 64 up to date > thunderbird 31.0-1
going to try on another system.

Comment 5

[:aceman]

I do not see any autocompletion in the screenshot. At least not the one in the compose window.
I just see search inside the address book. And "pa with roof" properly matches the contact you created. Why should "pa" match "pa with roof" ? Those do not seem to be the same character.

Comment 6

[Ordim.info]

autocompletion in message compose window is the same. not matching.
I do agree it is not the same character with or without roof... but it usually happen that people does not use roof or special accent as they should. 
Using specials accent need to press additionnal keys.
At least maybe some option to match or not specials accents could be introduced ?

Comment 7

[:aceman]

Ok, so from the features described on the page at https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/localeCompare you actually want the "sensitivity=base" option?

Comment 8

[Ordim.info]

Yes absolutely.

Comment 9

[Thomas D. (:thomas8)]

Aceman, any reasons NOT to use sensitivity: 'base'?
Could this cause havoc (too many results) for specific locales?

If this isn't implemented yet, it sounds good to me (could be confirmed as an RFE)...

Comment 10

[Thomas D. (:thomas8)]

Although, looking at my own locale, is it really desirable that
"Hocker" finds "Höcker"? Different words, and both exist...
Would have to check further how this affects name searches on each locale...

Comment 11

[:aceman]

1. I am not sure if that .localeCompare() functionality is already supported in TB. I rememeber it needed to include some special international support library and that one was just coming to Firefox yet.
2. the AB search actually descends into c++ code to search matching cards. I really doubt that backend supports these special character features.

Comment 12

[Magnus Melin [:mkmelin]]

Re 1: INTL_API is enabled in thunderbird nowadays

Comment 13

[Magnus Melin [:mkmelin]]

Though for the actual feature, I don't know. For Finnish and Swedish it's not desirable to have å or ä mach a, or ä to match a. (Not sure if that would be the case though).

Comment 14

[Magnus Melin [:mkmelin]]

en ö to match o.

Comment 15

[Thomas D. (:thomas8)]

(In reply to Magnus Melin from comment #13)
> Though for the actual feature, I don't know. For Finnish and Swedish it's
> not desirable to have å or ä mach a, or ä to match a. (Not sure if that
> would be the case though).

Not sure either, but the more interesting usecase is the other way round:
Type "a" to match å or ä...

Comment 16

[Wayne Mery (:wsmwk)]

Citing some related bugs.  I didn't include bug 730945 - doe sthat even exist anymore?

Comment 18

[Bruno G.]

As someone who deals with French named contacts a lot, this should definitely be listed as a bug not an enhancement... It is frustrating to have to type accented characters for recipients to autocomplete.

Comment 19

[Mirza Hadžič]

1. Can confirm, very annoying and non-standard behavior. Used to enter "Boz" and enter for "Božena", but here nothing happens.
2. Deleting char (in this case "Boz" -> "Bo") wouldn't give you "Božena" either, because for some reason autocomplete is only after new character at the end of the input string, not after any other edits, like delete for example. Also very annoying.