1-Visitor

Question

change bars identifying a new table that breaks to new page don't identify table continuation

Forum|Forum|14 years ago
January 11, 2012
20 replies
2995 views

Make sense? The table title on the first page of the table has change bars.
When the table runs across onto a second page, the repeat title living in a
float is not change barred.

Has anyone been asked to change this behavior before? How'd you do it?

--
Paul Nagai

Show previous replies

naglists

Author

1-Visitor

It is only in the touchup e-i-c.

And to be clear this (floated table title continuations) is the only error
I'm aware of. The remainder of the touchup coding/functionality has been
working as we expect for a very long time.

Actually, all three of my floats, do not reflect change bars. So I should
probably say change bars on floats is the only touchup problem I'm aware of.

On Wed, Jan 11, 2012 at 2:49 PM, Suzanne Napoleon <
SuzanneNapoleon@fosiexpert.com> wrote:

> Paul,
>
> I'm not sure what Help 537 means either, but I don't think it applies. There
> is no issue with merging a chgmark in a charsubset with a chgmark in a
> charlist. Chgmark is coded just once. Hmmm ... is chgmark coded in the
> docdesc?
>
> Suzanne
>

ptc-1908075

1-Visitor

FWIW: My testing is in 6.0.
Suzanne

naglists

Author

1-Visitor

sheepishly: 5.3 m110. (I should have reported THAT much earlier, too.)

I'm moving on. Thanks for everyone's thoughts/time. If post-upgrade (next
few months, I hope), things change, I'll update this thread.

On Wed, Jan 11, 2012 at 3:23 PM, Suzanne Napoleon <
SuzanneNapoleon@fosiexpert.com> wrote:

> FWIW: My testing is in 6.0.
> Suzanne
>

ptc-1908075

1-Visitor

Paul,

I encourage you to file this with tech support and see what they say. If it's a bug, maybe you'll get a fix or a workaround.

Suzanne

BobSpangenburg

1-Visitor

Paul,

To reiterate what Andy eluded to, I don't see where you're loading the title content into the variable you use in your float. Are you sure the touchup wrapper is getting into that variable to be used within the float?

Though I'm only familiar (off the top of my head) with the CPD product, everywhere I want change bars to show up, I have to wrap it with the code that causes the change bars. This includes the floats.

In each of your FOSI snippets, I didn't see where your titletext content was being wrapped or pushed through to the float usetext. I haven't had any problems that I'm aware of in having a change bar within a float and I'm still using 5.3 M060.

Just a thought.

Bob

naglists

Author

1-Visitor

I missed Andy's suggestion, if that's what he was getting at. So you're
saying I need to specifically resolve context of touchup and explicitly
insert that markup again into the float because when the float content is
(re)called, it resolves as not in context of the original touchup? If
that's the solution, I'll push back with my authors.

Resolving elements context of touchup requires system-funcs. I don't want
to do that on title in table.

Further, I "forced" chgmark on the e-i-c associated with the float (without
resolving context just to look at the formatting side). The change bar
displays but there is a break between it and the change bar being generated
"automatically" on the table itself. I'm not sure if I can "close" that gap
or not.

... unless I'm still missing the context of touchup advice you all are
trying to give me.

My original understanding of float was that any output of the <att> floated
goes to the float and is in-context of where it was when saved to the
float. So, in the att below, it is true, the title value is saved earlier
in the title e-i-c and I do not explicitly test for context of touchup nor
do I insert touchup into the savetext or use chgmark here on the att's
usetext. I *think* from what Suzanne has been saying (her markup doesn't
show any explicit use of chgmark or saving of touchup markup either) is
that for her, the change bars are showing up on her floated continued
chapter title because the chapter title itself is in change barred content.
Maybe I have misunderstood her, too. Anyhow, it seems to me that the
floated content shows up outside of the main flow as far as context goes
and therefore is not change barred and I have misunderstood you all
including Suzanne OR there is a bug in 5.3 m110.

<att>
<specval attname="print-only" attloc="system-var" attval="#ANY">
<specval attname="landscape" attloc="table" attval="yes">
<specval attname="enumerated" attloc="table" attval="yes">
<charsubset>

<usetext source="<bold">,tableusect.txt,
</bold>,<tablespace>,</tablespace>,table-title.txt,\ (continued)\">
<subchars>
<indent leftind="1.05in" firstln="*-1.05in">
<postsp minimum="5pt" nominal="5pt" maximum="5pt" condit="keep"<br"/>priority="med">
<keeps next="7">
<textbrk startln="1" endln="1">
<float flidref="table-float.top" width="page" scope="table"<br"/>pagetype="afterref">
<enumerat increm="1" enumid="tablepagect">
<savetext textid="tablepagect.txt" conrule="tablepagect">
</subchars>
</usetext>
</charsubset>
</att>

On Thu, Jan 12, 2012 at 8:14 AM, Bob Spangenburg <
-> wrote:

> Paul,
>
> To reiterate what Andy eluded to, I don't see where you're loading the
> title content into the variable you use in your float. Are you sure the
> touchup wrapper is getting into that variable to be used within the float?
>
> Though I'm only familiar (off the top of my head) with the CPD product,
> everywhere I want change bars to show up, I have to wrap it with the code
> that causes the change bars. This includes the floats.
>
> In each of your FOSI snippets, I didn't see where your title text content
> was being wrapped or pushed through to the float usetext. I haven't had any
> problems that I'm aware of in having a change bar within a float and I'm
> still using 5.3 M060.
>
> Just a thought.
>
> Bob
>

BobSpangenburg

1-Visitor

Paul,

The content of your varaible "table-title.txt" would contain the begining and end of your change bar markup, in your case, the PI. In all the code I use, I have two variables: "scontent.txt" and "econtent.txt". These two variables are normally a null. When change bars are needed, they get filled at the e-i-c, with the change mark up if it is applicable.

However, in your case, if the title element already has the markup in the content of the <title> tag, it should be passed along to the float. The markup you're using (PI's) should then, using their own e-i-c, trigger change bars. I'd have to play with it to see why you're not getting them, since I think you mentioned early on that you were getting the bars on the first title.

Let me know and I'll see if I can get a 'non-CPD' version working to show this.

Oh, to your note about the gap... most likely, you're getting it because you're showing the bar on the content of the header row, not the row itself. When change bars are "joined," they have to be adjacent elements. There is a difference between marking the content of the row and the row itself. When multiple rows are added or deleted and marked, they'll showa solid change bar. If the content of the sames rows are deleted, but the row is left in tact, you'll get broken change bars.

HTH,

Bob

naglists

Author

1-Visitor

Thanks for the clarifications, Bob. I have used
element_or_condition_name_change_bar_start.txt and
element_or_condition_name_change_bar_end.txt in other instances, so I
understand that technique.

The root of my problem appears to result from the fact that I do not test
for touchup and explicitly call out chgmark at the e-i-c of any element.
The *only* chgmark I emit anywhere is from the e-i-c for touchup itself.
(We used to support change highlighting withing change bars, so that's how
I know it requires a system-func to detect touchup in context="* touchup".)

I was initially expecting that the composition engine would resolve the
float output as being in context of touchup since it is called from (and,
frankly, emitted in ... it appears to me) context of touchup. However, this
"lack" of context is true even when the entire h2 owning the table that
breaks across pages is wrapped by touchup tags. (So the gap is not the
result of only having change bars on the header text, not the row ... my
entire table is wrapped ... but in the XML content, not in my stylesheet
... and if I look closely at the output ... it appears as though the change
bar starts after the initial rule of the table header on the second page of
the table. So I now conclude that floats are "outside" the normal flow /
context at least as far as the touchup PI is concerned.

Here is an example XML psuedo-instance:
...

<h2>
<title>my h2 title</title>
<para>...</para>
<table>
<title>my table title</title>
...tgroup/colspecs/thead/tbody all go here
</table>
<para>...</para>
<newpage/>
<para>...</para>
</h2>

...

The resulting change bar is completely solid on page 1 beginning with the
title of the h2 and continuing to the last rule of the last row of the
table that fits on the page. On page 2 the change bar begins, it appears,
AFTER the first rule of the table header ... which is well after the table
title continuation ... the piece that floated. If I force a change bar on
the floated information, there is a gap after the baseline of the table
title continuation until just after the first rule of the table header.

On page 2, the change bar, once it starts is continuous to the baseline
after the post-table paragraph.

On page 3, the change bar continuously marks the post-newpage paragraph.

With the exception of the "force" test of chgmark on the float, all of this
is achieved, stylesheet-wise, by the previously included excerpts. The
<att> that floats. And the e-i-c for touchup.

Out of the box Editor change tracking, converted by an ACL to touchup PI
markup (and another ACL to remove it), controls the change bar from an
authoring perspective.

On Thu, Jan 12, 2012 at 11:31 AM, Bob Spangenburg <
-> wrote:

> Paul,
>
> The content of your varaible ??????"table-title.txt" would contain the
> begining and end of your change bar markup, in your case, the PI. In all
> the code I use, I have two variables: "scontent.txt" and "econtent.txt".
> These two variables are normally a null. When change bars are needed, they
> get filled at the e-i-c, with the change mark up if it is applicable.
>
> However, in your case, if the title element already has the markup in the
> content of the <title> tag, it should be passed along to the float. The
> markup you're using (PI's) should then, using their own e-i-c, trigger
> change bars. I'd have to play with it to see why you're not getting them,
> since I think you mentioned early on that you were getting the bars on the
> first title.
>
> Let me know and I'll see if I can get a 'non-CPD' version working to show
> this.
>
> Oh, to your note about the gap... most likely, you're getting it because
> you're showing the bar on the content of the header row, not the row
> itself. When change bars are "joined," they have to be adjacent elements.
> There is a difference between marking the content of the row and the row
> itself. When multiple rows are added or deleted and marked, they'll show a
> solid change bar. If the content of the sames rows are deleted, but the row
> is left in tact, you'll get broken change bars.
>
> HTH,
>
> Bob
>

ptc-1908075

1-Visitor

Paul,

Does the document contain this:

<title>Whatever</title>

or this:

<title>Whatever</title>

The firstincludes _touchup with #CONTENT when it is saved to table-title.txt. So the change bar floats with the content.

The second would require different FOSI coding to support floated change bars, assuming it is possible with this markup combination.

Suzanne

naglists

Author

1-Visitor

Got it.

Thanks for the help, everyone. Sorry it took so long to get the message
through!

On Thu, Jan 12, 2012 at 12:08 PM, Suzanne Napoleon <
SuzanneNapoleon@fosiexpert.com> wrote:

> Paul,
>
> Does the document contain this:
>
> <title>Whatever</title>
>
> or this:
>
> <title>Whatever</title>
>
> The first includes _touchup with #CONTENT when it is saved to
> table-title.txt. So the change bar floats with the content.
>
> The second would require different FOSI coding to support floated change
> bars, assuming it is possible with this markup combination.
>
> Suzanne
>

Sign up

Please use your PTC eSupport account.

Welcome to the PTC Community

Please use your PTC eSupport account.

Scanning file for viruses.

This file cannot be downloaded