Jürgen Schmidt wrote:
On 4/23/14 9:03 AM, Andrea Pescetti wrote:
I received a DOCX document that OpenOffice Writer cannot open (crash).
The company that sent it to me cannot make it public ...
I understand the problem and we know this situation. I believe it is
not easy to address in an open source project. Either the documents can
be cleaned up and confidential data get removed or the company contacted
another company where special agreements can be done.
In the case of a crash, you are always on the "receiver" side, meaning
that the DOCX document causing the crash is something that people sent
you. And these people may be uninterested in problems with OpenOffice.
Besides the various options for anonymizing a document either on the
"sender" or "receiver" side, already discussed in the thread and quite
interesting in themselves, are there other options involving only the
document and (a specially configured version of) OpenOffice?
I mean, if the first thing a developer does on a crash is to obtain a
meaningful stacktrace and analyze it, and the document becomes mostly
irrelevant at that point, then a stacktrace could be enough to improve
the quality of OpenOffice without needing to access confidential data.
Or is that not enough to work with?
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
