You can single-source styles through the use of style sheet mediums.
One use for a medium is to have one group of style settings for online formats (DotNet Help, HTML Help, WebHelp, WebHelp Plus, WebHelp AIR) and a different group of settings for print-based formats (Adobe PDF, XHTML, Microsoft XPS, Microsoft Word, Adobe FrameMaker). Therefore, you could use one medium for your online targets and use another medium for PDF and your other print-based targets.
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 style sheet 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 style sheet 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 style sheet 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 tag 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.
Following are the tasks that you might perform when working with style sheet mediums.
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 Style Sheet Mediums.
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).