Can you make the HTML5 ToC look like PDF Bookmarks listing?
Posted: Thu Aug 07, 2014 4:14 pm
Hello!
I'm trying to wrap my head around the way that certain differences in output types work in Flare, and to see if there are any ways to work around these differences that I don't know about. I'm going to try to be clear about my questions, but they all revolve around ToCs, which are a fairly loaded term in the world of Flare, so I apologize in advance if I don't do a good enough job of keeping things straight!
We have been creating PDF documentation for a while now, and we're now working to start creating HTML versions of the documents we already have in PDF (we will also be making new documents with the same / similar content and a different structure, but that's not what I'm asking about here). What I'm trying to figure out how to do is use the same ToC (the *.fltoc file) to generate both the PDF and HTML outputs. I've created different targets, I have certain types of content (such as title page) marked as either print or screen-only using conditions, and all of that works fine.
The thing that I'm stuck on right now is the difference in the way that the 'Contents' menu is generated for HTML5 output, compared with the way that either the ToC Proxy or PDF Bookmarks pane are generated for PDF output. I believe I understand the differences, but I want to see if there's a way to get the HTML5 Contents more in-line with the ToC that gets generated for PDF Bookmarks, or if I'm going to need to do some serious reorganizing of my project structure.
Right now, the *.fltocs that I use are fairly simple. I have a topic for each section, and the topic itself is filled with various levels of headings and mostly snippets. The PDF Bookmarks are generated from those headings, so I get something like this:
Heading level 1
- Heading level 2
- Heading level 2
- - Heading level 3
- Heading level 2
Heading level 1
(sorry for the rough representation)
On the other hand, the Contents that appear for HTML5 help are based precisely on the actual *.fltoc file, and since that only has a topic link for each section, when I generate HTML5 help, I get this:
Heading level 1
Heading level 1
Heading level 1
What is the best way to fix this? I imagine I could create a second ToC for the online help and manually create items that point to each heading in all of the topics, but that seems like a lot of work and I wouldn't want to have to manually maintain both sets of ToCs since we're trying to make PDF and HTML versions of the same content. I could also add those sorts of items to the existing ToC, but would that affect the PDF output at all?
Additionally, we could change our basic organizational structure from snippet-based to topic-based, so the *.fltoc files would have to look like what I expect the generated Contents to look like, but the amount of work involved in that method is daunting. I'm hoping that's not the right answer.
I was also looking at the possibility of using a browse sequence (which looks like it should be able to be automatically generated) but I'm not sure if that's the best answer, either. Is there some other way to change the generated Contents in HTML5 output that I'm not aware of?
Any thoughts on how to best approach this problem? Thanks in advance!
I'm trying to wrap my head around the way that certain differences in output types work in Flare, and to see if there are any ways to work around these differences that I don't know about. I'm going to try to be clear about my questions, but they all revolve around ToCs, which are a fairly loaded term in the world of Flare, so I apologize in advance if I don't do a good enough job of keeping things straight!
We have been creating PDF documentation for a while now, and we're now working to start creating HTML versions of the documents we already have in PDF (we will also be making new documents with the same / similar content and a different structure, but that's not what I'm asking about here). What I'm trying to figure out how to do is use the same ToC (the *.fltoc file) to generate both the PDF and HTML outputs. I've created different targets, I have certain types of content (such as title page) marked as either print or screen-only using conditions, and all of that works fine.
The thing that I'm stuck on right now is the difference in the way that the 'Contents' menu is generated for HTML5 output, compared with the way that either the ToC Proxy or PDF Bookmarks pane are generated for PDF output. I believe I understand the differences, but I want to see if there's a way to get the HTML5 Contents more in-line with the ToC that gets generated for PDF Bookmarks, or if I'm going to need to do some serious reorganizing of my project structure.
Right now, the *.fltocs that I use are fairly simple. I have a topic for each section, and the topic itself is filled with various levels of headings and mostly snippets. The PDF Bookmarks are generated from those headings, so I get something like this:
Heading level 1
- Heading level 2
- Heading level 2
- - Heading level 3
- Heading level 2
Heading level 1
(sorry for the rough representation)
On the other hand, the Contents that appear for HTML5 help are based precisely on the actual *.fltoc file, and since that only has a topic link for each section, when I generate HTML5 help, I get this:
Heading level 1
Heading level 1
Heading level 1
What is the best way to fix this? I imagine I could create a second ToC for the online help and manually create items that point to each heading in all of the topics, but that seems like a lot of work and I wouldn't want to have to manually maintain both sets of ToCs since we're trying to make PDF and HTML versions of the same content. I could also add those sorts of items to the existing ToC, but would that affect the PDF output at all?
Additionally, we could change our basic organizational structure from snippet-based to topic-based, so the *.fltoc files would have to look like what I expect the generated Contents to look like, but the amount of work involved in that method is daunting. I'm hoping that's not the right answer.
I was also looking at the possibility of using a browse sequence (which looks like it should be able to be automatically generated) but I'm not sure if that's the best answer, either. Is there some other way to change the generated Contents in HTML5 output that I'm not aware of?
Any thoughts on how to best approach this problem? Thanks in advance!