To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52559
                  Issue #:|52559
                  Summary:|VALUE() fails on HTML table cell with trailing non-
                          |breakable space
                Component:|Spreadsheet
                  Version:|OOo 2.0 Beta
                 Platform:|PC
                      URL:|
               OS/Version:|Windows XP
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P4
             Subcomponent:|open-import
              Assigned to:|spreadsheet
              Reported by:|jeffdp





------- Additional comments from [EMAIL PROTECTED] Wed Jul 27 11:45:05 -0700 
2005 -------
A particular set of data from an HTML table is to be imported from a web
application into Calc so that it can be massaged.  In this particular
application, the certain cells of interest to me contain numbers, concatenated
with HTML non-breakable space " "; presumedly, to prevent ugly formatting
in the event of empty cells.  Therefore, the data in these columns looks
something like this, with leading spaces:

<td align="right" nowrap="nowrap">         1&nbsp;</td>

Importing this data into Calc results in a string value rather than a number.  
Since I could not operate on the data directly, I chose to use VALUE(). However,
a side effect of the non-breakable space is that the VALUE() complains with
Err:502.  CELL("TYPE") yields "l" (label) and CELL("CONTENTS") yields a value
which is still not usable by VALUE().

Editing the HTML source and removing the &nbsp results in valid numbers, at
which point VALUE() becomes superfluous anyway, as the cells are already a
numeric type, and can be referenced directly in formulas.

So -
1) &nbsp; results in a string type data value in resulting cell; and
2) VALUE() cannot determine the value of the string containing the invisible 
&nbsp;.

Either fix works for me, but I imagine that they are related and would probably
be fixed concurrently.

I am attaching a page of specific data (anonymized to protect the innocent)...
the last three tables rows were edited in the HTML source to determine whether
leading spaces, the &nbsp, or both were the cause.  However, this is easily
reproducible with a table containing a single element of data.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to