[Feature Request] Add translation option to add language for Next and prev buttons.

[anvithks]

I was wondering is there any option to add i18n translation to at least translate buttons next and previous. Of course I can try to do it on my own. I know I can hardcode this oj file, but you know that this approach is not something that I want to achieve. Besides adding a language file is much easier for average user.

Originally posted by @sysadmin-info in #24 (comment)

[sysadmin-info]

I was wondering is there any option to add i18n translation to at least translate buttons next and previous. Of course I can try to do it on my own. I know I can hardcode this oj file, but you know that this approach is not something that I want to achieve. Besides adding a language file is much easier for average user.

Originally posted by @sysadmin-info in #24 (comment)

The solution is quite simple. All you have to do is to create a i18n directory inside your plugin, where README.md is located. Then put inside the i18n directory file en.toml, pl.toml, fr.toml etc. for each language.

Example content of en.toml

[embed-pdf-next]
other = "Next"

[embed-pdf-prev]
other = "Previous"

Example content of pl.toml

[embed-pdf-next]
other = "Następna"

[embed-pdf-prev]
other = "Poprzednia"

Then in your file embed-pdf.html inside the shortcodes directory you have to change Next and Previous to this:

        <button id="pdf-prev-{{ substr (.Get "url" | md5) 0 8 }}">{{ i18n "embed-pdf-prev" }}</button>
        <button id="pdf-next-{{ substr (.Get "url" | md5) 0 8 }}">{{ i18n "embed-pdf-next" }}</button>

[anvithks]

Would you be able to raise a PR for this solution? I can test it out.

[sysadmin-info]

The problem is that I have no idea how to raise a PR. I already tested it on my side and it is working as expected.

[anvithks]

The problem is that I have no idea how to raise a PR. I already tested it on my side and it is working as expected.

Sure. No worries .
Let me check how it's done and will push these changes