Skip to main content
A
Asha_Rayakar
Known Participant
March 19, 2010
Answered

To recognize corrupt framemaker file using framemaker API

  • March 19, 2010
  • 1 reply
  • 1074 views

If I rename a framemaker book as .fm file and then I try to include this file as a component of another book, no pdf is generated on saving the book as pdf.

How can I make sure that a book file is not added as a component using framemaker API ( currently using fdk 6.0).

Thanks,

Asha Rayakar

This topic has been closed for replies.
Correct answer Russ Ward

Asha,

I think I understand now. Somebody else renamed the file... you are just trying to catch the error in your code, right?

I tried to duplicate this scenario, but in my experiments, FrameMaker was smart enough to know what kind of file it was, regardless of the extension. So, here are just some ideas...

- If the file isn't actually "corrupt," you can use F_ApiGetObjectType() to find out whether it is a FO_Book, FO_Doc, or something else. If a document is corrupted, I don't know what that function might return.

- If the file is corrupt, I would think that you should be able to query some kind of property to find that out. For example, maybe you could count the number of paragraph formats in the file. My guess is that a corrupt document will have significantly fewer than you would expect to see, if any at all.

Russ

1 reply

R
Russ Ward
Legend
March 19, 2010

Hi Asha,

I don't understand your question. What exactly are you trying to do?


Russ

A
Asha_RayakarAuthor
Known Participant
March 19, 2010

Hi Russ,

A framemaker book file  (.bk) was renamed as (.fm). And when I open this file, it shows a one line entry of the path of the file in framemaker. I can add this as a component when creating a new book. However this should not be allowed as it is a corrupt framemaker file.

Are there any properties from which we can determine if a framemaker file (.fm) is actually a .bk file ?

Thanks,

Asha

R
Russ WardCorrect answer
Legend
March 19, 2010

Asha,

I think I understand now. Somebody else renamed the file... you are just trying to catch the error in your code, right?

I tried to duplicate this scenario, but in my experiments, FrameMaker was smart enough to know what kind of file it was, regardless of the extension. So, here are just some ideas...

- If the file isn't actually "corrupt," you can use F_ApiGetObjectType() to find out whether it is a FO_Book, FO_Doc, or something else. If a document is corrupted, I don't know what that function might return.

- If the file is corrupt, I would think that you should be able to query some kind of property to find that out. For example, maybe you could count the number of paragraph formats in the file. My guess is that a corrupt document will have significantly fewer than you would expect to see, if any at all.

Russ

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