Plugin Author
Tim W
(@timwhitlock)
Loco Translate observes WordPress-specific locale variants like de_DE_Formal or de_CH_Informal. When using DeepL (and OpenAI) via Loco Translate, these codes will cause it to request the required style.
If you’re using a neutral code like de_DE, then because there exists a Formal variant, but no explicit informal variant, Loco Translate will default to “informal” (and the other way around). This logic is probably best not relied upon, because if an informal variant were to suddenly exist, it would change the behaviour.
If you want to be certain what formality your locale has, you can use the loco_locale_formality filter to force the required value. This is what I would recommend.
If the formality is set correctly and the API still mixes the styles, then that would be an issue outside of my plugin’s control.
@timwhitlock de_DE_informal microsoft API still translate formal.
i use microsoft API because deepL is getting worse.
see https://www.awesomescreenshot.com/video/44369988?key=de9ca0b3eb7d41b1f466ee9e217b879c
please add in available languages: de_DE_informal and make it work show “DU” instead of “SIE”
thank you.
Plugin Author
Tim W
(@timwhitlock)
Microsoft Translator doesn’t support formality variation. It accepts the language code de only.
@timwhitlock will de_DE_Informal also used when de_De selected as language?
If not: How can i force use de_DE_Informal instead of de_De?
Plugin Author
Tim W
(@timwhitlock)
will de_DE_Informal also used when de_De selected as language?
As explained – de_DE is implied “informal” because there exists a formal variant, but no informal one. So yes – for OpenAI and DeepL – Loco will request the informal tone for de_DE. You will not see de_DE_Informal on your screen, but this is what is happening.
How can i force use de_DE_Informal instead of de_De?
Use the filter, as I advised. This is a better route in case of future changes to WordPress locales.
