Hi Michael,
thanks for that.
However, I needed to convert row/col spans into html equivalents,
as I had for example wide header text and row-spanning data cells.
<http://www.lapsedhippy.com/~jmullee/xslt/cals_to_html.xslt.gz>
This did the job, though of course it doesn't scale well
past a few hundred rows.
My hope, in posting my code, was that somebody better at it than
I would point out any inefficiencies.
In the meantime, it worked OK for somebody having problems
with other even-less-efficient code ..
john
-----Original Message-----
From: Michael Müller-Hillebrand [mailto:info(_at_)cap-studio(_dot_)de]
Sent: 13 May 2004 15:49
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] RE: [saxon] OASIS-Open/CALS *big* table conversion
problems
It seems as the solution mainly by Andrew Welch which I
posted in March 2004 with the subject "Table Normalization"
http://www.biglist.com/lists/xsl-list/archives/200403/msg00741.html
addresses some of your issues, especially retrieving the
correct column widths from a table with colspan and rowspan
attributes. Unfortunately the archive display is truncated,
so I send you the posting in a separate mail.
- Michael
On 13.05.2004 (9:56 Uhr -0400), Mullee, John wrote:
Hi
(Sorry, OT, Cross posting to XSL-LIST; let's resume there ...)
Jakob's case doesn't /require/ recursion (AFAICT), but
I had issues with the other people's code when processing
rowspans and colspans.
There was a thread about this in July 2001, 'table
formatting challenge',
where a few solutions were posted, but none of them handled the mixed
rowspan/colspan stuff I had in ~ 100MB xml with < 10^4 cals tables.
The recursive technique was the only one I could come up with,
having to refer, for row/col span reasons, to computed output from
previous context. Recursion allowed storage of intermediate results
in an RTF, which was made available to subsequent calls.
I don't know why NW's code didn't handle Jakob's 2000-row table -
perhaps it's head-recursive and blew stack.
I'm new to XSLT in particular and even functional languages
in general, so NW's code was a bit opaque to me ...
NW posted some corner cases I sucessfully tested my code
against (see below)
Does your code handle it okay? like to post ? :)
john
--
________________________________________________________________
Michael Müller-Hillebrand, Dipl.-Ing. <http://cap-studio.de/>
FrameMaker, FrameScript, XML/XSL,... Publishing-Lösungen
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--
------------------------------------------------------------------------------
Notice: This e-mail message, together with any attachments, contains
information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New
Jersey, USA 08889), and/or its affiliates (which may be known outside the
United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as
Banyu) that may be confidential, proprietary copyrighted and/or legally
privileged. It is intended solely for the use of the individual or entity named
on this message. If you are not the intended recipient, and have received this
message in error, please notify us immediately by reply e-mail and then delete
it from your system.
------------------------------------------------------------------------------