Re: Problems with Microsft's new Office 'XML'

Just a quick followup to 'close' the question.

The main problem with the new Excel XML is that it is still a binary. I haven't managed to read the XML binary with Spreadsheet::ParseExcel, but have worked around this by getting the client to supply a 'normal' Excel binary and then reading that.

If anyone does manage to combine xml parsing with Excel binary, please do msg me :)

Comment on Re: Problems with Microsft's new Office 'XML'

Replies are listed 'Best First'.
Re^2: Problems with Microsft's new Office 'XML' by pajout (Curate) on Oct 10, 2005 at 15:26 UTC
I have no experience with M$ tools for transforming from xls to XML, but, if your requirement is not too general, you can write VBA macro which transforms and prints xls into _your_ form of xml file. And parsing will be easy on the next step... I hate the wheel reinvention, but I suppose that M$ XML could be similar to <some>binary_code</some>...	[reply]
Re^3: Problems with Microsft's new Office 'XML' by graq (Curate) on Oct 10, 2005 at 22:56 UTC
The file (fetching and) processing takes place on a Solaris box; I'm not aware of any way of running VB script without using a Windows OS. As a total aside, I am beginning to dislike this problem, as it looks like I'm going to have to use SOAP to fetch the file now (and in some awful flat WSDL format) which is causing completely different problems - but I am betting that other clients will wish to supply (non binary-xml) Excel, so the current parsing solutuion is of use. Look out for my next question in SoPW! <a href="http://www.graq.co.uk">Graq</a>	[reply]


go ahead... be a heretic
	PerlMonks