About Stylesheet Mediums

example

Let's say you have text hyperlinks that are shown in blue font with an underline. That may be fine for Target A, but let's say you want this style to appear in black font with no underline for Target B. The solution is to use a stylesheet medium.

Suppose Target A is using the "default" medium, where the blue underline properties are specified. With the properties for Target A already set, you now need to specify style properties for Target B. Therefore, in the Stylesheet Editor, instead of selecting the "default" medium, you can select another medium (e.g., the "print" medium) and change the properties for the style to black with no underline. It's the same stylesheet and the same style that you are working with. The only difference is that one medium is telling Flare to display that content in blue with an underline, and the other medium is telling it to use black font with no underline. With Target A using the default medium and Target B using the other medium, the content will display appropriately in each output.

Flare provides you with the following stylesheet mediums. These are enough to satisfy the needs of most authors, but you can create additional mediums if necessary.

• default This is the standard medium. Any settings that you specify in the default medium "trickle down" automatically to the other mediums. However, you can override any setting in a specific medium.

  example

  Suppose you are using four different mediums (default, print, non-print, CustomA) in your project. Let's say you specify that the font color for the p style in the default medium should be red. If you were to then open any of the other three mediums, you would see that the font color for the <p> tag in each of those is also red. If you were to open the print medium and change the font color for the <p> tag to blue, that is the color that will be used for that medium. However, the <p> tag will continue to be displayed in red for the default, non-print, and CustomA mediums.

• print This medium is designed to be used for print-based output types (Adobe FrameMaker, Adobe PDF, Microsoft Word, Microsoft XPS, XHTML). When you create a print-based target, this medium is automatically associated with it (although you can select a different medium for the target if necessary).
• non-print If you are creating online output and do not want to use the default medium for it, you can use this medium instead. For example, you might want to use the default medium for three online targets that you are working on, but you want to create a fourth online target that uses a different set of styles. In that case, you can use the non-print medium for that fourth target (or you can create custom mediums if necessary).

Page layouts render content using the Print medium settings in the stylesheet. See About Page Layouts.

example

Let's say you have a style called "p.Section" and you apply this style to the text you have in a header frame in a page layout. In the Default style medium, the font color for this style is black, but in the Print medium it is red. It makes more sense to display the font for a page layout based on the Print medium, because that medium will most likely be used in the print-based output. Therefore, the text displays as red in the page layout.

Different mediums in a CSS are set apart by the @media rule and sets of curly braces. This can be seen when you open the stylesheet source file; to do this, navigate to the CSS file in the Content Explorer, right-click on it, and select Open with>Internal Text Editor.

The placement of the medium section in the stylesheet affect which styles are used when you print topics. For example, if you are using the print medium and want those styles to be used when printing a topic from a web browser, the @media print section should be placed in the stylesheet after your default media section, because style properties lower in a CSS take precedence over properties placed above them. You can always move the medium sections around in the stylesheet (if you want them to be placed higher or lower in the file) by cutting and pasting them in the Internal Text Editor.

For more information about mediums in a CSS, see http://www.w3.org/TR/CSS2/media.html.

Following are the tasks that you might perform when working with stylesheet mediums.

• Select in Editor When you are modifying the properties of a style in the Stylesheet Editor or when you are working in the Table Style Editor, you need to let Flare know which medium your settings should be applied to. To do this, select the medium from the Medium drop-down list in the editor, then set the style properties as necessary. See Selecting Stylesheet Mediums.
• Select in XML Editor Flare lets you use two different layout modes when working in the XML Editor: Web Layout mode and Print Layout mode. The "default" and "print" mediums are tied to these two layout modes. This simply means that when you are working in Web Layout mode, the XML Editor displays the styles specified in the default medium. But if you switch to Print Layout mode, the XML Editor automatically displays the styles specified in the print medium. This is simply a way to let you see your content in the format that you are most likely concerned about at the moment. Of course, you can always select a specific medium in the XML Editor when using either layout mode. See Selecting Stylesheet Mediums and About Layout Modes.

• Create You may very well be able to meet all of your style editing needs by simply using the mediums provided by Flare (default, print, non-print). However, if necessary, you can add as many new custom mediums as you need. See Creating Stylesheet Mediums.

  note

  Note: Although the application provides a medium called "print," you might find it useful to create a custom medium for print output, rather than using the "print" medium provided. There are benefits to using the print medium provided by the application, and there are other benefits to creating a custom medium. For example, if you want page breaks before a particular heading for print output, but not when users send online topics to the printer, it is a good idea to create a custom print medium. The reason for this is that browsers respect the settings in the "print" medium provided by the application. Therefore, even though your online output style medium does not have page breaks set before that heading, the application will see that you DO have a page break specified in the print medium. And when a user tries to print a topic from your online Help, the printer will start a new page at that heading. The solution is to create a custom print medium (perhaps calling it "PDF" or "XPS"), specifying page breaks in that medium, and using it for your print output (instead of using the "print" medium provided by the application).

• Associate With Targets After you decide on a medium to use for output, you need to associate it with the target. After you build the target, the medium will be used to display the correct style settings in the output. See Associating a Medium with a Target.