You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2012/10/06 22:54:35 UTC

[Bug 121151] Uppercase MM in number format from Excel is not recognized

https://issues.apache.org/ooo/show_bug.cgi?id=121151

Andrea Pescetti <pe...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
            Summary|Date cell doesn't show      |Uppercase MM in number
                   |month                       |format from Excel is not
                   |                            |recognized
     Ever confirmed|0                           |1

--- Comment #5 from Andrea Pescetti <pe...@apache.org> ---
So the issue here is that the number format
[$-410]dd/MM/yyyy
is not recognized completely.

Its meaning is:
- "[$-410]": (irrelevant in our case) interpret according to the Italian
"culture", see
http://msdn.microsoft.com/en-us/library/windows/desktop/dd318693%28v=vs.85%29.aspx
- "dd": show the day as 01-31, see
http://office.microsoft.com/en-us/excel-help/number-format-codes-HP005198679.aspx
- "MM": not standard, it should be "mm" (lowercase) according to the same link
and it would mean month as 01-12
- "yyyy": year, 4 digits (same link)

So it seems that the report generation is indeed producing something that does
not adhere to the Microsoft specification, since it produces "MM" instead of
"mm". If you open your file in Notepad (yes, it's a normal text file) and
replace
[$-410]dd/MM/yyyy
with
[$-410]dd/mm/yyyy
then OpenOffice will display it correctly. Otherwise, it will ignore the
uppercase "MM" since it's invalid, and it will display day and year only.

And now the problem is: do we want to relax the OpenOffice parser so that "MM"
and "mm" are considered equivalent like apparently Excel and Gnumeric do? This
usually requires discussion and valid arguments, unless you manage to find some
Microsoft specification saying explicitly that we should be case-insensitive
here.

-- 
You are receiving this mail because:
You are the assignee for the bug.