WPML String Translation 3.3.3

[Accessibility] Improved colors and contrast according to European Accessibility Act (EAA) standards.
Fixed incorrect translation in the Customizer when the user profile language differs from the site’s default one.
Fixed inability to create taxonomy labels in a language other than English.

Fixed an error with the Glossary sync process
Improved the error parsing for corrupted content
Fixed an issue where the Other texts (Strings) section on the Translation Dashboard was displaying no strings in certain cases
Fixed an issue where linebreaks were removed from mail notifications in secondary languages
Fixed an issue with the formatting of HTML tags when importing PO files
Fixed an issue where backslashes were removed in string translation
Fixed an issue where Gravity Form Translations were not removed on the frontend
Implemented a fix that now allows using 0 (zero) as a valid input in String Translation
Fixed an error on the Translation Dashboard that happened when too many languages were active
Fixed a few edge cases where translations from translation (.po) files were not fully loaded for strings autodetected by WPML
Fixed an issue with autodetecting strings that have incorrect HTML tags
Fixed an issue with importing translation (.po) files when the default language is not English
Removed a deprecated feature for auto checking .mo files

Fixed an issue with missing strings on multisites
Fixed an error when installing the String Translation add-on using Composer 2.7.9