Red Hat Bugzilla – Bug 152814
FC1 - OpenOffice.org - April date formatting bug
Last modified: 2008-05-01 11:38:06 EDT
As instructed from https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121838
puting this bug report here to Fedora Legacy.
Description of problem:
There is a bug in OpenOffice.org 1.1.0 that displays dates in April
incorrectly. It is described in qa.openoffice.org at
An example is typing 4/11 in Calc while in year 2004. The date won't
format correctly, even if you've correctly setup the cell formatting
to Date format. Other years have other dates as problems, example, for
year 2005 it's 4/10.
This has been fixed in OpenOffice.org 1.1.1.
Steps to Reproduce:
1. Open Calc 1.1.0.
2. Enter the date 4/11/04 in Cell A1.
3. Enter the date 4/12/04 in Cell A2.
4. Enter the date 4/13/04 in Cell A3.
5. Enter the date 4/10/05 in Cell A4.
6. Format all cells to date, preferably something easier to read, like
"April 11, 2004".
Actual Results: The dates 4/11/04 and 4/10/05 are not formatted
Expected Results: The dates mentioned above should have been
This has been fixed in OpenOffice.org 1.1.1, according to the QA link
mentioned above. This was actually fully fixed in OpenOffice.org 1.1.2 according
------- Additional Comments From firstname.lastname@example.org 2004-10-16 07:40:40 ----
While this is an annoying bug, it is not a Security related bug, and thus not
suitable for Fedora Legacy. If at such time we need to do a security fix on
OO.org, please remind us to fix this issue as well.
------- Bug moved to this database by email@example.com 2005-03-30 18:28 -------
This bug previously known as bug 2162 at https://bugzilla.fedora.us/
Originally filed under the Fedora Legacy product and General component.
Unknown priority P2. Setting to default priority "normal".
Unknown platform PC. Setting to default platform "All".
The original reporter of this bug does not have
an account here. Reassigning to the person who moved
it here, firstname.lastname@example.org.
Previous reporter was email@example.com.
Setting qa contact to the default for this product.
This bug either had no qa contact or an invalid one.