-
-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In MS Excel elements list formulas are always reported in English regardless of the Excel language. #9144
Comments
@lukaszgo1 wrote:
At first glance, it seems the way the formula is retrieved has not changed since contribution by @dineshkaushal in 2015.2 as of 06ab8e4, although there of course might be side effects I hadn't considered. Note: I'm not arguing at all this should be fixed only if it is a regression, I'm convinced this is an issue for any user of non-English locales. |
@michaelDCurran this one was an easy fix, as the range object exposes a "FormulaLocal" property, if I recall correctly. |
The dispid you need is: 263
I was able to fetch this by:
Opening Excel and focusing on a cell.
Opening the Python console and running the following command:
nav.excelCellObject._comobj.GetIDsOfNames('formulaLocal')
That is, using the IDispatch interface on an Excel range object, calling
GetIDsOfNames with the name: formulaLocal.
|
@michaelDCurran: Thank you! Quick, clear, informative. @lukaszgo1: No need to bother checking earlier versions. PR on its way. |
Steps to reproduce:
Actual behavior:
The formula is shown as '=TODAY()'.
Expected behavior:
The formula should be shown in the language in which it was entered for example for Polish version of Excel '=DZIŚ()'.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-16458,5e710dac
Windows version:
Windows 7 x64
Name and version of other software in use when reproducing the issue:
Microsoft Excel 2010 32-bit in Polish
Other information about your system:
Other questions
Does the issue still occur after restarting your PC?
Yes
Have you tried any other versions of NVDA?
Yes 2018.1 and the problem is present there. I believe it worked correctly in the past, but cannot recall with which version.
The text was updated successfully, but these errors were encountered: