Pagy::Frontend::I18N.load_file Error about pagy HOT 8 CLOSED

Updated the CHANGELOG (1f3087b)

from pagy.

Thanks for the explanation. Then it looks like you are using the i18n extra... and I just understood that my doc is not clear enough then :).

I will update also the initializer_example.rb to make it more clear.

You don't need that 2 lines if you use the i18n extra, because your app is using the canonical I18n gem included as a dependency of rails, hence that 2 lines are totally ignored by the I18n gem.

from pagy.

Hi @msdundar
sorry for the issue, but there have been some simple to fix breaking changes in version 0.11.0. Please, follow the CHANGELOG link to update. Please, let me know if I can help.

Besides, I just noticed that the CHANGELOG missed to report to update also the initializer file. I will fix the CHANGELOG.

Thanks

from pagy.

@msdundar
I saw that you are using a custom language. The new Pagy version has been refactored in order to better support custom i18n, especially with regard to multiple languages and relative pluralization.

If the file you are using is generic (i.e. suitable for general use), then you could add your language to the bottom of the pagy.yml file and create a pull request. ;)

If your language doesn't use the same "en" default pluralization types (i.e. 'zero', 'one', 'other'), you should also add a proc in the plurals.rb, so it will be properly pluralized by pagy i18n.

Please, let me know if I can help. Thanks

from pagy.

Thanks for your quick reply, detailed explanation and update on CHANGELOG.

I will make a PR for translations soon. My issue is fixed, after changing the initializer as shown below:

Pagy::Frontend::I18N.load(file:'config/locales/gems/pagy/tr.yml', language:'tr')
Pagy::Frontend::I18N.load(file:'config/locales/gems/pagy/en.yml', language:'en')

best regards.

from pagy.

I suppose that the 2 lines are from 2 apps, right? Because there is no support for dynamic translation of multiple languages in the current pagy internal i18n. And if you are using the i18n extra (i.e. the canonical I18n gem), then that 2 lines are not used at all by the pagination.

from pagy.

In fact, they are from the same application and it worked well :) I am not using any additional translation-globalization GEMs, just default i18n bundled with Rails and ActiveSupport. When I switch between locales I can see the translated pagination texts without any problems.

from pagy.

Updated initializer_example.rb (cdab354)

from pagy.