FOSI boxing and alignment groups?

[ptc-953343]

I'm having a problem with getting an alignment group to work with boxing.
I have a typical chapter with markup like this:

<chapter><title>CHAPTER TITLE</title>
<section><title>Head 1 title</title>
...
</section>
<section><title>Head 2 title</title>
...
</section>
</chapter>

This is not goign to be reporduced like a typical chapter title setup.
Instead I have to do something like this

[ptc-1908075]

In general, suppress and save the content, output the variables from formatting
pseudo-elements with algroup that align material that has been boxed by
formatting pseudo-elements. If I remember correctly, you need to be sure the
e-i-c with boxing is coded as a block element. On the other hand, if i remember
correctly, the formatter assumes a block textbrk for algrouped stuff.

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

[ptc-953343]

The problem was the nesting, trying to apply the boxing to the outer
element, then do the alignment. The alignment group seems to have an
implied blocking to it.

So I moved the boxing to the psuedo elements but that changed how the
boxing worked. It seems like it inherited some indents on the psuedo
elements that weren't there when I just formatted the title element.

..dan

> In general, suppress and save the content, output the variables from
> formatting
> pseudo-elements with algroup that align material that has been boxed by
> formatting pseudo-elements. If I remember correctly, you need to be sure
> the
> e-i-c with boxing is coded as a block element. On the other hand, if i
> remember
> correctly, the formatter assumes a block textbrk for algrouped stuff.
>
> Good Luck!
> Suzanne Napoleon
> www.FOSIexpert.com
> "WYSIWYG is last-century technology!"
>
>
>

[ptc-1908075]

In general, you want formatting pseudo-elements to inherit. Otherwise the
sources of missing characteristic values becomes too complicated.

[ptc-953343]

> In general, you want formatting pseudo-elements to inherit. Otherwise the
> sources of missing characteristic values becomes too complicated.
>
> BTW: Keep in mind that boxing is an overlay. It does not add any
> horizontal or
> vertical space, regardless of the boxing offset values.
>
> Suzanne
>
>
>

I found part of my boxing problem, I had values set at the e-i-c level and
then within an attvalue. That was making the offset values not change as
teh second instance was overriding my changes.

I think my difficult problem is going to get these 2 side by side boxes to
size the same and fill the full space. I'm thinking this isn't going to be
possible unless I pad the titles with non-printing characters.

What I'm seeing is this:

[steve.thompson4]

You started this exchange by referring to boxing. Is that the only thing that will give you what you need? Is the location for the box (this is a chapter and/or section title, so maybe somewhat consistent) going to vary from page to page? Even if it does, any possibility of using a region?

Haven't used them much myself, but do know they have a background color available, are 'sizable', and the 'size' is not dependent on the content inserted.

Just a thought.

Steve Thompson
+1(316)977-0515

[ptc-953343]

Regions look like they have to be in the same area everytime and the same
size. I might get away with this if it was always one line or always two
lines, but it varies - I need the vertical size to change to the pargest
content, the horizontal to always be full width and split evenly. Sounds
like region has some of the features I need though.

I thought tables were going to do it for me instead of boxing, but I
forgot you can't use attributes in psuedo elements. This table would do
the trick if I could figure out a way to code it:

<table>
<tgroup cols="2"><colspec colname="col1"&lt;br"/>colwidth="2.00in"/><colspec colname="col2"&lt;br"/>colwidth="2in"/>
<tbody><row><entry valign="top">Shading="#000000"?>Aircraft Fire on Deck </entry>
<entry valign="top">Ground Emergencies</entry>
</row></tbody>
</tgroup>
</table>

I was going for the boxing and alignment group as all the section titles
have a similar formatting. The first one requires the use of the alignment
group and appending the chapter title, otherwise they are all the same,
falling wherever on the page.

..dan

> You started this exchange by referring to boxing. Is that the only thing
> that will give you what you need? Is the location for the box (this is a
> chapter and/or section title, so maybe somewhat consistent) going to vary
> from page to page? Even if it does, any possibility of using a region?
>
> Haven't used them much myself, but do know they have a background color
> available, are 'sizable', and the 'size' is not dependent on the content
> inserted.
>
> Just a thought.
>
> Steve Thompson
> +1(316)977-0515
>

[BobSpangenburg]

Dan,

Have you tried building the table on the fly using the FOSI? Each title would fill a forward-looking variable scoped to the element containing the titles. Assuming you always have a primary title, it would be the element to build the table and print it after the primary title. Both titles would have their content suppressed. When the table is built, the variables would place the content of the title tags into the entry for each column. Since it's a table, it's always the same size, as well as having the background filled in.

Fromyour previous post:

source="!<table><tgroup cols="2"><colspec colname="col1" colwidth="2.00in"/">
<colspec colname="col2" colwidth="2in"/"><tbody><row>
<entry valign="top">!,prtitle.txt,!</entry>
<entry valign="top">!,sectitle.txt,!</entry>
</row></tbody></tgroup></table>!"

The "!" symbols are important for the coding.

Hope this helps,

Bob

[ptc-953343]

Thanks, I should have closed this out. Suzanne sent me a link to her site


I was trying to generate the table as pseudo elements and not getting
anywhere with that approach.

..dan

> Dan,
> Have you tried building the table on the fly using the FOSI? Each title
> would fill a forward-looking variable scoped to the element containing the
> titles. Assuming you always have a primar...

[BobSpangenburg]

Hey Dan,

Yeah, the "!" symbol tells the stylesheet not to process the "<" as an element, but to keep it as text. Then, when it's used, it's actually an element.

Glad you're on your way with this.

Bob

[ptc-3050150]

We just put together a few thousand work packages into a book and for the first time get to see a full list of the bad ID/ID Refs...and it is insane. Is there some way to get that window exported to a, well, anything other than Print Screen?

Excel, text, csv, even printed to PFD...anything that could be cut and pasted?

We are using 5.4 M040

John T. Jarrett CDT
Senior Tech Writer, Integrated Logistics Support,Land & Armaments/Global Tactical Systems

T832.673.2147 | M 832.363.7234 | F 832.673.2376| x1147 | -
BAE Systems, 5000 I-10 West, Sealy, Texas USA 77474
www.baesystems.com

[bibach]

John,

Try something like this at the command line: show ids output=C:\myids.txt

It's just a simple text file and doesn't have a lot of information,
but it might serve your needs, with a little slicing and dicing.

-Brandon


On Thu, Sep 9, 2010 at 2:58 PM, Jarrett, John T (US SSA)
<-> wrote:
> We just put together a few thousand work packages into a book and for the first time get to see a full list of the bad ID/ID Refs...and it is insane. Is there some way to get that window exported to a, well, anything other than Print Screen?
>
> Excel, text, csv, even printed to PFD...anything that could be cut and pasted?
>
> We are using 5.4 M040
>
> John T. Jarrett CDT
> Senior Tech Writer, Integrated Logistics Support,Land & Armaments/Global Tactical Systems
>
> T832.673.2147 | M 832.363.7234 | F 832.673.2376| x1147 | -
> BAE Systems, 5000 I-10 West, Sealy, Texas USA 77474
> www.baesystems.com
>