FrameMaker files with multiple text flows convert poorly into html5. I have document where I have a master page with an extra text flow (flow B) which forms an "info box" on the bottom of the page. That box ends up in the beginning of the HTML5 file. I suppose it makes sense if one sees the html file as one long flow, but I would still like to have some resemblance to the original document.
Is there a way to manage multiple text flows in a meaningful manner when publishing to HTML5?
Anyone with experience in this might want to know: • separate (disconnected) Flow Bs, or • connected Flow Bs relying on ¶ pagination controls? • in Master Page text frames?, or • in Anchored Frames in Flow A?