• Resolved Aydin Javadly

    (@xakerik)


    Hello. Thank you for this excellent work. However, I have faced several problems. I work in Azerbaijan. The date and time in your form is mostly taken from the browser language. Google Chrome and many browsers do not yet fully support the Azerbaijani language. I didn’t see any text about date and time translation in the translation files. I liked your work and I am working to translate the plugin into Azerbaijani language. I am currently working on a test website. I want to get the PRO version soon. But this translation problem complicates the work a bit. I will be glad if you can help me in this regard.

    https://pasteboard.co/BMlaTzhIdyeV.png

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author ameliabooking

    (@ameliabooking)

    Hello there.

    Thank you for reaching out to us.

    The front-end calendar is loaded from a 3rd party HTML5 library, and we have no effect on it. If the translation for your language exists in the library, it will be pulled and displayed on the front-end based on the locale language of the page.

    You should be able to access this file: /wp-content/plugins/ameliabooking/public/js/frontend/amelia-booking.js and in there find your locale (“az” if we’re not mistaken). When you scroll through the line, you will see the month names and the weekday names which you would be able to change. If that helps, you would need to do that every time the plugin updates as we cannot include the language through Amelia since it’s being pulled from a 3rd party library.

    Kind regards.

    Thread Starter Aydin Javadly

    (@xakerik)

    Thanks for the answer. But the solution didn’t help. I saw the Azerbaijani language on the file. Everything is good there. I tested. On the mobile phone, everything is fine, but the desktop version is not translated.

    Plugin Author ameliabooking

    (@ameliabooking)

    Hi again.

    If the Azerbaijani language is loaded on the page, it should load the correct day name strings. As you can see in the file we advised you to inspect, they should all be there.

    Can you open the console (F12) of the booking page, and in there type window.localeLanguage[0] ? That should show you the locale of the page.

    If the page is public, and free to be viewed by everyone, would you be able to provide the page URL here, so we can also take a look?

    The language is pulled from the 3rd party library, so it’s available both in Amelia Lite and the full version – we haven’t had any issues with this locally, so it’d be good if we can take a look at the page.

    Kind regads.

    Thread Starter Aydin Javadly

    (@xakerik)

    Thanks for the answer. I did as you said. The language “az” is shown there. But it doesn’t translate. Website: https://birseans.az/registration

    https://pasteboard.co/iAUk0t20xUZu.png

    Plugin Author ameliabooking

    (@ameliabooking)

    Thank you for the page.

    We have forwarded the issue to our developers, and as soon as we hear from them we’ll get back to you.

    Plugin Author ameliabooking

    (@ameliabooking)

    Hi again.

    After inspecting this issue, it seems there’s a problem with Chrome and the intl library that’s being used. In other browsers, it seems to be working fine: https://imagesharing.com//photo.php?s=9jnhc0dy

    It also works on Chrome for Android, but for the desktop app – it’s blocking the library for some reason.

    We can see that, for example, “Uzbek Latin” contains similar characters, and it’s facing the same problem. Our developers will see if there’s anything we can do about it in the future, but we can’t promise anything, since this seems to be a conflict between the browser and the 3rd party library that we’re using.

    Kind regards.

    Thread Starter Aydin Javadly

    (@xakerik)

    Thanks for your reply. I figured out the source of the problem. I also thought the problem is in the browser. I wish you success in your work.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Date and time translation’ is closed to new replies.