Cart
[Home] [By Thread] [By Date] [Recent Entries]
Toshihiko,
At 03:58 AM 5/29/2009, you wrote: Thank you for your reply. I knew of it vaguely but didn't know they had made so much progress. The XSLT2.0 implementation seems to adopt two-phase process for processing table. First, normalize the table. Second, process the normalized table. Depending on exactly what's meant by "normalized", that seems like a reasonable approach. It makes things simpler. I am thinking that my approach (to get column position directly) is too straightforward to process complexed CALS table. Well, the basic problem is that there are a number of properties on a cell that might inherit either from a colspec, from a row, from the table itself or in some cases even from elsewhere. In effect, there's an inheritance hierarchy that may have to be traversed in order to determine the value of any given property. If the current plan is to rewrite the table with all inherited properties explicit, this would make rendering much easier. In any case, given that the Docbook team is onto the problem, I think you have a place to turn. Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
|
