Autogenerated sections in printed document

[Guest]

Hello!

I have some problems working with Robohelp 6.0 for Word

1. I want to form Microsoft Word document containing cover page, table of contents, glossary, index etc. I want to
form all of these autogenerated sections with my own Word template. I.e. I want to form cover page with product
name, company name, production date and other attributes having their own location and design style. With Robohelp I
can generate only default cover page with document name. The same with other autogenerated sections. Can I assign
some Word templates to Robohelp for use in autogenerated sections? Or can I do this with any other manner?

2. As I read in Robohelp's Users Manual I can change some of page settings manually in resulting document only. These settings are page numbering style, page headers /footers etc. It is not convenient. I want to fit these
settings before generation, possibly with templates too. Can I do this with Robohelp?

Help me, please.

Thank you.

[Peter Grainge]

Welcome to the forum.

You can use your own templates by selecting them in the last page of the wizard. That said, many times when we see a problem it is because someone has opted for other than the supplied Style Mapping template. The templates used are usually good templates and nobody has put a finger on why the home brewed templates are not working.

The answer to point 2 is that you cannot affect those items.

Take a look at the topic on my site about Printed Documentation. I think it will cover a lot of the points you raise.

[Mick_Mathers]

I too wanted a custom frontsheet, TOC and index in the printed documentation. All of these I could do in RH2002 that I used before MS Word 2003.

When I upgraded to RH6, I could no longer have these custom parts when generating the printed documentation from word documents.

But, you can have custom parts in the printed documentation if you use RH for HtmlHelp.

I've converted all our help projects to HtmlHelp. This is a reasonably simple procedure. Peter Grainge's web site has some useful info on do's and don'ts for this.

Mick Mathers