https://bugs.documentfoundation.org/show_bug.cgi?id=166208
--- Comment #7 from dpkesling <[email protected]> --- I still wonder how this error occurred. You attribute this to user error by my somehow specifying UTF-7, but I have some difficulty with that explanation (not the UTF-7 part). My problem was observed on TWO different machines.The second machine was prepped by removing the entire LibreOffice 24 package via Windows control panel. A fresh download of Libre 25 was performed and installed using the TYPICAL option. TWO fresh copies of the suspect data file were downloaded and testing was performed without any other intervening steps... ESPECIALLY NOT performing any changes in OPTIONS. Again, the "virgin" file was read correctly by my R program whereas the other,"Calc saved" file had the +AC0 encoding error. Again, this happened on BOTH my machines, independent of one another. I do not dispute your UTF-7 assessment... I just wonder how the same error could appear on BOTH machines? Possible answers are: 1) I really am an incompetent dolt who managed to make the same mistake on two different machines, despite the fact that changing a code page seems like a pretty involved, intentional process not prone to accidental revision. 2) Somehow Microsoft Control Panel uninstall process for v24 of Libre (which was working just fine for me) corrupted some residual file that went untouched during the uninstall process. When v25 installed, it picked-up on that changed value. 3) Assuming that v25 went through the entire cycle from Unit test -> System test -> Release testing (which I'm sure it did), there is the possibility that someone JUST PRIOR to the final build of the .exe image for distribution had changed the code page for whatever reason and THAT is what went out the door. Perhaps there are other scenarios which haven't immediately come to mind, but these 3 are certainly candidates. The fact that the error occurred on two different machines diminishes (though doesn't eliminate) the likelihood of Theory 1. The additional fact that my processing simply uses Calc as an intermediary step rather than as a self-contained solution might be a situation not considered in your Release Testing Script/Plan. I shall attempt to manually change the code page to see if that effects a change and success. I will report back if it doesn't. -- You are receiving this mail because: You are the assignee for the bug.
