Problem: If you're experiencing issues with translating custom block contents despite having wrapped them in localization tags, it might be because these are JavaScript strings. Solution: We recommend following our guide on adding gettext calls to JavaScript code, which you can find here: Translating JavaScript strings in WPML. However, be aware of a known issue where WPML might not currently translate JavaScript strings effectively. You can learn more about this problem here: Translating strings from JavaScript files issue. Additionally, strings like "Choose file" and "No file chosen" are dependent on the browser's language setting and may not be influenced by WPML.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
