Remove empty Bangla translation

[CyrilleB79]

Link to issue number:

Closes #19643

Summary of the issue:

When selecting Bangla language for NVDA, the whole interface is in English. This is because there had been an attempt to have NVDA translated in Bangla around 2022. Unfortunately, almost no translation at all has reached an NVDA release. As a result:

1. In the Bangla interface file, no string at all is translated
2. In the symbols.dic file, the vast majority of symbols are just English. Only 6 complex symbols have been modified. And among these 6 symbols:
   • one of them is written ". sentence ending" (with an extra space), thus it does not actually control anything
   • the decimal point just has no replacement, making the rule apparently malformed or at least un-useful and harder to understand

Description of user facing changes:

• Bangla won't be proposed as an NVDA language in the languages list.
• When using Bengali voice, the 4 valid Bangla/Bengali complex symbols will be reported in English. But users using Bengali voice will benefit of any change done in English symbol file since 2022 and in the future.

Description of developer facing changes:

N/A

Description of development approach:

• Removed interface (nvda.po) and symbols files for Bangla.
• Character description file remains unchanged. It was pre-existing 2022 translation attempt and actually contains Bangla character names. It had been introduced much earlier in NVDA with other character files for Indian family langages.

Testing strategy:

• Check that Bangla is not offered anymore in the language list.
• Check that starting NVDA with --lang=bn
• Check that Bangla character description still works with eSpeak, Bengali voice.

Known issues with pull request:

None.
If someone wants to translate again NVDA to Bangla in the future, they can just do it.

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

[seanbudd]

can we please not modify this or the list in this PR?

[CyrilleB79]

@seanbudd can you clarify?

• Should I remove all the changes in the User Guide? In this case, we would have the User Guide wrongly stating that we support Bangla...
• Or just remove Bangla from the list? But in this case, should I keep 56 supported languages (which is wrong), set it to 55 (which is also wrong) or set it to 63 (which is correct but not in line with the expanded language list that follows)?
• And if I remove some User Guide modifications from this PR, should I introduce them in another PR? Against alpha or beta?

My idea when opening this PR against beta was the following:

1. The language list had already been modified during this beta dev cycle due to Cambodian addition.
2. Translation freeze has not yet started. Thus some translators have not yet started translating the User Guide. Fixing the list of languages and its number of items in the same beta dev cycle would allow translators to perform only one check of this list instead of 2 in 2 different beta cycle.
3. I have not added extra possible modification of this list that have been discussed in Clarify / fix the list of supported languages #19496 (bullet list formatting, auto-generation of the language names, etc.) since these are subject to discussion and introducing this late in the beta dev cycle may be risk (e.g. translation freeze delay).

[CyrilleB79]

As an additional note.
I do not plan for now to implement an automated generation of the language list. If that's what NV Access want, I'd suggest that you open a formal issue for that, since for now, this idea is only part of what has become a discussion (#19496). Though in any case it has no sense to keep the current wrong number of languages and the incomplete list in the User Guide for the next releases.

[seanbudd]

Hi @CyrilleB79 - I believe this was already discussed on #19496.
We are looking to refine the policies for including languages in the user guide.
As requested, please ensure this PR only removes Bangla.

[seanbudd]

Should I remove all the changes in the User Guide? In this case, we would have the User Guide wrongly stating that we support Bangla...
Or just remove Bangla from the list? But in this case, should I keep 56 supported languages (which is wrong), set it to 55 (which is also wrong) or set it to 63 (which is correct but not in line with the expanded language list that follows)?

Bangla was never included in this count or list. You can just remove the files without touching the user guide.

[seanbudd]

And if I remove some User Guide modifications from this PR, should I introduce them in another PR? Against alpha or beta?

Please hold off on this until a policy is established

[CyrilleB79]

OK, I have removed the changes in the User Guide and cleaned the initial description accordingly.

[seanbudd]

Thanks @CyrilleB79