[xep-support] Version 4.7

[Steve Ylvisaker]

Michael

Thanks for the explanation. This helps. 

Our implementation is fairly simple. We just want to place the text "(continued)" on the table title when table spans multiple pages. With RenderX we accomplished this with <rx:table-omit-initial-header/>. Unfortunately, the implementation of this solution requires a lot of additional and confusing constructs to gain the desired effect. When Antenna House implemented this property we were able to get rid of all of that code and just use the markers. As we are in the process of setting up a side by side test I am currently just placing <fo:retrieve-table-marker/> in a different name space so RenderX will ignore it and not abort. The result will not meet our ultimate requirements but I am certain that RenderX will eventually have this feature in place so I am not concerned about continuing without it at this time.

Mostly I was concerned that I had missed something when I installed 4.7

Again - thanks for the explanation
Steve


-----Original Message-----
From: owner-xep-support at renderx.com on behalf of Michael Sulyaev
Sent: Tue 9/12/2006 10:49 AM
To: xep-support at renderx.com
Subject: Re: [xep-support] Version 4.7
 
Steve Ylvisaker wrote:
> I installed version 4.7 today. It appears that it does not support 
> <fo:retrieve-table-marker/>. Could someone confirm that this is the case?

Hello Steve,

XEP 4.7 does not support table-markers. This is clearly stated in the 
Reference and in the message to xep-announce at .

RenderX is now working on a new version of the formatter, which will 
support table markers, maybe somewhat different table markers from what 
XSL 1.1 WD currently describes.

Table markers are tricky. As soon as you think of an example that is at 
least slightly more complex than those proposed by the WD, you 
immediately realize that the description of the table markers has 
significant drawbacks.

Consider, for example, the situation when the number of columns in a 
table has to be changed because of a table-marker retrieved on 100th 
page, bringing in more table-cells in a row than the current number of 
columns. There are other situation of this kind, lots of them, actually.

The design and description of table markers has suffered several changes 
during the evolution of 1.1 spec. It is possible that they may change 
again before 1.1 becomes a Recommendation.

We understand the goals and purposes which table markers can be used 
for. Nevertheless, in order to implement them properly, we are 
collecting use-cases and examples. A wide range of them will be of great 
help for us to make a fast, reliable and really useful implementation of 
table markers.

Can you describe the task you are working on and the way you will use 
table-markers? We would appreciate if you send a sample FO demonstrating 
the task and approaches.

It could also happen so that table markers are not actually required in 
a particular case. If so, than RenderX engineers or the community of 
this list may come up with a solution w/o table-markers.

-- 
Best regards,
  Michael Sulyaev, mailto:msulyaev at renderx.com
RenderX
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo at renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4294 bytes
Desc: not available
URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20060912/ef4d4e7b/attachment.bin>