Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Lotus .wk1 import filter can't handle formulas containing string concatenation|
|Component:||open-import||Assignee:||AOO issues mailing list <issues>|
|Status:||ACCEPTED ---||QA Contact:|
|Version:||OOo 3.0 Beta 2|
|Issue Type:||DEFECT||Latest Confirmation in:||---|
Description keel 2006-06-13 12:04:56 UTC
When OpenOffice.org Calc imports a .wk1 file, it replaces any formula containing a string concatenation operator (&) with =#NAME!#UNKNOWN FUNC NAME#() . To reproduce the problem: 1. Run a spreadsheet program that can save .wk1 files. (Unfortunately, OOo Calc itself *can't* do this, so you'll have to use a different app.) 2. Enter a formula that uses string concatenation. For example, if you're using Lotus 123 or Quattro, you could enter this: +"foo"&"bar" or, if you're using Excel, you could enter this: ="foo"&"bar" 3. Save the file in .wk1 format. 4. Open the file in OpenOffice. (I'd be glad to provide an example .wk1 file showing the problem if someone would tell me how to upload attachments here. The "Submit an Issue" page explicitly indicates that attachments are supported, but I don't see any means of doing this.) In case it helps, I should mention that a bit of quick testing shows that this bug was not introduced by any recent changes, as both OpenOffice 1.1.5 and StarOffice 5.2 show the same behaviour.
Comment 1 keel 2006-06-13 12:10:49 UTC
Created attachment 37109 [details] Example .wk1 file showing the problem
Comment 2 keel 2006-06-13 12:14:11 UTC
Okay, apparently you can only upload an attachment *after* submitting the initial bug report. That's severely unintuitive. In any case, I've uploaded an example file now.
Comment 3 Joost Andrae 2006-06-13 17:12:59 UTC
confirmed JA->ER: please have a look at this
Comment 4 Joost Andrae 2006-06-13 17:13:19 UTC
Comment 5 ooo 2006-07-20 13:10:33 UTC
Comment 6 Martin Hollmichel 2007-11-09 16:52:34 UTC
change target from 2.x to 3.x according to http://wiki.services.openoffice.org/wiki/Target_3x
Comment 7 keel 2008-08-21 06:09:57 UTC
Any chance of anyone fixing this? The problem's still there in the 3.0 Beta, more than two years after I originally reported it.
Comment 8 urmasd 2013-01-15 15:02:57 UTC
The opcode for concatenation operator is 0x18. It's so trivial to fix.