-
-
Notifications
You must be signed in to change notification settings - Fork 784
Remove Bangla interface file / choice #19643
Copy link
Copy link
Closed
Labels
component/i18nexisting localisations or internationalisationexisting localisations or internationalisationp5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Metadata
Metadata
Assignees
Labels
component/i18nexisting localisations or internationalisationexisting localisations or internationalisationp5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for Bug.
Following @seanbudd's comment: #19496 (reply in thread)
Steps to reproduce
In NVDA language list, select Bangla (Bengali) and restart
Actual behavior
The whole interface is in English.
Expected behavior
Some people wanted to translate the interface to Bangla in the past, but for various reasons, they did not continue this work. No Bangla string has ever landed in NVDA interface translation (.po).
Thus, Bangla interface file should be removed so that Bangla do not appaer in the NVDA language list.
Character description file was pre-existing the effort to translate NVDA's interface to Bangla. So it should remain in NVDA, as other Indian language character description files which had been introduced in NVDA at the same period.
Regarding symbol translation, I'd say the file should be removed too:
bnsymbol file will prevent bn readers to benefit from English file evolutions (symbol name change, level change, etc.) since there is no bn maintener anymore.NVDA logs, crash dumps and other attachments
N/A
System configuration
NVDA installed/portable/running from source
installed
NVDA version
2026.1beta3
Windows version
N/A
Name and version of other software in use when reproducing the issue
N/A
Other information about your system
N/A
Other questions
Does the issue still occur after restarting your computer?
N/A
Have you tried any other versions of NVDA? If so, please report their behaviors
Same issue in all 2025.x versions at least.
If NVDA add-ons are disabled, is your problem still occurring?
N/A
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
N/A