2009/11/14 NoOp <[email protected]>: > On 11/13/2009 12:41 PM, Dotan Cohen wrote: >> There is a rather critical bug in Open Office regarding date formats. >> This issue has cause both myself and my users continued frustration, >> in fact I would estimate that over half of the users that I have >> introduced OOo to have complained or abandoned OOo due to this bug. I >> just noticed that this bug is marked as a feature request, not a bug >> in the OOo Issue tracker. Will someone with the proper permissions >> please mark the bug as a bug, not a feature request: >> http://www.openoffice.org/issues/show_bug.cgi?id=5556 >> >> Thank you in advance. >> > > You can review to see if you think that the issue is a showstopper: > http://wiki.services.openoffice.org/wiki/Showstopper > and if so nominate it on the release list. > > Read the page completely & follow the instructions carefully. If you are > unsure, then the last line is the best option: > <quote> > if you are not sure if your bug is a Stopper or not, you can ask on the > mailing list too > </quote> >
Thanks. I have read that page and I am rather divided on the issue as it pertains to dataloss. In the most technical sense, one could argue that this is not a dataloss issue as the original date is in fact stored correctly in the ODF file. However, that date is displayed incorrectly to the user, who then may make decisions based on that wrong information. Worse, when editing the data (as opposed to inserting a new date) the user is _more_than_likely_ to enter the date in the "wrong" format, and therefore the data stored in the ODF file will in fact be the wrong data, no matter how it is displayed in the future. I will subscribe to the releases list and ask there in the next few days. In the meantime, I would appreciate more feedback on this issue, especially by users who have been affected by this issue. Thanks! -- Dotan Cohen http://what-is-what.com http://gibberish.co.il --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
