Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Search should be accent insensitive (SYN-666) #1523

Open
matrixbot opened this issue Mar 29, 2016 · 3 comments
Open

Search should be accent insensitive (SYN-666) #1523

matrixbot opened this issue Mar 29, 2016 · 3 comments
Labels
A-I18n A-Message-Search Searching messages T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.

Comments

@matrixbot
Copy link
Member

(Imported from https://matrix.org/jira/browse/SYN-666)

(Reported by @manuroe)

@matrixbot
Copy link
Member Author

Jira watchers: @manuroe

@matrixbot matrixbot changed the title Search should be accent insensitive (SYN-666) Search should be accent insensitive (https://github.com/matrix-org/synapse/issues/1523) Nov 7, 2016
@matrixbot matrixbot changed the title Search should be accent insensitive (https://github.com/matrix-org/synapse/issues/1523) Search should be accent insensitive (SYN-666) Nov 7, 2016
@jdauphant
Copy link

Any news on that ?

@erikjohnston erikjohnston added the T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements. label Jul 26, 2021
@squahtx squahtx added the A-I18n label Sep 6, 2022
@MadLittleMods MadLittleMods added the A-Message-Search Searching messages label Sep 6, 2022
@squahtx
Copy link
Contributor

squahtx commented Sep 7, 2022

http://www.unicode.org/reports/tr10/#Asymmetric_Search sounds like a useful property for whatever we end up implementing to have. ie. Leon should match both Leon and Léon, whereas Léon will only match Léon.

libicu has an implementation of it (https://unicode-org.github.io/icu/userguide/collation/string-search.html) but it's not clear whether it's possible to get it working with postgres.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-I18n A-Message-Search Searching messages T-Enhancement New features, changes in functionality, improvements in performance, or user-facing enhancements.
Projects
None yet
Development

No branches or pull requests

5 participants