Publish in Responsive HTML5 - files skipped and 3rd level topics not generated

Question

I'm having trouble getting the new FrameMaker 11 Publish features to work as expected.
I have a ditamap with three levels of headings. When I use the Publish feature to output in Responsive HTML5, a TOC is produced, in which there are no links below the second level.
Moreover, even some files at the second level randomly are not accessible from the TOC. A link is present, but when I click, it lands on a page that says "this webpage is not found".
When I look in the output directory, all the files are present in html form, so they do exist.
One file, however, although correctly formed in the xml source with a series of unordered lists, comes out looking like this:
An interactive script called bootstrap_.cmd is provided when you run the installation package for the Control Centre. This script simplifies the configuration of the sample database with a MySQL database engine. It performs a series of setup tasks, including:
ÃÃÆ⠀™Ãƒâ€ ’ƒâ€šà ƒÆ’ƒÆ’‚¢Ãà †â€™Ãƒâ€ ’ĮբÃà †â€™Ãƒâ€ ’ƒÂ¢Ã¢â€Å ¡Ã‚¬Ã…¡Ãà †â€™Ãƒâ€ ’ƒâ€šà ƒÆ’ƒÆ’‚¬Ãà †â€™Ãƒâ€ ’ƒÆ’ââ‚ ¬Ã…¡Ãƒâ€šà ƒÆ’ƒÆ’‚¢               Execution of the SQL command that creates the database,
Needless to say, this is not useable. Is this a bug in Frame, or am I doing something wrong?
Thanks to anyone who can help,
EFR
Cambridge Imaging Systems

Answer 1

I had some help from Adobe support about the inability of the Publish tool to generate more than two levels of depth in the hierarchy.
The depth is managed by the 'ParaTags' setting in 'BookWithFM-TOC' section of "ditafm-output.ini". By default, it is set to manage only two levels. To change it to four:
[BookWithFM-TOC]
Template=TOCTpl.fm
ElementTags=
ParaTags=title.0|title.1|title.2|title.3|title.4|title-index
Nevertheless, for a long time I could not get this to work for me, because there were in effect TWO ditafm-output.ini files in my standard installation and the one which controlled the output was HIDDEN and did not appear in any searches!
This file:
C:\Program Files (x86)\Adobe\AdobeFrameMaker12\fminit\ditafm\ditafm-output.ini
is the incorrect one, but it is the only one that actually shows up when I looked for ditafm-output.ini.
The correct ini file was in a subdirectory of the path
C:\Users\my_user\AppData\Roaming\Adobe
The trick is to do a search on AppData. It does not show up in a Windows Explorer, but the search returns a slew of htm files recently generated by the Publish process. These confess the hidden path in their headers, under the OriginalFile tag.
None of this was at all self-evident! Thanks Adobe Support.
EFR
Cambridge Imaging Systems