Iain Beeston

At present it only supports US English, but internationalisation is something I'd love to implement. I have no firm plans yet though, I'm afraid

I think internationalising the gem will take a lot of work and major restructuring. The main classes that would need to change would be query.rb and query_constants.rb, but there is...

I appreciate that you're keen to help internationalise the gem and I'll try to prioritise internationalisation, but there are structural issues I'd like to resolve first that will make it...

I'm planning on moving a lot of the English language substitutions out to yaml files in a future release. That should make it easier to translate, although I suspect more...

I'm planning on making each translation an independent gem, such that when the gem is loaded it registers itself with nickel, and then nickel can be switched to use any...

Sorry, it's rather difficult to fix individual issues in nickel at the moment. I have a refactor in the works, which will help (and also allow users to supplement nickel...

I've found this too. My solution is to import the swiper css from a CDN in my `application.tailwind.css`, like this: `@import url('https://cdn.jsdelivr.net/npm/swiper@8/swiper-bundle.min.css');` (note that it uses swiper version 8 because...

There is already the inflections gem (by @davidcelis) but I think multilingual inflections support aught to come "out-of-the-box" with rails-18n, and including inflections here might encourage people to contribute inflections...

@RST-J Could I please get a review of this too?

@RST-J No problem, I understand completely (sorry for spamming you with requests!)