-
Notifications
You must be signed in to change notification settings - Fork 161
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
Support internationalization #384
Comments
I have the same error when the device name or task name contains latin characters.
I've modified my
Hope this helps |
@bkeryan Just to understand better, meaning we would want user-provided string (in this case, the device_name "Gerät") to be encoded to utf-8? Given the scenario above, is this supposed to be the expected output, instead of the encoding error?
|
@charitylxy The goal is to pass the user-provided string to the C API in an encoding that works.
Yes and no. Given that the user has renamed a device to "Gerät", the expected behavior is that using the device works correctly with no errors. However, if the user doesn't have a device named "Gerät", the error output you displayed is correct. |
@charitylxy BTW, this issue does not cover returning localized error messages, since that is localization, not internationalization. The localized error content is available in LabVIEW, but I don't think
|
Closing this issue as it was fixed in the following PRs: |
The DAQmx C API (
nicaiu.dll
) supports internationalization but not localization:nidaqmx-python currently assumes that user-provided strings are ASCII and error messages are UTF-8. User-provided strings that use non-ASCII characters produce encoding errors.
Note that there is also a UTF-8 version of the DAQmx C API (
nicai_utf8.dll
) but nidaqmx-python does not currently use it.Steps to reproduce:
The text was updated successfully, but these errors were encountered: