FrameMaker 12 Publish Crash

Question

Using Framemaker 12.0.1.331 all publish operations crash if the document contains a UserString of 1 or more characters in a table element.  We use UserStrings in this way to hold metadata about tables such as database keys and effective dates.
The Mif looks like this:  [We would normally have an xml fragment here but this is enough to produce a crash]
<Tbl
  <TblID 10>
<UserString `A'>
  <TblTag `Format A'>
  <TblFormat
Incidently a zero length UserString doesn't result in a crash.
Looks like a bug to me.
regards,
    Colin

Answer 1

Hi Anchal,
Thank you for all your efforts with this. However, the UserString issue is not fixed with the FrameMaker 12.0.2. Here is the way I am testing this:
1) Create a new Portrait FrameMaker document.
2) Create two small text frames at the top of the page.
3) Select one frame and run this:
#target framemaker
var doc = app.ActiveDoc;
var textFrame = doc.FirstSelectedGraphicInDoc;
textFrame.UserString = "Set with ExtendScript";
alert (textFrame.UserString);
The fifth line displays "Set with ExtendScript" like you would expect. However, when you comment out the fourth line and just try to display UserString, it displays "undefined".
I tried selecting the second text frame and repeating the test with FrameScript:
Set oTextFrame = FirstSelectedGraphicInDoc;
Set oTextFrame.UserString = 'Set with FrameScript 6';
Display oTextFrame.UserString;
It displays the UserString like it should. When I comment out the second line and run it again, it still displays the correct UserString. If I save and close the document and reopen it, it still displays the correct UserString.
FrameScript 6 is correctly reading and writing the UserString property, but ExtendScript is not. Please let me know if you have any questions or comments. Thank you very much.
Rick