• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Wrong content in HTML 5 output

Participant ,
Feb 14, 2020 Feb 14, 2020

Copy link to clipboard

Copied

I output HTML 5 of a product guide in 16 languages. I use a separate .book file and .sts file for each language. Each book file has a dozen .fm files; each .fm file is a chapter in the guide. I recently updated to FM 2019 (update 4) and the following issues occurred:

 

  • FM seems to '"remember" some content from the previous book I output and includes it in the book I'm currently outputting. For example, I open the German book, output the HTML 5, and close the book. Next,  I open the Spanish book and output the HTML 5. A chapter in the Spanish HTML 5 output is in German. The errant content is the entire content of one FM file. 

 

  • One .png file is converted to a black box. The rest of the .png files are fine.

 

I closed and re-opened FM and at first it seemed to fix the former problem, so I just closed and re-opened FM between languages. But now when I try to generate HTML 5 output, FM consistently crashes, so now I can't generate it at all. I've also tried rebooting my computer. Thoughts?

TOPICS
Responsive HTML5

Views

471

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 17, 2020 Feb 17, 2020

Copy link to clipboard

Copied

Hi,

 

Yes. FrameMaker ignores changes in your FrameMaker files, when you convert to HTML5. We all hope that this will be fixed soon.

This is already described in the Adobe Tracker:

https://tracker.adobe.com/#/view/FRMAKER-5475 

 

And for example here:

https://community.adobe.com/t5/framemaker/framemaker-2019-html5-generated-output-problems/m-p/107075... 

 

You might vote for this issue in the Adobe Tracker so that this issue gets more attention.

 

The issue with black PNG files in HTML5 is also already described:

https://tracker.adobe.com/#/view/FRMAKER-7769 

https://community.adobe.com/t5/framemaker/fm12-quot-black-quot-images-in-html5-output/m-p/6149426?pa... 

https://community.adobe.com/t5/framemaker/png-images-not-displaying-properly-when-generating-a-pdf-i... 

However, FrameMaker must not crash!

There is a new update 5. Can you update?

Please also delete existing the HTML5 export of this project.

Did you change anything in your sts file?

 

Best regards

 

Winfried

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Feb 21, 2020 Feb 21, 2020

Copy link to clipboard

Copied

Hi Winfried, 

 

It sounds like the issue I'm encoutering is related to, but not exactly the same, as the one you describe. The problem isn't that FrameMaker is ignoring changes I've made to the file. I haven't made changes to the files. The problem is that FrameMaker is including content from a different book in the book I'm currently outputting to HTML 5. For example, if I output French and then Spanish, the Spanish HTML 5 has some chapters that are from the French book. 

 

I've taken update 5. FrameMaker still crashes all the time. 

 

Fortunately, I saved the .fm files from the previous version of FrameMaker before upgrading to 2019. So went back to that earlier version of FrameMaker so I could get the work done.

 

FrameMaker 2019 is unusable for us right now.  

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 23, 2020 Feb 23, 2020

Copy link to clipboard

Copied

LATEST

Hi Deb,

 

Hm. When you still get crashes, please describe this in the Adobe bug tracker:

https://tracker.adobe.com/#/home 

Adobe takes crashes rather serious.

 

And can you reproduce the other issue?

I encountered something like this myself. However, only once.

Please describe this also in the bug tracker and then post the link here.

Then I will vote for this.

 

Best regards

 

Winfried

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines