Boxing across multiple pages

sylvain.castong2 · ‎Sep 25, 2006

Hi Adepters,

Can anyone confirm if starting Editor 5.0 boxed elements
can be broken over multiple pages?

Thanks

Sylvain Castonguay

BRP

From: Gail McCants

Sent: 25 septembre, 2006 11:32
To:
Archives
Subject: Re: Epic Preferences

Good morning Adepters,

Is there a way to limit the number of
characters an author enters into a particular element? We want to limit the
number of characters entered in a title field to stop at 100. We have our own
customized DTD so making changes in the FOSI is not a problem. Thanks in
advance,

Gail McCants
TSYS Product and Knowledge Development

sylvain.castong2 · ‎Sep 25, 2006

Hi Adepters,

Can anyone confirm if starting Editor 5.0 boxed elements
can be broken over multiple pages?

Thanks

Sylvain Castonguay

BRP

From: Gail McCants

Sent: 25 septembre, 2006 11:32
To:
Archives
Subject: Re: Epic Preferences

Good morning Adepters,

Is there a way to limit the number of
characters an author enters into a particular element? We want to limit the
number of characters entered in a title field to stop at 100. We have our own
customized DTD so making changes in the FOSI is not a problem. Thanks in
advance,

Gail McCants
TSYS Product and Knowledge Development

lhales · ‎Sep 25, 2006

Sylvain,

If you mean an element that is wrapped by a box, I believe the answer is
no. The on line help (help 179) in the second paragraph is pretty
explicit. "one box cannot exceed one page". If you want some additional
info, take a look in the 28001 tutorial in the Epic\tutorials\28001
folder. Use the Epic 'find tag/attribute' feature and find and ID with a
value of "boxing" (hey I was being original ok).

Lynn

sylvain.castong2 · ‎Sep 25, 2006

Thanks Lyne,

Now here's my issue: I have a troubleshooting section with symptom,
possible_cause and what_to_do tag structure where I would like to have 3
columns table output in the PDF. The goal is to avoid our technical
writers to fiddle with table settings in Editor and page breaks (which
can be very confusing especially when merging tables from different
writers) and let FOSI do the formatting. Eventually the troubleshooting
section will be available in another completely different format on the
web. So we want to eliminate manual page breaks and other manual
formatting.

Any suggestions?

Sylvain Castonguay
BRP

naglists · ‎Sep 25, 2006

> Now here's my issue: I have a troubleshooting section with symptom,
> possible_cause and what_to_do tag structure where I would like to have 3
> columns table output in the PDF. The goal is to avoid our technical
> writers to fiddle with table settings in Editor and page breaks (which
> can be very confusing especially when merging tables from different
> writers) and let FOSI do the formatting. Eventually the troubleshooting
> section will be available in another completely different format on the
> web. So we want to eliminate manual page breaks and other manual
> formatting.>
> Any suggestions?

Where our customers have insisted on this sort of formatting, we have
said: Either you manage the tables (and rules and breaks) yourself or
fund the development of pagesets that contain the boxes and live with
the inherent limitations / inflexibility of that sort of formatting.
They've chosen to manage the tables themselves. It's as painful as we
told them it would be, if not worse, but they get exactly what they
want ... in print. Online versions are clunkier than they would be if
their content were stored in semantic XML paired with print and online
stylesheets instead of generic table elements.

ptc-1908075 · ‎Sep 25, 2006

Boxing does not break at columns or pages unless deepcontentsplitting is on. When deepcontentsplitting is not on, boxed content oversets off the bottom of the page, usually followed by other content. In Preview, use View->Options->Extended Pages to see what is off the page

Deepcontentsplitting is available in 5.0. However, there have been problems with it. The 5.2 release notes list several bugfixes related to deepcontentsplitting. However, I have not worked with deepcontentsplitting in 5.2.

Adepters: What's your experience?

Hope this helps.

Good Luck!

Suzanne Napoleon

www.FOSIexpert.com

In a message dated 9/25/2006 2:40:57 PM Eastern Daylight Time, Sylvain.Castonguay@brp.com writes:

Hi Adepters,

Can anyone confirm if starting Editor 5.0 boxed elements can be broken over multiple pages?

Thanks

Sylvain Castonguay

BRP

ptc-1787870 · ‎Sep 26, 2006

Some of our documents do not compose when deepcontentsplitting is on. I'm
still forcing it off until it works better.

I've also been watching the release notes closely and noting that a fair
number revolve around deepcontentsplitting.

Regards,
Jason

StudentWP@aol.com
09/25/2006 06:45 PM
Please respond to
<adepters@arbortext.com>

To
sylvain.castonguay@brp.com, adepters@arbortext.com
cc

Subject
Re: Boxing across multiple pages

Boxing does not break at columns or pages unless deepcontentsplitting is
on. When deepcontentsplitting is not on, boxed content oversets off the
bottom of the page, usually followed by other content. In Preview, use
View->Options->Extended Pages to see what is off the page

Deepcontentsplitting is available in 5.0. However, there have been
problems with it. The 5.2 release notes list several bugfixes related to
deepcontentsplitting. However, I have not worked with deepcontentsplitting
in 5.2.

Adepters: What's your experience?

Hope this helps.

Good Luck!
Suzanne Napoleon
www.FOSIexpert.com

In a message dated 9/25/2006 2:40:57 PM Eastern Daylight Time,
Sylvain.Castonguay@brp.com writes:
Hi Adepters,

Can anyone confirm if starting Editor 5.0 boxed elements can be broken
over multiple pages?

Thanks

Sylvain Castonguay
BRP