Skip to main content
jayaflir
jayaflir
Inspiring
October 17, 2018
Answered

FM 2017 - Responsive HTML5 output - Tables rendered as images

  • October 17, 2018
  • 1 reply
  • 855 views

Hello.

I recently started using FrameMaker 2017 and have been playing with the Responsive HTML5 output. After only changing the default settings (STS file) for the header color and logo image, I have noticed a number of discrepancies between the Save as PDF output and the Responsive HTML5 output (multiple layouts):

  • Out-of-document hyperlinks are blue but not functioning
  • One table is rendered as an image (and the table is numbered as Table b b)
    Source:

    Output:
  • Figure numbering is off (multiple Figure 1-1s in the same chapter)

This is just what I have noticed after a couple of minutes of playing around...

Any advice would be appreciated.

Jay

Message was edited by: Jay Abramoff

This topic has been closed for replies.
Correct answer Stefan Gentz

Looks like your table is inside a text frame which is inside an anchored frame which is inside the main text flow … + an image + graphic objects + numbers.

So, what FM has to do here, is to convert this whole construction into an image. Otherwise, this cannot go in an HTML page.

Notice, that FM *always* creates an image for the content of an anchored frame (unless it's just an image). This is why you get one single image for the anchored frame. This might also explain the b b in the numbering of the table title and the wrong numbering of the image.

You might want to try to "simplify" this construction. Maybe like this:

1 reply

S
Stefan GentzCorrect answer
Legend
October 17, 2018

Looks like your table is inside a text frame which is inside an anchored frame which is inside the main text flow … + an image + graphic objects + numbers.

So, what FM has to do here, is to convert this whole construction into an image. Otherwise, this cannot go in an HTML page.

Notice, that FM *always* creates an image for the content of an anchored frame (unless it's just an image). This is why you get one single image for the anchored frame. This might also explain the b b in the numbering of the table title and the wrong numbering of the image.

You might want to try to "simplify" this construction. Maybe like this:

jayaflir
jayaflirAuthor
Inspiring
October 18, 2018

Thank you, Stefan.

That makes sense. I recently started working at this company, so I inherited this and other docs, which are currently only delivered as PDF. However, that could change at any time, so I'll need to know what changes to make to ensure other output looks OK.

What about the other issues?

Also, it's nice to hear from you, specifically, as I attended a couple of your presentations at Israel's MEGAComm the last couple of years. (I also happened to run into you, Paula, and a couple of others at a spot overlooking the Western Wall - I think two years ago - and took a photo of your group. )

S
Stefan Gentz
Legend
October 18, 2018

Oh wow, that is funny! Yeah, I remember :-)

Regarding the other questions …

So, first thing: Of course there are differences in PDF and Responsive HTML5 help. PDF gives you exactly what you see in the WYSIWYG view of your FrameMaker document. HTML is a completely different thing. Don't even try to make it "static" and look like exactly like your PDF output. It just doesn't make sense from many points of view. However, you can customize the styles with pretty much everything CSS has to offer.

Regarding the "Out of Document" links: Where exactly do they point to? To other documents within the same book? Do you publish the whole book? Or just one document? Or do they point to somewhere completely different? Wherever you point to: Make sure that this target destination really exists. And in case it's e.g. some other chapter in the same book: Make sure to first update the whole book once and then check the hyperlinks in FrameMaker. Do they work there? Extra tip: You can hold down ctrl+alt and then do a left-mouse-click on the hyperlink in FrameMaker to "jump" to the destination.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices