{Blank Subject 2011-07-27}

[SindyYoung]

Good Morning All,

I was wondering if there was any way to display information coded as generated text in a text file. The issue is we have a customer who is making up their own rules for cross-referencing and we need to see what they have coded in their FOSI to produce their end results.

Sindy Young
AWACS Tools and Technology Team,
(253) 657-6964
Kent, WA 98032

[naglists]

Hi Sindy,
Not sure about text file output.

But what about "set gentexttagdisplay = full" and then doing a Print Editor
View?

Maybe that's enough to troubleshoot your customer's stylesheet problems
(that's me making some assumptions there 🙂

On Wed, Jul 27, 2011 at 11:10 AM, Young, Sindy R
<sindy.r.young@boeing.com>wrote:

> Good Morning All,****
>
> ** **
>
> I was wondering if there was any way to display information coded as
> generated text in a text file. The issue is we have a customer who is
> making up their own rules for cross-referencing and we need to see what they
> have coded in their FOSI to produce their end results. ****
>
> ** **
>
> Sindy Young
> AWACS Tools and Technology Team,
> (253) 657-6964
> Kent, WA 98032 ****
>

[JasonBuss]

If you're using fosi, this can be done pretty readily with userule in a
usetext (should be under the FOSI help). Supports saving content from a
text var into an external file (*.exp by default). Not sure on Styler,
haven't used it much.

[LynnHales]

Sindy,

Take a look at the oid_gentext() function (help 5708) and the oid_is_gentext() function (help 1263). If you build a simple ACL script, you should be able to traverse the document. Put an if statement in to test if the oid is generated text (equal 1) and if so, then use the oid_gentext() to output the string to a file.

You may have to do some work with the file as the gentext string has a lot of 'overhead' with it.

If you want some help, email me off line.

Lynn
---- "Young wrote:
> Good Morning All,
>
> I was wondering if there was any way to display information coded as generated text in a text file. The issue is we have a customer who is making up their own rules for cross-referencing and we need to see what they have coded in their FOSI to produce their end results.
>
> Sindy Young
> AWACS Tools and Technology Team,
> (253) 657-6964
> Kent, WA 98032
>
> -----End Original Message-----

[ptc-1908075]

Sindy,

If you're using FOSI, information on writing to an external ASCII file is
available in the PDF file
at

Also, you can use \&#RE;\ to force a new line in the external file.

Hope this helps!

Suzanne Napoleon
www.FOSIexpert.com
"WYSIWYG is last-century technology!"

[JasonBuss]

#ELEMNAME? That’s a new one for me, is that in the documentation? I did a quick search, and didn’t come up with anything (unless it was added after 5.3M040)

[ptc-1908075]

Sindy,

If you're using FOSI, information on writing to an external ASCII file is
available in the PDF file
at

Also, you can use \&#RE;\ to force a new line in the external file.

Hope this helps!

Suzanne Napoleon
www.FOSIexpert.com
"WYSIWYG is last-century technology!"

[ptc-1908075]

It's included with other keywords in the PDF file
at

[ptc-1908075]

My apologies for the duplicate email.
Suzanne