In project explorer I have Configuration->Publishing Options->Webhelp->Table of Contents->Simple Template Layout Format of Table-of-contents Headings set to Arial, Helvetica 10, 9, 8 etc for the various headings.
Similarly, for Keyword index.
However, the eViewer displays the TOC and Keyword index in Times New Roman (by the look of it), basically the same font as used for the topics. Also the Keyword search page is also using Times New Roman and is a bit of a mess as the Submit button collides with the results per page: dropdown box.
Am I missing some crucial setting, or is this a bug? I am using a copy of the "Webhelp, iFrames, Responsive, Blue" skin in Build 5452.
eViewer TOC and Index fonts not as expected
Moderators: Alexander Halser, Tim Green
- Greg Smith
- Posts: 138
- Joined: Thu Feb 01, 2007 4:52 pm
- Location: Cambridge, England
- Tim Green
- Site Admin
- Posts: 7818
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: eViewer TOC and Index fonts not as expected
Hi Greg,
Nothing you set in your WebHelp options in your project, if that is where you are editing, will have any effect on your output if you are using a skin. The skin always replaces all the templates and settings for the chosen output format with those stored in the skin. You need to edit the skin, and if you are already editing the skin and are in the Simple Layout version of the template that means the custom template has been deleted/reset to default and the skin is now damaged beyond repair. All the templates in custom skins are always set to Source Code and shouldn't be switched back, which is now only possible with the Reset button.
If you use a fresh copy of the skin the problem should go away.
Nothing you set in your WebHelp options in your project, if that is where you are editing, will have any effect on your output if you are using a skin. The skin always replaces all the templates and settings for the chosen output format with those stored in the skin. You need to edit the skin, and if you are already editing the skin and are in the Simple Layout version of the template that means the custom template has been deleted/reset to default and the skin is now damaged beyond repair. All the templates in custom skins are always set to Source Code and shouldn't be switched back, which is now only possible with the Reset button.
If you use a fresh copy of the skin the problem should go away.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
- Greg Smith
- Posts: 138
- Joined: Thu Feb 01, 2007 4:52 pm
- Location: Cambridge, England
Re: eViewer TOC and Index fonts not as expected
Thank you for your helpful reply.
OK... I'm beginning to understand.The skin I chose did not define any font for TOC and Index, but 'hid' the definitions in the project. So I tried the alternative "Webhelp, Integrated iFrames Blue Header" skin. This is more acceptable, but has an ugly frame at the top with a logo and text telling you to basically edit the HTML to make it acceptable.
I do not speak HTML, but I seem to have been able to hack the layout of the skin to get rid of the logo frame I do not want. So progress...
However, the Keyword search page is untidy (in this skin?) with the Results per page too close to the Submit button as it was in the previous skin. Looking through the HTML I do not see any way (for me with my 0 HTML skills) to adjust the positions as I cannot find any code for this.
I suppose it is possible that the skin premium pack (which I believe I got as part of the update to version
may have something closer to acceptable without needing to edit the HTML... but I do not seem to be able to find it in the version 8 installation, nor is there an obvious download on your site. Assuming I have a licence for it, how do I get access to it?
OK... I'm beginning to understand.The skin I chose did not define any font for TOC and Index, but 'hid' the definitions in the project. So I tried the alternative "Webhelp, Integrated iFrames Blue Header" skin. This is more acceptable, but has an ugly frame at the top with a logo and text telling you to basically edit the HTML to make it acceptable.
I do not speak HTML, but I seem to have been able to hack the layout of the skin to get rid of the logo frame I do not want. So progress...
However, the Keyword search page is untidy (in this skin?) with the Results per page too close to the Submit button as it was in the previous skin. Looking through the HTML I do not see any way (for me with my 0 HTML skills) to adjust the positions as I cannot find any code for this.
I suppose it is possible that the skin premium pack (which I believe I got as part of the update to version
- Tim Green
- Site Admin
- Posts: 7818
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: eViewer TOC and Index fonts not as expected
Hi Greg,
The Premium Pack is a separate installation. The download link and installation details should be included in the confirmation mail you received when you purchased the upgrade, if it was included. If you already have Premium Pack 3 you can also use the V3 eWriter skins, or the V2 combined WebHelp/eWriter skins, included there. They will all work fine with HM8.I suppose it is possible that the skin premium pack (which I believe I got as part of the update to versionmay have something closer to acceptable without needing to edit the HTML... but I do not seem to be able to find it in the version 8 installation, nor is there an obvious download on your site. Assuming I have a licence for it, how do I get access to it?
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.