[xep-support] Re: technical help

From: Kevin Brown <kevin_at_ADDRESS_REMOVED>
Date: Wed Apr 01 2015 - 09:28:28 PST

You should be able to do this with a float.

See samples at http://www.renderx.com/usecasestest.html

Specifically side floats and marginalia

 

Kevin Brown

RenderX

 

From: David Yin [mailto:David.Yin@PACCAR.com]
Sent: Wednesday, April 01, 2015 10:01 AM
To: kevin@renderx.com; 'RenderX Community Support List'
Subject: RE: [xep-support] technical help

 

Much of the nature of our business needs an image to reside next to the
fo:block. And in the case of <task> an image really should go next to the
<ol.li>.

 

I think we can forego the span all columns, I have been playing with a new
format with 1 column, indented in, and having the images appear to the far
left. It works great for <concept> topics but not so great for <task>
topics.

 

The footnote would be nice if I can position the footnote space next to the
line and to the left. Top and bottom are not real functional.

 

-David Yin

 

From: Kevin Brown [mailto:kevin@renderx.com]
Sent: Tuesday, March 31, 2015 12:16 PM
To: 'RenderX Community Support List'; David Yin
Subject: RE: [xep-support] technical help

 

David:

 

Yes, either rx:flow-section or fo:block span="all" must be a direct child of
fo:flow.

I can understand the complexity to flatten things so that you end a flow and
start a new sub-flow, but there is no other alternative if you are using
these structures.

 

One question: Must the image you wish to place across all three columns be
located wherever it falls in the flow? Or could it be at an alternate
position?

If an alternate position on the page (like in the footnote area) is
acceptable, then you can just use a footnote structure which can occur
anywhere in the flow content at any depth and it is pulled into the footnote
area. You could place your image (and figure title) in this structure and it
would be page wide at the bottom of the page.

 

If you have flexibility in that you can define the page master this page
would occur on, then you also have the option of placing it into a marker
and pulling it to the top of the page. This also could occur at any level in
the hierarchy but would require that specific page to regions large enough
to accommodate the image.

 

Kevin Brown

(650) 327-1000 Direct

(650) 328-8008 Fax

(925) 395-1772 Mobile

skype:kbrown01

 <mailto:kevin@renderx.com> kevin@renderx.com

 <mailto:sales@renderx.com> sales@renderx.com

 <http://www.renderx.com/> http://www.renderx.com

 

 

 

From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf Of
David Yin
Sent: Tuesday, March 31, 2015 6:09 AM
To: xep-support@renderx.com <mailto:xep-support@renderx.com>
Subject: [xep-support] technical help

 

I have been posting on the DITA yahoo users group but the suggestion was for
me to ask this board instead since I am looking at a specific functionality
of renderX.

 

There is a Kevin Brown on the forum that has been responding to those posts.

 

I am an intermediate user in DITA, working on a pilot project over the last
3 years.

 

I am trying to use the <rx:flow-section> element to allow a graphic, buried
down inside a topic, nested into a topic, nested into a bookmap, to use up
all 3 columns in a 3 column page.

 

I have been able to get the element to work where the minitoc is 1 column
and the chapter itself is 3 columns. I have not been able to get the
rx:flow-section down to the block level for the placeImage template.

 

I feel like commons.xsl has to be re-written to flatten everything into its
own fo:flow and then only the graphic gets placed as a fo:block.

 

Need help.

 

Thanks.

David Yin

Peterbilt Motors - Customer Service | Service Publications Manager |
940.591.4196 | david.yin@paccar.com <mailto:david.yin@paccar.com>

 

_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
Received on Wed Apr 1 09:24:46 2015

This archive was generated by hypermail 2.1.8 : Wed Apr 01 2015 - 09:24:51 PST