You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by jteh on 2010-03-04 06:08
Even though the strings in the versionInfo module are marked as translatable, they always render as English, even when the language is set to something else. This is most obvious in the NVDA About dialog.
I suspect this is caused by versionInfo being imported in logHandler.FileHandler.handle(). Although this is a late import, NVDA does log some messages before initialising languageHandler. This change was introduced in 0863820 and is therefore probably a regression introduced in 2009.1rc1.
Notes:
We import versionInfo there to check whether this is a test version.
We can't initialise languageHandler earlier because it requires config to be loaded and we want to be able to log NVDA startup and config load.
The text was updated successfully, but these errors were encountered:
Reported by jteh on 2010-03-04 06:08
Even though the strings in the versionInfo module are marked as translatable, they always render as English, even when the language is set to something else. This is most obvious in the NVDA About dialog.
I suspect this is caused by versionInfo being imported in
logHandler.FileHandler.handle()
. Although this is a late import, NVDA does log some messages before initialising languageHandler. This change was introduced in 0863820 and is therefore probably a regression introduced in 2009.1rc1.Notes:
The text was updated successfully, but these errors were encountered: