-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request - install unaccent #4783
Comments
Using non-ASCII characters is nice BUT in every csv download, they come out crazy in Excel (which is how a lot of us will open them). I found this solution
And I am wondering if we can get downloads in ANSI format for Excel? In other words, could we have choices in the format of downloaded data? |
There are two possible ways in which UTF-encoded data may be represented:
Allowing a user to input "slaskie" and find data for Śląskie is potentially helpful (typing Turning Śląskie into slaskie for download just sounds like a dirty trick to me. Now they've got some irreversible mess which doesn't match anything they can find anywhere and cannot be converted back to anything which does. Not a great place to find oneself! Even if there was some defensible path to that sort of thing, |
You can just say no. |
Tabling; might be reconsidered in context of #6524 |
Is your feature request related to a problem? Please describe.
It's occasionally useful to ignore accents and diacritics and such.
Describe what you're trying to accomplish
#2874, but this could be useful for lots of searches, perhaps could even allow relaxing some rules.
Describe the solution you'd like
Install https://www.postgresql.org/docs/current/unaccent.html, build stuff (probably mostly trigram indexes) to use it
Describe alternatives you've considered
Additional context
Needs coordinated with @lkvoong re backups/copies.
Priority
This would be new functionality, I don't have time to dive in at the moment, the really cool possibilities would take some time to develop, probably relatively low.
The text was updated successfully, but these errors were encountered: