The above markdown is incorrect. Notice there is no space between the [] and the ()` when generating links. So the correct version would be:

p5.js এর একটি [নতুন 2.0 রিলিজ](https://github.com/processing/p5.js/releases/) উপলব্ধ! এটি আগস্ট, 2026 এ ডিফল্ট হয়ে যাবে, তাই এটি পরীক্ষা করে দেখার জন্য এবং বাগ রিপোর্ট করার জন্য এই সময় নিন। 1.x থেকে 2.0 এ স্কেচ রূপান্তর করতে আগ্রহী? [সামঞ্জস্যতা এবং রূপান্তর সংস্থানগুলি দেখুন।](https://github.com/processing/p5.js-compatibility)

So it gets rendered like:

And not:

Thank you @cassiano for catching that! My mistake. I see the extra space in the markdown link.

I'll fix the files of both the languages and push the correction right now.

I've pushed the fix. Here is a screenshot of the corrected Bengali UI—the link now renders properly.
Screenshot 2025年10月28日 at 11 51 58 PM

Didn't you miss this translation?

Hi @cassiano, thanks for pointing this out!

I intentionally left "General" untranslated. In this specific UI context (like "General Settings"), the word "General" is widely understood by users, similar to terms like "File" or "Edit".

The direct Bengali translation (সাধারণ) can also mean "common" or "ordinary," which I felt might be more confusing to the user than the familiar English term. I thought "General" was clearer and more accurate here.

However, if you'd prefer me to translate it, I can add it! Please let me know.

This is up to you, who knows the language details. My expertise is in pt-BR only.

How was your overall experience with the script? How helpful was it?

Thanks @cassiano! I'll leave "General" as-is then.

As for the script, it was fantastic! It was incredibly helpful and saved a huge amount of time. Finding all those missing keys manually would have been very difficult.

It worked perfectly for both hi and bn, and the [NEEDS TRANSLATION] markers made the whole process very clear and simple. It's a great tool, thank you for making it!

Thank you. You are absolutely right about how difficult it becomes to remove unused keys manually. Also, leaving them in the localization files is highly undesirable, given they are not being used anywhere in the codebase.

My proposal in #3666 is to run it automatically during build-time for each locale and them provide AI-generated translations for all missing keys, while allowing end-users to suggest reviewed translations for these directly in the editor itself after deploying this new version.

That sounds like an excellent proposal, @cassiano!

Automating the key syncing during build-time is a very smart solution, and the idea of using AI-generated translations that end-users can review directly is a great way to scale the translation work.

I'll be sure to check out the full discussion in #3666. Thanks for sharing the plan!