5 ms·

> this bug "9001 Wrong Things Programmers Assume About Internationalization" This behavior should at a minimum be locale-aware. I would be surprised if Firefo

> this bug "9001 Wrong Things Programmers Assume About Internationalization" This behavior should at a minimum be locale-aware. I would be surprised if Firefox did that by default in my pt-BR profile.

chavesn 13y ago
(I'm not programming this kind of thing so please forgive my ignorance.) Is that loose of a search not actually desirable in "find in page" instances? In other words, are there many words where 'e' matching 'é' would actually generate a false positive? This is the only case I could see that would be problematic. And even then "find in page" is usually used as quick navigation to the minimum matching search (high recall) and not about excluding all possible mismatches (high precision).
- logicchains 13y ago
  There are words in other languages, French for instance, that with an accent changed or removed have completely different meaning.
  - bausson 13y ago
    That is sadly true. It's even worse than that. 'e' is the most used letter in french, but 'é' and 'è' are quite used too. 'ê' and 'ë' being rarer, but still existing. So, I am exaggerating it a bit, but you can compare it to having to search for words with the consonants, because every vowel is considered the same by your search algorithm. Yes, I'm pushing it, but you see the problem it can easily become in huge pages.
    - JetSpiegel 13y ago
      Why sadly?
      - bausson 13y ago
        What is sad for me is chrome new way of handling thing, not french accents (which can be a bother, but they're cute, so that's ok). Most pages nowadays are small enough that it won't be a bother, but their still are some cases (newspaper posts, blog analysis, etc...) where accent sensitiveness will be an issue.
ygra 13y ago
It should probably be aware to the language of the page, not your own.
- lmm 13y ago
  No, no, no. The user needs to be able to predict the behaviour.
  - deleted 13y ago
    [deleted]
    - lmm 13y ago
      "Nice things" like searching for "cafe" on page A, finding "café" and thus concluding that search works like that, then searching for "cafe" on page B, not finding anything, and then discovering that page B actually did say "café"?

chavesn 13y ago

(I'm not programming this kind of thing so please forgive my ignorance.) Is that loose of a search not actually desirable in "find in page" instances? In other words, are there many words where 'e' matching 'é' would actually generate a false positive? This is the only case I could see that would be problematic. And even then "find in page" is usually used as quick navigation to the minimum matching search (high recall) and not about excluding all possible mismatches (high precision).

logicchains 13y ago
There are words in other languages, French for instance, that with an accent changed or removed have completely different meaning.
- bausson 13y ago
  That is sadly true. It's even worse than that. 'e' is the most used letter in french, but 'é' and 'è' are quite used too. 'ê' and 'ë' being rarer, but still existing. So, I am exaggerating it a bit, but you can compare it to having to search for words with the consonants, because every vowel is considered the same by your search algorithm. Yes, I'm pushing it, but you see the problem it can easily become in huge pages.
  - JetSpiegel 13y ago
    Why sadly?
    - bausson 13y ago
      What is sad for me is chrome new way of handling thing, not french accents (which can be a bother, but they're cute, so that's ok). Most pages nowadays are small enough that it won't be a bother, but their still are some cases (newspaper posts, blog analysis, etc...) where accent sensitiveness will be an issue.

ygra 13y ago

It should probably be aware to the language of the page, not your own.

lmm 13y ago
No, no, no. The user needs to be able to predict the behaviour.
- deleted 13y ago
  [deleted]
  - lmm 13y ago
    "Nice things" like searching for "cafe" on page A, finding "café" and thus concluding that search works like that, then searching for "cafe" on page B, not finding anything, and then discovering that page B actually did say "café"?