DEPRECATION WARNING: ActiveSupport::Multibyte::Chars#normalize is deprecated and will be removed from Rails 6.1. Use #unicode_normalize(:nfc) instead.

[GhennadiiMir]

Looks like it's easy to fix, let me know if it's better that I'll create a PR for this.

[mrstif]

@GhennadiiMir you can target branch v2.0 which already fixes this issue but hasn't been released yet...

[jrochkind]

Is a release anticipated anytime soon? Are there active maintainer(s) of this gem?

[mrstif]

hard to say @jrochkind ...
if v2.0 hasn't been released in 7 years, it probably means that it won't be released anytime soon either...

unless @norman has something to say about that

[norman]

Hello! I haven't used or maintained this library in ages. I think it is conceptually wrong for the most part, as described in the README. If you want transliteration you can use Babosa, or i18n which provide context-sensitive transliteration for many languages. You can also using Stringex, which this library was extracted from. I really see no need to use this library any more.

[norman]

That said if anybody disagrees and DOES wish to maintain this I would be happy to pass off ownership.

[jrochkind]

Oh yeah, i forgot i18n can do this too!

While I agree it's conceptually wrong, sometimes it's still useful. :)

It's not super well-documented in the i18n gem, if anyone else gets here and wonders, it's as easy as:

I18n.transliterate("Ærøskøbing")
# => "AEroskobing"

Won't necessarily have exactly the same behavior as the mappings here, but it's gonna be a conceptually leaky approximation either way, so.

@norman thanks for the response! Since apparently some people are still using this (as evidenced by a 4-day-old issue filed!), it might be helpful to just add something to the README saying the gem is no longer being maintained.

[norman]

it might be helpful to just add something to the README saying the gem is no longer being maintained.

Ok, will do!