[Bug] The result of the translation is showing Portuguese (Portugal) instead of Portuguese (Brazil)

[lbarrios1]

Is there an existing issue for this?

• I have searched the existing issues

Have you checked the FAQ (#6)?

• I have checked the FAQ

Are you using the latest Zotero and the latest plugin?

• I have confirmed I'm using the latest Zotero and the latest plugin

Environment

OS: Windows 11 Home
Zotero Version: 7.0.9 (64-bit)
Plugin Version: 2.0.5

Describe the bug

I configured the plugin to translate from English (United States) to Portuguese (Brazil). However, the translation result is showing as Portuguese (Portugal).

This is proven by testing the Google Translate tool itself, which shows the difference in spelling between Portuguese (Brazilian) and Portuguese (Portugal) words.

Debug Output

debug output.txt

Anything else?

[windingwind]

Thanks for the debug log. Seems like Google Translate has its own language code for this language. I will try to fix, also PR is always welcome.

[github-actions]

🚀 This ticket has been resolved in v2.0.8. See Release v2.0.8 for release notes.

[windingwind]

Google Translate uses pt for Portuguese (Brazil), instead of pt-BR, and pt-PT for Portuguese (Portugal). It should be fine if you choose the option Portuguese if you are on old versions.

The latest release should fix this.

[lbarrios1]

@windingwind, thank you for your attention on this matter.

I'm afraid that the bug is still not fixed.

I updated the plugin to the most updated version (2.0.12).

It doesn't matter if I choose Google (API) engine or other engine (e.g., DeepL (Free Plan)), and it doesn't matter if I choose 'Portuguese' or 'Portuguese (Brazil)' as output languages, the result of the translation is still showing in Portuguese (Portugal).

debug output.txt

[github-actions]

🚀 This ticket has been resolved in v2.0.13. See Release v2.0.13 for release notes.

[windingwind]

Thanks for the feedback.

For Google, I really have no idea what's going on there. Since this is a somehow hacked version of the API used by the Google Translate website, there are a lot of guesses that Google provides degraded results on purpose for this kind of usage.

The issue with DeepL and DeepLX should be fixed now. Please try again.

[windingwind]

I keep this issue open for now:)