622565 - Improve autocomplete of non-ASCII text

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: Location Bar & Autocomplete, defect)

Description

[Stuart Morgan]

There are two things we should consider here:
1) Run keywords and queries through unicode canonicalization (we almost certainly should do this)
2) Strip keywords and queries of diacriticals. This would make, e.g., e match é. I believe this is how most searches in OS X work, so we probably should do it.

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Not sure if this is something we need and/or is easy enough for 2.1 or not.

I wonder if any of the l10n teams and their testers have noticed problems in this area while working with 2.1 milestones?

Comment 2

[Marcello Testi]

Not here. Trying to ping the mailing-list to have some feedback

Comment 3

[Marcello Testi]

I don't know if this should affect also URLs, anyway, I've tried adding a bookmark for some "José" (I put the name with diacritical into the bookmark title). Then typing in the location bar (Camino 2.1b1) "josé" (lowercase) worked, while "josè" and "jose" didn't. Of course "jos" worked as well.

While the behavior described in Morgan's point #2 would be optimal, I wouldn't assign a big priority to it. Others might think differently…

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

I'm a bit surprised (though pleasantly so) we haven't heard anything about this.  If it does pop up or l10n teams have heard about it and not yet mentioned it to us, we can renominate for 2.1.x.

Otherwise, I don't think it's on Stuart's agenda, and it's not likely to be something I can figure out.