[Libreoffice-bugs] [Bug 49135] MONTH() function returns '12' for empty cells

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 25 17:25:54 CEST 2012


https://bugs.freedesktop.org/show_bug.cgi?id=49135

Rainer Bielefeld <LibreOffice at bielefeldundbuss.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |LibreOffice at bielefeldundbus
                   |                            |s.de

--- Comment #1 from Rainer Bielefeld <LibreOffice at bielefeldundbuss.de> 2012-04-25 08:25:54 PDT ---
NOT reproducible with "LibreOffice 3.5.3.1 (RC1) German UI/Locale [Build-ID:
21cb047-d7e6025-9ba54fc-b4a51a8-f42372b] on German WIN7 Home Premium (64bit),
=MONAT('') gives Error message "#NAME" as expected.

Also not reproducible with 3.4.5

So might be Linux reated? But:

In my German  Ubuntu LibO 3.4.4 (VirtualBox) function MONAT() is not
translated, but works as expected.

@reporter:
Thank you for your report – unfortunately important information is missing.
May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to
find out what information will be useful to reproduce your problem? If you
believe that that  is really sophisticated please as for Help on a user mailing
list
Please:
- Attach a sample document (not only screenshot) or refer to an existing 
  sample document in an other Bug with a link.
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem (due to example in Bug 43431)
– if possible contribute an instruction how to create a sample document 
  from the scratch
- add information 
  -- concerning your PC 
  -- concerning your OS (Version, Distribution, Language)
  -- concerning your LibO version (with Build ID if it's not a public release)
     and localization (UI language, Locale setting)
  –- Libo settings that might be related to your problems 
    (video hardware acceleration ...)
  -- how you launch LibO and how you opened the sample document
  –- If you can contribute an OOo Issue that might be useful
  -- everything else crossing your mind after you read linked texts

Even  if you can not provide all demanded information, every little new
information might bring the breakthrough.

May be you can test <https://www.libreoffice.org/get-help/bug/> for submitting
bug reports?

Please report new bugs with initial status UNCONFIRMED

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Libreoffice-bugs mailing list