You can define two different sets of attributes for every style: One for electronic help formats (HTML Help, WebHelp, Visual Studio Help and eWriter Help) and one for print-style output (PDF, printed manuals, Word DOCX and ePUB and Kindle Mobi eBooks).
Share stylesheets across multiple projects with style repositories
If you manage multiple projects that all need to look the same, check out Help+Manual's powerful style repositories. They allow you to share stylesheets between multiple projects and edit the styles for all of them in the same central location. See the Working with Style Repositories chapter for details!
It is important to understand that the formatting of the text in the topic header box above the topic editor is handled differently in PDF and DOCX output. The formatting of the main text in the editor is exported to PDF and DOCX and used there. The formatting of the topic header is not exported – only the plain text is exported and the formatting is defined in the PDF or DOCX template.
This is necessary because in PDF and DOCX you can define different formatting for the headings on different levels. This formatting can only be defined in the template, since you don't have multi-level formatting definitions in your project.
You can't influence header formatting in PDF and DOCX from your project
What this means is that you can't influence the formatting of topic headers or TOC entries in PDF and DOCX from your project. All the header formatting in these two document types is defined in the PDF and DOCX templates, not in your project.
|
1.Select in the tab.
2.Select Normal, as most other styles are usually based on this style. You will need to edit any styles not based on Normal separately).
3.Change the font settings in the Print View and Help View tabs. Deselect Same options as help view in the Print View tab to edit the print style settings.
4.Repeat for any styles not based on Normal – these are styles that are not shown as "sub-branches" of Normal in the style tree. |
You can also create completely different layouts for electronic and print output, with a completely different appearance for all your styles in each format. However remember that you can only redefine the attributes of existing styles for each output format. You cannot have different styles for each format because the styles are attached to your text by name. There is only one list of styles, but each style can have two different definitions.
•Proceed as described above and edit all the style attributes you want to change for each output format – you can define separate font, paragraph, border and background settings for each view. |
If you define print view style attributes they will be used in Kindle Mobi and ePUB eBooks. For technical reasons, eBook files work better when they have their own styles and fonts defined for them specifically. Among other things, it may be sometimes be necessary to define special font names for use in your ePUB eBooks (for example for eBooks aimed at Apple iBooks on iOS devices, which have different standard fonts available). Please see Managing Fonts in ePUB for more details.
|
You can zoom the entire contents of the editor quickly with the Zoom control in the status bar below the editor window. This control is also available in the tab in the ribbon toolbar.
You can also switch the editor display between the styles defined for electronic help formats (HTML Help, WebHelp, Visual Studio Help and eWriter Help) print-style help formats (PDF, printed manuals, Word DOCX and ePUB and Kindle Mobi eBooks).
This will only have an effect if you have defined different settings for screen and print output in your style definitions. See Multiple style sets for more information on using different style sets for different output formats.
Display buttons in the status bar:
|
See also:
About inheritance in styles
Defining styles
Editing styles
The Format Menu (Reference)
