KIREEK
KIREEK#0172
- Gender
- Male
Description
While preparing a custom translation aligned with the current 169-line online.en.ls, several launcher UI elements either have no .ls entry or ignore the
.ls override entirely. A strings dump of online.exe confirms these are embedded as ASCII / XAML resource defaults inside the binary, which appear to take
precedence over the .ls value.
Issues, by page
Page 1 (front page)
- The FAQ button has no entry in online.en.ls — always displays in English.
- The D3D: dropdown items have no .ls entries. All 12 options remain in English:
Direct3D 8, Direct3D 9, Direct3D 9on12, Direct3D 11 (2.79.3), Direct3D 12 (2.79.3), Vulkan (2.3.1), Direct3D 11 (2.87.1), Direct3D 12 (2.87.1), Vulkan
(2.7.1), Direct3D 11 (Custom), Direct3D 12 (Custom), Vulkan (Custom).
- The Anti-Aliasing: dropdown values have no .ls entries.
Page 2
- The Shaders label has no .ls entry.
- The dgVoodoo VRAM: dropdown's Auto value has no .ls entry.
Page 3
- The NEXT PAGE button on this page is not translated, even though online.user.ls line 72 is translated. The rest of page 3's content does pick up the
translation correctly.
Page 4 (and visible on every page: footer buttons)
- PREVIOUS PAGE, NEXT PAGE, CHECK FOR UPDATES, MORE, REVERT — these strings DO exist in online.en.ls (lines 73, 72, 40, 41, 42) and translating them in
online.user.ls has no effect — the launcher still shows the English text after restart. The online.exe strings dump shows multiple ASCII copies of each of
these labels embedded as XAML defaults.
Repro
1. Generate a fresh online.user.ls from the current 169-line online.en.ls, with all entries (in particular lines 40, 41, 42, 72, 73) translated to a
non-English string.
2. Restart the launcher.
3. Observed: the items listed above remain in English on each respective page.
While preparing a custom translation aligned with the current 169-line online.en.ls, several launcher UI elements either have no .ls entry or ignore the
.ls override entirely. A strings dump of online.exe confirms these are embedded as ASCII / XAML resource defaults inside the binary, which appear to take
precedence over the .ls value.
Issues, by page
Page 1 (front page)
- The FAQ button has no entry in online.en.ls — always displays in English.
- The D3D: dropdown items have no .ls entries. All 12 options remain in English:
Direct3D 8, Direct3D 9, Direct3D 9on12, Direct3D 11 (2.79.3), Direct3D 12 (2.79.3), Vulkan (2.3.1), Direct3D 11 (2.87.1), Direct3D 12 (2.87.1), Vulkan
(2.7.1), Direct3D 11 (Custom), Direct3D 12 (Custom), Vulkan (Custom).
- The Anti-Aliasing: dropdown values have no .ls entries.
Page 2
- The Shaders label has no .ls entry.
- The dgVoodoo VRAM: dropdown's Auto value has no .ls entry.
Page 3
- The NEXT PAGE button on this page is not translated, even though online.user.ls line 72 is translated. The rest of page 3's content does pick up the
translation correctly.
Page 4 (and visible on every page: footer buttons)
- PREVIOUS PAGE, NEXT PAGE, CHECK FOR UPDATES, MORE, REVERT — these strings DO exist in online.en.ls (lines 73, 72, 40, 41, 42) and translating them in
online.user.ls has no effect — the launcher still shows the English text after restart. The online.exe strings dump shows multiple ASCII copies of each of
these labels embedded as XAML defaults.
Repro
1. Generate a fresh online.user.ls from the current 169-line online.en.ls, with all entries (in particular lines 40, 41, 42, 72, 73) translated to a
non-English string.
2. Restart the launcher.
3. Observed: the items listed above remain in English on each respective page.
Last edited:
