https://bz.apache.org/ooo/show_bug.cgi?id=25710
brainchild <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #22 from brainchild <[email protected]> --- I am affected by this issue, and find it astonishing that although it has the potential to cause substantial problems for the user, was reported 15 years ago, and requires no debugging or redesign to resolve, it still remains open. Is there no way to triage this problem to a track of issues that are easy to fix and that significantly reduce the chance the very unwanted effects? Publishing a document with inaccurate indices is a bad result, whereas a feature such that the application rebuilds indices on major events such as saving, opening, printing, and editing would seem nearly trivial to implement. I myself received a document that was automatically generated by an external tool. The tool marks the indices as dirty in the file it creates, which Microsoft users report is detected by MS Office as soon as the file is opened. Meanwhile, Open Office is completely silent, making not even a warning. Some users are proposing homegrown macros to solve the problem to compensate for lack of support from inside the application (https://forum.openoffice.org/en/forum/viewtopic.php?f=5&t=70662). But a custom macro adopted by a few diligent users does nothing to protect against an arbitrary user receiving a file with dirty indices and remaining oblivious because the application was lazy. If a major issues can be partially solved with 10 lines of macro code, then can it be fully solved, in the code base, over a period of 15 years? -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue.
