stylesheets - Styler vs. Arbortext

[ptc-1123085]

How can Styler stylesheets be converted to Arbortext Editor only stylesheets? problem: In the beginning of the custom app dev cycle, we used Styler to create some of our stylesheets. We are only styling for the Editor and are only concerned with screen output. Now that we are only using Editor, some of the stylings made in Styler are inaccessible. For example, gentext for Arbortext Editor doesn't appear in a stylesheet that was created in Styler but now accessed via Arbortext Editor. The gentext is accesible only through a text editor. Is there any way to convert stylesheets made in Styler to simple Arbortext Editor stylesheets with no <OutputProperties output="editor" tagging?

[BobSpangenburg]

Karen, Styler is required to convert a "Styler" stylesheet into a "FOSI" stylesheet, which is what Editor uses for its screen stylesheet. It's actually not "simpler" then Styler, it's just a different technology. In fact, when you can't do something in Styler, you use FOSI extensions to accomplish the task. Without looking at the Styler stylesheet and building a FOSI stylesheet by hand, I don't know of another method. Styler is an Arbortext-specific stylesheet language, whereas FOSI (Formatted Output SGML Instance" is based on the DOD Output Spec. Though old, it is reliable and powerful for paper output. Arbortext just so happens to also use it for its screen output. Bob

[ptc-1123085]

The problem is that gentext that is created in Styler has markup specifying which kind of output (ie: Editor). Since we only read our text onscreen, we don't need Styler and don't need the options of PDF, Print, Web, etc. Unfortunately we have some stylesheets that were created with Styler but we currently are using the Editor exclusively. Now gentext that was created in Styler becomes 'invisible' in Editor Styler; the gentext appears onscreen, but it is not modifiable in Editor Styler. We would like to convert all of the stylesheets created with Styler to the Editor Styler version, without <OutputProperties>. gentext created in Styler <Element name="dcktlink" style="inline"> <Context priority="0" selector="dcktlink"> <BaseProperties> <Breaks blockOrInline="inline"/> </BaseProperties> <OutputProperties output="editor" propertySetReferences="custom__link"> <GeneratedText> <AddBefore><_sfe:BeforeOrAfterText><_ufe:gentext><_gte:AttributeContent attr="st" occur="1" scope="dcktlink"/> <_gte:AttributeContent attr="n" occur="1" scope="dcktlink"/></_ufe:gentext></_sfe:BeforeOrAfterText ></AddBefore> </GeneratedText> </OutputProperties> </Context> </Element> gentext created in Editor <Element name="dcktlink" style="inline"> <Context priority="0" selector="dcktlink"> <BaseProperties propertySetReferences="custom__link"> <Breaks blockOrInline="inline"/> <GeneratedText> <AddBefore><_sfe:BeforeOrAfterText><_ufe:gentext><_gte:AttributeContent attr="st" occur="1" scope="dcktlink"/> <_gte:AttributeContent attr="n" occur="1" scope="dcktlink"/></_ufe:gentext></_sfe:BeforeOrAfterText ></AddBefore> </GeneratedText> </BaseProperties> </Context> </Element>

[lfraley]

You might be able to get an Advisor to do this for you. It sounds like a quick call to get your problem solved and wouldn't require you to get Styler.

http://www.single-sourcing.com/advisor