Created attachment 201252 [details] LO 26.2 Start Center with an FODT file open failure message box If you try opening an (F)ODT file, and it has a syntax error which LO does not auto-recover from - it brings up a message box saying: General Error General input/output error this is poor behavior, because: 1. It's not true. That is, there was no "general error". There wasn't even an error in the input filter. It's the _file_ that had an error (or content we were unable to parse). 2. It doesn't say in which input file the error occurred. 3. It doesn't say where in the input file the error occurred. 4. It doesn't say during what action/operation the error occurred. 5. It doesn't say what was erroneous (which it could say; there's a description of the error printed to stdout) 6. It's a very small message box, at first glance it's barely noticeable after coming up (screenshot to follow) 7. There is no graphic in this message box, e.g. something indicating that it's an error (although TBH that's a more general problem with message boxes for errors).
Note that it's different for non-flat ODF.
(In reply to Mike Kaganski from comment #1) > Note that it's different for non-flat ODF. You mean, that it involves specifying which file within the ZIP, or saying that it's the decompression?
Created attachment 201255 [details] A sample ODS with a duplicating attribute