11-15-2021 12:11 PM
Dear Roberto,
I have some news :
- about me : the problem is not present under LabWindows/CVI 2019 (W10), only since LabWindow/CVI 2020 (even "f1" issue)
- about NI support : they propose to edit the project and use "UTF-8" encoding to resolve the problem. And "PrintTextFile" function works perfectly.
------------
FYI :
It is the same solution for other problems, like with the LabWindows/CVI "menuutil" example.
If you open, for example, an "Example n°1.txt" file, look at the menu shortcut created
(save, quit and comeback in the example).
------------
It is not a good news to us.
Our software use plenty ANSI text and ini files,
so we need to convert all of them to UTF-8
and retest all the functionalities of our software.
It is a long time to do !
Then, the first tests to migrate all the projects from ANSI to UTF-8,
show some compatibility problems.
For example, we use the “¤” character, and this one seems become not usable.
It was in LabWindows/CVI 2019 !
And it is only the beginning of ours tests.
Example :
switch (stringLine[0])
{
case '¤': // Not compilable under CVI 2020 f1, but was in 2019 !
Thank you very much for your help.
Best regards.
11-16-2021 01:36 AM
Pims, if all the ASCII text you have uses only one code page you can try exploring the option to change system locale in windows for the ANSI applications and continue to use ANSI projects in CVI. But if you use ANSI text from multiple code pages, this won't be an option for you.
11-16-2021 03:29 AM
Dear Razvan,
Thanks for your help, in any case, I will test it.
But finally, staying in ANSI projects will give me just a little more time.
Anyway, in the future, I should go through UTF-8.
Some others functions seem have the same encoding problem (menuutil, etc...).
So, because, I always upgrade CVI over time, I will update my software to UTF-8 projects.
And see...
Best regards.