About Arbortext Styler > Defining Page Layout > Side by Side Alignment > Considerations when Configuring Side by Side Alignment
  
Considerations when Configuring Side by Side Alignment
Please take the points listed below into consideration when configuring side by side alignment:
• If you are working with FOSI and XSL-FO print/PDF engines some special handling is required to output right aligned side by side positioning. With right alignment, these engines use the left indent and first line indent settings in the Indent category to determine the left edge of the current (aligned) element. They ignore the Horizontal offset value in the Side by side category. PTC ALD and HTML use the Horizontal offset and Width values on the Side by side category to determine the left edge of the right aligned element. You will need to use FOSI or XSL-FO edited source to set the left indent to the required value if you want FOSI or XSL/FO print/PDF output to work in the same way as in HTML or PTC ALD print/PDF outputs from the same stylesheet.
• Nested alignment groups do not format correctly when working with the FOSI and XSL-FO engines.
• Side by side settings are only supported for an element that has a Structure type of Block. Arbortext Styler attempts to enforce this by disabling the Side by side controls if the element being styled appears to be inline.
It can be difficult to confirm the structure type when property sets apply for the element, as more than one can apply in a given instance. It may be the case that side by side formatting is applied to an inline element. When working with HTML outputs, this can lead to unexpected results. You can try and mitigate this:
◦ Avoid setting side by side properties directly on the element that is expected to be inline.
◦ Use context and conditions to avoid setting side by side properties in Property Sets when the element would also be inline (either by Property Set or by direct assignment).
• If any HTML outputs are configured to create CSS rules for property sets, side by side properties should also be specified in a property set. Side by side properties set in a context or condition will cause HTML/CSS defects to be reported.
Refer to Styling HTML Files from Different Document Types for information on creating CSS rules for property sets.
• When working with HTML outputs, some browsers ignore a Yes value for End previous alignment on some elements, but obey it on others. The behavior is not consistent among browsers. It may be necessary to experiment with configuring the setting for multiple elements, or using End all contained alignments to prevent problems. This limitation can be seen in the procedures/procedure_left and procedures/procedure_right sample documents in the samples directory. Refer to procedures/about_procedure_samples.xml for further information.
• When working with HTML outputs, setting End previous alignment to Yes will usually end all previous alignments. Sometime it has no effect. This creates limits on what can be done with nested alignments.
• Refer to Differences in Behavior of Indent Settings Between Outputs in Side by Side Category for a list of differences in effect of the side by side properties between the various possible outputs.