[Issue] XML (MS Excel 2003) Import artifact (value-range)

[YD7FZ5X7]

When: importing a excel-2003 (or compatible home made) XML file.
Effected: formulas that have a Area-Ranges in them.
What: imported formula string is malformed.

example1,source: "=SUM(R[-4]C:R[-2]C)"
example1,result: "=SUM(A1:A3]))"
example2,source: "=SUM(R[4]C:R[6]C,R[4]C[1]:R[6]C[1],R[4]C[2]:R[6]C[2])"
example2,result: "=SUM(A1:A3];[.B1:B3];[.C1:C3]))"
(target cell-addresses are correctly converted)

Os: Win.Xp.Pro.Sp3.Eng (possible using some NL settings)
OOF: 3.0 (final/Or Beta 4), Eng(USA), Eng(USA)
Included XML(excel 2003 generated) Test file.

reported to issue tracker, 95039

Excuse the random name.
MvG.

[acknak]

I don't think support for the MSO 2003 XML format has a very high priority. You can report the problem: [Tutorial] Reporting bugs or suggestions (once the traffic from OOo3 release drops off a bit), but I think you will likely need to find your own solution.

Why do you want to use this format?
Can you use MSOffice to convert it to binary .xls?
Could you use OOXML instead?

[YD7FZ5X7]

Generally background Info:
Needed to transport Spreadsheet data from a old-format into something usable with current day software,
with first priority at something supported/readable by Excel2003(target user), and secondly by oOo(Me).
Specifics: SuperCalc(dos,CAL)(SC.export)->SDI(text), SDI-(MyProgram)->XML.

I don't think support for the MSO 2003 XML format has a very high priority.

Something that I already feared, as
1) I run into the same problem a long time ago.
2) Reading up on XML topics did also showed the same lack of interest in this department.
Still strange, as its just about the only relative easy text-base format supported by oOo that is spreadsheet related,
allowing for relativve easy importing of 'converted' older spreadsheet-data formats.
Well at leased, correct me if I'm wrong, I'm not aware of any other text-base formats supported
by oOo that could be used as a intermediate/import of spreadsheet related date.(formulas included)

… but I think you will likely need to find your own solution.

Hehe, XML was my solution.
But I did read something about making import filters.
But the more I read about it, the more I felt lost.
So laking the needed knowledge in that department, that turned out not to be a viable option for me. (and probably a lot of others to)
+ It use would only be for me personally (checking converted data), and not for the target user for which I did the converting.

Can you use MSOffice to convert it to binary .xls?

I could have, but decided it was easier and more secure in this case to just go with a tmp-install of excel2003 for myself.

Issue-report on hold until oOo site is back to normal.
MvG.

[YD7FZ5X7]

Issue reported to tracker. 95039

[acknak]

Y'know, I just happened to think: that file format is handled by XSLT filters, so should be possible to fix it yourself. You can see where the filters are located by looking under Tools > XSLT Filter Settings > MS Excel 2003 XML > Edit > Transformation.

Of course, I have no idea how comfortable you are with XSLT, or whether that transform is understandable.

[YD7FZ5X7]

Won't hurt me to take a look at it.
If I can make some sens of it, I might give it a try.
Thanks.

[YD7FZ5X7]

After playing around with the “XSLT Filter Settings” for “MS Excel 2003 XML”,
I did got some picture of how some things work inside the filter,
but I also must conclude that there just to much I don't now about
the whole conversion process to make any successful modifications to it.