Volodymyr Mykhailyk wrote:
> Hi,
> Actually I am not sure you will be able to do such work-around. It will
> take too much time, and can give no results.
> I think it better to increase memory size used by xep.
I agree that tables are really your only choice here. The only other
thing that might possibly work would be to use side floats for the stuff
on the edges.
You didn't say if each of your examples is coded as a single table or as
one giant table. If the latter then make each one a separate table: that
should produce a much lower memory load than one giant table (assuming
that XEP can free up a table's memory once it's been placed on a page).
Or break your job up into chunks that you can then concatenate together
after XEP processes them. Of course this will only work if you don't
need to do page number citations across chunk boundaries.
Cheers,
Eliot
-- W. Eliot Kimber Professional Services Innodata Isogen 9390 Research Blvd, #410 Austin, TX 78759 (214) 954-5198 ekimber@innodata-isogen.com www.innodata-isogen.com ------------------- (*) To unsubscribe, send a message with words 'unsubscribe xep-support' in the body of the message to majordomo@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.htmlReceived on Mon Jul 31 08:51:55 2006
This archive was generated by hypermail 2.1.8 : Mon Jul 31 2006 - 08:51:59 PDT