Translation Issues Due to Non-Standard JSON Format

We are currently attempting to translate the interface into Turkish (and other languages) using standard tools like Loco Translate.

We noticed that the plugin does not recognize the standard WordPress JSON translation files generated automatically by Loco Translate (or WP-CLI) from the .po files. Even though the .po and .mo files are correct and located in the system languages directory, the Vue.js interface remains untranslated.

The Issue: Upon investigating the plugin files, we found a convert-cli.js script in the languages folder. It appears that the plugin relies on a custom JSON format and specific naming convention (e.g., uixpress-tr_TR-uixpress.json) generated by this internal Node.js script, rather than using the standard WordPress wp_set_script_translations() implementation which loads standard JED-formatted JSONs.

Our Workaround: We confirmed this behavior by manually creating a JSON file named uixpress-tr_TR-uixpress.json formatted exactly as your script requires, and the translations started working immediately.

The Request: However, manually creating these custom JSON files is not sustainable and prevents us from managing translations efficiently via the WordPress admin panel.
Could you please consider updating the plugin to support standard WordPress script translations? Specifically:

1. Utilize wp_set_script_translations() for your registered scripts.

2. Allow the plugin to load standard WordPress JSON translation files (generated by Loco Translate or core WP) instead of requiring the custom output from convert-cli.js.

This would greatly improve compatibility for multilingual sites and simplify the translation process for your users.