To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102837
------- Additional comments from [email protected] Tue Jun 16 16:03:35 +0000 2009 ------- I added the requested information. Before marking as INVALID, please notice: I'm NOT complaining about the messed up file content. I'm perfectly aware that this is a Google Docs problem. But since OpenOffice.org does not warn about a defect file, I at least expect all OpenOffice.org functions to work properly. If you're working in a distributed environment, it's totally impossible to notice if the file was once stored on Google Docs. If you now try to apply styles to the content, this will still work. But you will be unable to update all the styles simultaneously (see initial description), like you're able to, when working with a file which was not stored on Google Docs. So the least I'm asking for, is to warn the user about problems with this file. Otherwise, he might just blame OpenOffice.org for this. Furthermore, with growing ODF support for other software, this problem might not be limited (now, or in the future) to the Google ODF implementation. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
