Quick FOSI Question

Forum|Forum|15 years ago
November 12, 2010
6 replies
1453 views

We haven't had to change our FOSI in years (aside from slight
modifications) so I'm a bit rusty.

I'm hoping someone might be able to answer this quick question before
I inevitably figure it out.

Given two elements:
<problem id="p_123"><para>This is some
text</para><some-other-elements-here/></problem>
and
<problemref linkend="p_123">

I would like to have the para text from the ID node shown after the
problemref element in Arbortext.

I setup my fosi as follows:

<e-i-c gi="problem">
<charlist charsubsetref="block">
<indent leftind="@12pt" firstln="*"></charlist>
<att>
<specval attname="id" attloc="problem" attval="#ANY">
<charsubset>
<savetext textid="xref-formatted.txt"<br"/>conrule="<problem.fmt>,#CONTENT,</problem.fmt>" xrefidtag="problem">
</charsubset>
</att>
</e-i-c>

<e-i-c gi="problemref">
<charlist inherit="1" charsubsetref="inline"></charlist>
<att>
<specval attname="linkend" attloc="problemref" attval="#ANY">
<charsubset>
<usetext source="#XREF(linkend,xref-formatted.txt)"></usetext>
</charsubset>
</att>
</e-i-c>

Now, the issue I'm having is that #CONTENT gives me all text within
the problem, but I really only want the text within the para. Is
there a simple way to just pull the <para> text?

Thanks in advance,
keith

S

SindyYoung

1-Visitor

Give the para tag an id. The xref out to it. You may have to have two xrefs but it should work.

B

berard

Author

1-Visitor

That's certainly an option, but it might be more tricky since we use
<para> tags all over our content, and there would have to be some ACL
overhead to strip the IDs if copied/pasted into a different context.

As the model works today, when the user tries to insert a <problemref>
tag, they are presented with a dialog that shows all available
problems.

I was hoping there might be more of an xpath-like way to extract just
the content I need.

keith

On Fri, Nov 12, 2010 at 12:58 PM, Young, Sindy R
<sindy.r.young@boeing.com> wrote:
> Give the para tag an id. The xref out to it. You may have to have two xrefs but it should work.
>

L

LynnHales

1-Visitor

Keith,

In your <e-i-c> I'd change the 'gi' from "problem" to "para" and then add a 'context' of "problem". That should gather the text of the paragraph contained in the problem

Lynn
---- Keith Berard <-> wrote:
> That's certainly an option, but it might be more tricky since we use
> <para> tags all over our content, and there would have to be some ACL
> overhead to strip the IDs if copied/pasted into a different context.
>
> As the model works today, when the user tries to insert a <problemref>
> tag, they are presented with a dialog that shows all available
> problems.
>
> I was hoping there might be more of an xpath-like way to extract just
> the content I need.
>
> keith
>
> On Fri, Nov 12, 2010 at 12:58 PM, Young, Sindy R
> <sindy.r.young@boeing.com> wrote:
> > Give the para tag an id. The xref out to it. You may have to have two xrefs but it should work.
> >
>

B

berard

Author

1-Visitor

Aah, perfect!

I stare at "e-i-c" all day, and seldom think to expand it out to
"Element in Context", which does exactly what I need.

Thanks
keith

S

SindyYoung

1-Visitor

Good eye Lynn

L

LynnHales

1-Visitor