From b91788bdfe56875a9342d011439f954e50d9c751 Mon Sep 17 00:00:00 2001 From: Andras Timar Date: Fri, 30 Nov 2012 17:03:34 +0100 Subject: -> to please pofilter Change-Id: I6708f2d8d99d8b948733fb29b0a9279892bd3da9 --- source/text/scalc/05/empty_cells.xhp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/text/scalc/05/empty_cells.xhp b/source/text/scalc/05/empty_cells.xhp index 774afb4bc9..38951eb920 100644 --- a/source/text/scalc/05/empty_cells.xhp +++ b/source/text/scalc/05/empty_cells.xhp @@ -47,7 +47,7 @@ In older versions of the software, empty cells were forced to numeric 0 in some contexts and to empty string in others, except in direct comparison where =A1=0 and =A1="" both resulted in TRUE if A1 was empty. Emptiness now is inherited until used, so both =VLOOKUP(...)=0 and =VLOOKUP(...)="" give TRUE if the lookup resulted in an empty cell being returned. A simple reference to an empty cell is still displayed as numeric 0 but is not necessarily of type numeric anymore, so also comparisons with the referencing cell work as expected. For the following examples, A1 contains a number, B1 is empty, C1 contains the reference to B1: -A1: 1 B1: <empty> C1: =B1 (displays 0) +A1: 1 B1: <Empty> C1: =B1 (displays 0) =B1=0 => TRUE =B1="" => TRUE =C1=0 => TRUE @@ -65,7 +65,7 @@ =ISBLANK(VLOOKUP(1;A1:C1;2)) => TRUE (B1, previously was FALSE) =ISBLANK(VLOOKUP(1;A1:C1;3)) => FALSE (C1) Note that Microsoft Excel behaves different and always returns a number as the result of a reference to an empty cell or a formula cell with the result of an empty cell. For example: -A1: <empty> +A1: <Empty> B1: =A1 => displays 0, but is just a reference to an empty cell =ISNUMBER(A1) => FALSE =ISTEXT(A1) => FALSE -- cgit v1.2.3