Fixes 32012 - read the correct translations

[DeepDiver1975]

Description

Read translations from the correct location

Related Issue

• Fixes Personal language selection broken in core master #32012

How Has This Been Tested?

Screenshots (if appropriate):

• manually: open settings and see the real language names not the codes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

Open tasks:

• Backport (if applicable set "backport-request" label and remove when the backport was done)

[DeepDiver1975]

backport is in open PR - b669a73

[phil-davis]

works 👍

[codecov]

Codecov Report

Merging #32015 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master   #32015      +/-   ##
============================================
+ Coverage     63.58%   63.58%   +<.01%     
  Complexity    18553    18553              
============================================
  Files          1169     1169              
  Lines         69604    69604              
  Branches       1264     1264              
============================================
+ Hits          44259    44260       +1     
+ Misses        24976    24975       -1     
  Partials        369      369

Flag	Coverage Δ	Complexity Δ
#javascript	52.59% <ø> (ø)	0 <ø> (ø)	⬇️
#phpunit	64.84% <100%> (ø)	18553 <0> (ø)	⬇️

Impacted Files	Coverage Δ	Complexity Δ
lib/private/Helper/LocaleHelper.php	100% <100%> (+2.63%)	15 <0> (ø)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 69b1d49...8f94efa. Read the comment docs.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.