To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=91466
------- Additional comments from [EMAIL PROTECTED] Sat Nov 15 12:46:41 +0000 2008 ------- This issue is a real stopper for wild adoption in organisations. We are in the process of fully migrating from M$Office to OOo. While this works quite well, user resistance is variable and somtimes based on evething else than reason and facts. We have all the PCs in 2.4.1 and started to g*have this problem when working with partners in 3.0 (and also internanlly withthe testing PCs in 3.0). Even if this bullet problem can be considered as minor technically (my workaround is to cancel all style surcharges and apply the style again) THIS CAN'T BE ACCEPTABLE IN A COMPANY perspective ! We are starting to convince other organisations and partners to use OOo, and this bullet probelm is perceived by them as something important and not trivial when you HAVE TO KNOW WHAT IS THE PROGRAM (2.4 or 3.0) who created the ODx file !!! We are now in a worst situation than with M$ incompatibilities between versions !! Believe me, internally people stats to laught at this problem IN A BAD WAY, and this specific problem is causing a lot of backslash on OOo credibility we where patently building. I understand that we can't carry a faulty implemantaion, and I don't know what the solution is, but IMHO, if OOo3 has the right behaviour we should have a way to save a file with bullets in a post 2.4.1 (2.4.2) and this file shouls works well when going thru OO3 -> OO2.4.2-OO3. If we want people understand what is ODT advantage in interoperability, WE SHOULD SHOW IT instead of this really bad public relation one. TIP : Give to an executive an OOo 2.4.1 diaporama re-opened and re(saved by OO3 5 minutes before is presentation, and afer being taken as an amateur beacause is layout presentation is lame, let him explains what you should do with OOo :-< and try to explain this ODT 1.1 / 1.2 real standard and so, and post the result her :-)) As a conclusion, and as my english is bad, I want to be clear : OOo is a fantastic tool, I struglle everyday to complete the full OOo switch in my organisation, but this is a real, non technical, bad problem for OOo acceptance. D. --------------------------------------------------------------------- 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]
