ColaCheng
Hi all,
I have made an unicode tr39 confusable detection and skeleton implementation, ex_confusables
This library is able to compare two strings if they are visually confusable as described in Unicode® Technical Standard #39: Both strings get transformed into a skeleton format before comparing them. The skeleton is generated by normalizing the string (NFD), replacing confusable characters, and normalizing the string again.
Also did some profiling between char list and binary string implementation. The interesting part is char list is faster than binary. The result is here.
Feel free to open any issues you encounter in the Github repo and try it!
Thank you!
Where Next?
Trending in Announcing
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Exadra37
Thanks for sharing this library with us
Why did you prefixed the library name with
ex_?If I am not in mistake this prefix is normally used when a library is extending/wrapping Elixir core functionality, but I may be wrong.
ColaCheng
I don’t know this rule. I just came out this name because it implement in Elixir. Good to know this convention! Thank you!
John-Goff
Where did you get this idea from? A quick search on hex.pm shows that if this is a convention, it’s poorly followed: Packages | Hex
Exadra37
I ready it several times in this forum, but cannot find a reference to it now.
Maybe @AstonJ can help here.
Yes, you have a lot of misuse of it.
John-Goff
I think my point is that a convention is only a convention if it is followed. In this case it does not appear to be, so I would say there is no naming convention that is widely used by the community.
AstonJ
I am not aware of such a convention (and the Hex or Elixir core teams may be better people to ask) however I do have some ideas about naming (related to another topic). Hopefully I will get a chance to post about it at some point
Exadra37
I have not found a reference to my assumption in the forum yet, but I know that I read something about the use of “ex_” for library names and I think it was from Jose Valim itself, but probably I am mistaken in saying that was from him and on my affirmation, because I found this article:
https://medium.com/@toddresudek/hex-power-user-deb608e60935
Sorry for my confusion in saying: