Discussion:
Crashing when saving as .xml
(too old to reply)
Stamm, David-P45904
2010-01-19 19:08:57 UTC
Permalink
Windows XP Professional 2002 SP2
Intel® Core(TM)2 Duo CPU
T9400 @ 2.53 GHz
1.59 GHz, 3.48 GB RAM

Adobe® FrameMaker® 8.0p277 (structured)

On two similar workstations with similar setups, FrameMaker crashes when trying to save two of seven files as XML files. Get same results with both files when choosing either "File | Save As..." or "File | Save As XML... ." The other five files are fine.

In "Save Document" window, choose "Save" button. FrameMaker displays message,

"FmTranslator client got assertion failure."

Choose "OK" button. FrameMaker crashes with both customary message plus, "The instruction at . . . referenced memory at . . .. The memory could not be 'read'."

Have sent crash logs to FrameMaker failure reporting.

Help, please.

Thanks!

Dave Stamm
Writer
2010-01-19 19:30:13 UTC
Permalink
I'm really reaching here because I only used FM8 for a short time, but did you try validating your XML files before you saved?

Nadine
Subject: Crashing when saving as .xml
Date: Tuesday, January 19, 2010, 2:08 PM
Windows XP Professional 2002 SP2
Intel® Core(TM)2 Duo CPU
1.59 GHz, 3.48 GB RAM
Adobe® FrameMaker® 8.0p277 (structured)
On two similar workstations with similar setups, FrameMaker
crashes when trying to save two of seven files as XML
files.  Get same results with both files when choosing
either "File | Save As..." or "File | Save As
XML... ."  The other five files are fine.
In "Save Document" window, choose "Save" button. 
FrameMaker displays message,
    "FmTranslator client got assertion
failure."
Choose "OK" button.  FrameMaker crashes with both
customary message plus, "The instruction at . . . referenced
memory at . . ..  The memory could not be 'read'."
Have sent crash logs to FrameMaker failure reporting.
Help, please.
Thanks!
Dave Stamm
_______________________________________________
To unsubscribe send a blank email to
or visit http://lists.frameusers.com/mailman/options/framers/generic668%40yahoo.ca
Visit
http://www.frameusers.com/ for more resources and
info.
Stamm, David-P45904
2010-01-19 20:10:06 UTC
Permalink
Nadine -

Yes, validated file before trying to save as .xml and before crash.

Dave Stamm
Publications Specialist, Senior Staff
General Dynamics C4 Systems, Inc.
Battle Management Systems Division
1700 Magnavox Way, Suite 200 We'll hit your targets from here.(tm)
Fort Wayne, Indiana 46804-1552
US
tel: 260-434-9620
fax: 260.434.9606
***@gdc4s.com
http://www.gdc4s.com/

This message and / or attachments may include information subject to
GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be
accessed only by authorized recipients. Use, storage and transmission
are governed by General Dynamics and its policies. Contractual
restrictions apply to third parties. Recipients should refer to the
policies or contract to determine proper handling. Unauthorized review,
use, disclosure or distribution is prohibited. If you are not an
intended recipient, please contact the sender and destroy all copies of
the original message.

-----Original Message-----
From: Writer [mailto:***@yahoo.ca]
Sent: 2010-January-19-Tuesday 14:30
To: FrameMaker user's list posting; Stamm, David-P45904
Subject: Re: Crashing when saving as .xml

I'm really reaching here because I only used FM8 for a short time, but
did you try validating your XML files before you saved?

Nadine
Stamm, David-P45904
2010-01-19 20:30:26 UTC
Permalink
Nadine -

Yes and no: in our context, in both problematic files, and in other five files, the top-level elements have id attributes with values = <no value>.

Dave Stamm
Publications Specialist, Senior Staff
General Dynamics C4 Systems, Inc.
Battle Management Systems Division
1700 Magnavox Way, Suite 200 We'll hit your targets from here.(tm)
Fort Wayne, Indiana 46804-1552
US
tel: 260-434-9620
fax: 260.434.9606
***@gdc4s.com
http://www.gdc4s.com/

This message and / or attachments may include information subject to GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message.

-----Original Message-----
From: Writer [mailto:***@yahoo.ca]
Sent: 2010-January-19-Tuesday 15:15
To: Stamm, David-P45904
Subject: RE: Crashing when saving as .xml

Do the two crashing topics have the same ID number?

Nadine
Post by Stamm, David-P45904
Subject: RE: Crashing when saving as .xml
Date: Tuesday, January 19, 2010, 3:10 PM Nadine -
Yes, validated file before trying to save as .xml and before crash.
Dave Stamm
Publications Specialist, Senior Staff
General Dynamics C4 Systems, Inc.
Battle Management Systems Division
1700 Magnavox Way, Suite 200
   We'll hit your targets from here.(tm) Fort Wayne, Indiana 
46804-1552 US
tel:  260-434-9620
fax:  260.434.9606
http://www.gdc4s.com/
This message and / or attachments may include information subject to
GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be
accessed only by authorized recipients.  Use, storage and transmission
are governed by General Dynamics and its policies.
Contractual
restrictions apply to third parties.  Recipients should refer to the
policies or contract to determine proper handling.
Unauthorized review,
use, disclosure or distribution is prohibited.  If you are not an
intended recipient, please contact the sender and destroy all copies
of the original message.
-----Original Message-----
Sent: 2010-January-19-Tuesday 14:30
To: FrameMaker user's list posting; Stamm, David-P45904
Subject: Re: Crashing when saving as .xml
I'm really reaching here because I only used FM8 for a short time, but
did you try validating your XML files before you saved?
Nadine
Jeremy H. Griffith
2010-01-19 21:11:23 UTC
Permalink
On Tue, 19 Jan 2010 15:30:26 -0500, "Stamm, David-P45904"
Post by Stamm, David-P45904
Yes and no: in our context, in both problematic files,
and in other five files, the top-level elements have id
attributes with values = <no value>.
And they still validated??? They shouldn't have;
that would be a bug in the validator. In XML,
the ID attribute cannot be empty, and must start
with a letter (after which it can contain only
letters, digits, hyphens, and underscore). You
can just make it "x", or else remove it entirely.

Also note that within any particular XML file,
IDs must be unique; it's OK for IDs in different
files to be the same.

HTH!

-- Jeremy H. Griffith, at Omni Systems Inc.
<***@omsys.com> http://www.omsys.com/
Stamm, David-P45904
2010-01-19 21:59:41 UTC
Permalink
Jeremy -

With the \.dtd we're required to use, many of the attributes of these
top-level (that is, chapter-level) elements are optional. So, yeah. Go
figure.

Thanks.
Dave Stamm
Publications Specialist, Senior Staff
General Dynamics C4 Systems, Inc.
Battle Management Systems Division
1700 Magnavox Way, Suite 200 We'll hit your targets from here.(tm)
Fort Wayne, Indiana 46804-1552
US
tel: 260-434-9620
fax: 260.434.9606
***@gdc4s.com
http://www.gdc4s.com/

This message and / or attachments may include information subject to
GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be
accessed only by authorized recipients. Use, storage and transmission
are governed by General Dynamics and its policies. Contractual
restrictions apply to third parties. Recipients should refer to the
policies or contract to determine proper handling. Unauthorized review,
use, disclosure or distribution is prohibited. If you are not an
intended recipient, please contact the sender and destroy all copies of
the original message.

-----Original Message-----
From: Jeremy H. Griffith [mailto:***@omsys.com]
Sent: 2010-January-19-Tuesday 16:11
To: FrameMaker user's list posting
Cc: ***@yahoo.ca; Stamm, David-P45904
Subject: Re: Crashing when saving as .xml

On Tue, 19 Jan 2010 15:30:26 -0500, "Stamm, David-P45904"
Post by Stamm, David-P45904
Yes and no: in our context, in both problematic files, and in other
five files, the top-level elements have id attributes with values = <no
value>.
And they still validated??? They shouldn't have; that would be a bug in
the validator. In XML, the ID attribute cannot be empty, and must start
with a letter (after which it can contain only letters, digits, hyphens,
and underscore). You can just make it "x", or else remove it entirely.


Also note that within any particular XML file, IDs must be unique; it's
OK for IDs in different files to be the same.

HTH!

-- Jeremy H. Griffith, at Omni Systems Inc.
<***@omsys.com> http://www.omsys.com/
Harding, Dan
2010-01-20 15:18:38 UTC
Permalink
This may seem like an oddball request, but as part of our review process, it has been requested that there be a way to print the location (and possibly the content) of the index markers within the chapter text. That way, as reviewers are working their way through chapters, they can see at a glance whether or not a word or phrase is indexed.

Due to the nature of our review process this must be on paper; an electronic solution is not viable.

Being able to print the actual contents of the index marker at its location would be pure bonus (similar to the way MS Word allows you to print hidden text at a location within braces), but barring that, a simple visual representation of the index marker at its location would suffice.

Thanks in advance,

Dan Harding
Technical Specialist & Web Developer
University of Illinois Tax School
339 Mumford Hall
1301 West Gregory Drive
Urbana, IL 61801
217-333-0935
Rick Quatro
2010-01-20 17:49:57 UTC
Permalink
Hi Dan,

IXgen for FrameMaker does this. See

http://www.fsatools.com/

Rick Quatro
Carmen Publishing Inc.
585-659-8267
***@frameexpert.com
www.frameexpert.com

-----Original Message-----
From: framers-***@lists.frameusers.com
[mailto:framers-***@lists.frameusers.com] On Behalf Of Harding, Dan
Sent: Wednesday, January 20, 2010 10:19 AM
To: FrameMaker user's list posting
Subject: Printing Index Marker Symbols and Content?

This may seem like an oddball request, but as part of our review process, it
has been requested that there be a way to print the location (and possibly
the content) of the index markers within the chapter text. That way, as
reviewers are working their way through chapters, they can see at a glance
whether or not a word or phrase is indexed.

Due to the nature of our review process this must be on paper; an electronic
solution is not viable.

Being able to print the actual contents of the index marker at its location
would be pure bonus (similar to the way MS Word allows you to print hidden
text at a location within braces), but barring that, a simple visual
representation of the index marker at its location would suffice.

Thanks in advance,

Dan Harding
Technical Specialist & Web Developer
University of Illinois Tax School
339 Mumford Hall
1301 West Gregory Drive
Urbana, IL 61801
217-333-0935
Scott Prentice
2010-01-20 18:03:06 UTC
Permalink
MarkerTools from Leximation does this too ..
http://www.leximation.com/tools/info/markertools.php

and I believe that Index Tools Professional from Silicon Prairie
Software does as well .. http://www.siliconprairiesoftware.com/Products.html

Cheers,

...scott

Scott Prentice
Leximation, Inc.
www.leximation.com
+1.415.485.1892
Post by Rick Quatro
Hi Dan,
IXgen for FrameMaker does this. See
http://www.fsatools.com/
Rick Quatro
Carmen Publishing Inc.
585-659-8267
www.frameexpert.com
-----Original Message-----
Sent: Wednesday, January 20, 2010 10:19 AM
To: FrameMaker user's list posting
Subject: Printing Index Marker Symbols and Content?
This may seem like an oddball request, but as part of our review process, it
has been requested that there be a way to print the location (and possibly
the content) of the index markers within the chapter text. That way, as
reviewers are working their way through chapters, they can see at a glance
whether or not a word or phrase is indexed.
Due to the nature of our review process this must be on paper; an electronic
solution is not viable.
Being able to print the actual contents of the index marker at its location
would be pure bonus (similar to the way MS Word allows you to print hidden
text at a location within braces), but barring that, a simple visual
representation of the index marker at its location would suffice.
Thanks in advance,
Dan Harding
Technical Specialist & Web Developer
University of Illinois Tax School
339 Mumford Hall
1301 West Gregory Drive
Urbana, IL 61801
217-333-0935
Peter Gold
2010-01-20 18:53:06 UTC
Permalink
In addition to the other marker-management tools mentioned in recent
threads, you might want to look at the free markerworker tool, by
"cud." Search Google for it.

To colorize markers, I think you could apply a character format or
condition tag to them:

* Turn on View > Text Symbols
* Select an example of the character format or condition, and copy it
to the clipboard with Edit > Copy Special > (choose character format
or condition tag.)
* Use Find > Marker of Type > Index and Replace by Pasting

If your files are saved before you run the Find/Replace, you can
revert all files to undo the action. However, for real security in
case life happens, SAVE A COMPLETE COPY BEFORE REPLACING.

HTH

Regards,

Peter
_______________________
Peter Gold
KnowHow ProServices
Post by Harding, Dan
This may seem like an oddball request, but as part of our review process, it has been requested that there be a way to print the location (and possibly the content) of the index markers within the chapter text. That way, as reviewers are working their way through chapters, they can see at a glance whether or not a word or phrase is indexed.
Due to the nature of our review process this must be on paper; an electronic solution is not viable.
Being able to print the actual contents of the index marker at its location would be pure bonus (similar to the way MS Word allows you to print hidden text at a location within braces), but barring that, a simple visual representation of the index marker at its location would suffice.
Thanks in advance,
Dan Harding
Technical Specialist & Web Developer
University of Illinois Tax School
339 Mumford Hall
1301 West Gregory Drive
Urbana, IL 61801
217-333-0935
_______________________________________________
To unsubscribe send a blank email to
or visit http://lists.frameusers.com/mailman/options/framers/peter%40knowhowpro.com
http://www.frameusers.com/ for more resources and info.
Frank Stearns
2010-01-20 19:10:57 UTC
Permalink
Post by Harding, Dan
This may seem like an oddball request, but as part of our review
process, it has been requested that there be a way to print the
location (and possibly the content) of the index markers within the
chapter text. That way, as reviewers are working their way through
chapters, they can see at a glance whether or not a word or phrase
is indexed.
Due to the nature of our review process this must be on paper; an
electronic solution is not viable.
Being able to print the actual contents of the index marker at its
location would be pure bonus (similar to the way MS Word allows you
to print hidden text at a location within braces), but barring that,
a simple visual representation of the index marker at its location
would suffice.
Hi Dan -

Check out the "expand markers" function in the IXgen demo you just
ordered.

Marker text will be elevated into the main body text flow, with a
character tag applied to it. You can change the particulars of
that character tag to best suite your visual needs (color, size,
weight, etc -- just don't rename the tag).

Do note that lifting marker text into the main body text will
temporarily change the pagination of your document, but I assume
that's not an issue for a marker review copy.

When done, you can use the IXgen "collapse markers" function to
return the marker text to their source markers; your pagination will
return to what it was before (assuming you've not made changes to the
body text.)

While the marker text is exposed, you can make edits to it, though for
the majority of marker editing tasks, the Editable Marker List is
used. (Your choice; IXgen just provides more than one way to do some
things.)

Often Expand Markers is used if you are doing a find/change in the
body text and also want to pick up any occurrences in markers.

Frank Stearns Associates | makers of IXgen(tm) for FrameMaker(r)
***@fsatools.com <mailto:***@fsatools.com>
TOLL FREE Voice (USA and Canada): 800-567-6421
USA Voice: 360-892-3970 USA FAX: 360-253-1498
http://www.fsatools.com
Baruch Brodersen
2010-01-20 19:23:41 UTC
Permalink
Hi Dan,
Like Rick and others, I've used IXGen for years to do this sort of thing,
and I highly recommend it instead of, the workaround presented below.
Create an "index" character format and define all of its parameters to As-Is
except for color (red works well)and possibly an overbar. An overbar is a
nice visual cue if you print to black & white. Apply this character format
to all words containing index markers.
In another document (or mif fragment) redefine the index character format:
As-Is but with no overbar and set the color to black. When you have finished
producing a reveiw copy with the visually-indicated indexed words, import
the "index" character formats from the second document to make those words
look like the rest of the text in your document. Voila.
Now, you can also generate a list of index markers that will give you the
text and page location of the marker itself. In the book file, Add > List of
(or if you want it sorted alphabetically, Index of...) Markers > Index.
Baruch Brodersen
Post by Harding, Dan
This may seem like an oddball request, but as part of our review process,
it has been requested that there be a way to print the location (and
possibly the content) of the index markers within the chapter text. That
way, as reviewers are working their way through chapters, they can see at a
glance whether or not a word or phrase is indexed.
Due to the nature of our review process this must be on paper; an
electronic solution is not viable.
Being able to print the actual contents of the index marker at its location
would be pure bonus (similar to the way MS Word allows you to print hidden
text at a location within braces), but barring that, a simple visual
representation of the index marker at its location would suffice.
Thanks in advance,
Dan Harding
Technical Specialist & Web Developer
University of Illinois Tax School
339 Mumford Hall
1301 West Gregory Drive
Urbana, IL 61801
217-333-0935
_______________________________________________
To unsubscribe send a blank email to
or visit
http://lists.frameusers.com/mailman/options/framers/baruch%40technitext.com
http://www.frameusers.com/ for more resources and info.
--
B a r u c h B r o d e r s e n
T e c h n i t e x t D o c u m e n t a t i o n
8 7 7 7 2 1 6 9 8 8
Sent from Givatayim, TA, Israel
Kelly McDaniel
2010-01-19 19:58:00 UTC
Permalink
Check the log and see where the assertion failure occurred, then start from there to diagnose.

The referenced memory error means that FM went to a memory location that was indexed to contain a specific bit of data and found the wrong data or no data.

-----Original Message-----
From: framers-***@lists.frameusers.com [mailto:framers-***@lists.frameusers.com] On Behalf Of Stamm, David-P45904
Sent: Tuesday, January 19, 2010 1:09 PM
To: FrameMaker user's list posting
Subject: Crashing when saving as .xml

Windows XP Professional 2002 SP2
Intel® Core(TM)2 Duo CPU
T9400 @ 2.53 GHz
1.59 GHz, 3.48 GB RAM

Adobe® FrameMaker® 8.0p277 (structured)

On two similar workstations with similar setups, FrameMaker crashes when trying to save two of seven files as XML files. Get same results with both files when choosing either "File | Save As..." or "File | Save As XML... ." The other five files are fine.

In "Save Document" window, choose "Save" button. FrameMaker displays message,

"FmTranslator client got assertion failure."

Choose "OK" button. FrameMaker crashes with both customary message plus, "The instruction at . . . referenced memory at . . .. The memory could not be 'read'."

Have sent crash logs to FrameMaker failure reporting.

Help, please.

Thanks!

Dave Stamm
_______________________________________________


You are currently subscribed to Framers as ***@pavtech.com.

Send list messages to ***@lists.frameusers.com.

To unsubscribe send a blank email to
framers-***@lists.frameusers.com
or visit http://lists.frameusers.com/mailman/options/framers/kmcdaniel%40pavtech.com

Send administrative questions to ***@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.
Stamm, David-P45904
2010-01-19 20:14:32 UTC
Permalink
Kelly -

There's an interesting point: whether FrameMaker displays a "Save as XML Log." FrameMaker has done so when necessary file or files are missing. With all necessary files present, FrameMaker does not display the "Save as XML Log."

In my quick look through the crash log, I saw nothing meaningful to my non-software-engineer's eyes.

Dave Stamm
Publications Specialist, Senior Staff
General Dynamics C4 Systems, Inc.
Battle Management Systems Division
1700 Magnavox Way, Suite 200 We'll hit your targets from here.(tm)
Fort Wayne, Indiana 46804-1552
US
tel: 260-434-9620
fax: 260.434.9606
***@gdc4s.com
http://www.gdc4s.com/

This message and / or attachments may include information subject to GDC4S O.M. 1.8.6 and GD Corporate Policy 07-706 and is intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message.

-----Original Message-----
From: Kelly McDaniel [mailto:***@pavtech.com]
Sent: 2010-January-19-Tuesday 14:58
To: Stamm, David-P45904; FrameMaker user's list posting
Subject: RE: Crashing when saving as .xml

Check the log and see where the assertion failure occurred, then start from there to diagnose.

The referenced memory error means that FM went to a memory location that was indexed to contain a specific bit of data and found the wrong data or no data.

-----Original Message-----
From: framers-***@lists.frameusers.com [mailto:framers-***@lists.frameusers.com] On Behalf Of Stamm, David-P45904
Sent: Tuesday, January 19, 2010 1:09 PM
To: FrameMaker user's list posting
Subject: Crashing when saving as .xml

Windows XP Professional 2002 SP2
Intel® Core(TM)2 Duo CPU
T9400 @ 2.53 GHz
1.59 GHz, 3.48 GB RAM

Adobe® FrameMaker® 8.0p277 (structured)

On two similar workstations with similar setups, FrameMaker crashes when trying to save two of seven files as XML files. Get same results with both files when choosing either "File | Save As..." or "File | Save As XML... ." The other five files are fine.

In "Save Document" window, choose "Save" button. FrameMaker displays message,

"FmTranslator client got assertion failure."

Choose "OK" button. FrameMaker crashes with both customary message plus, "The instruction at . . . referenced memory at . . .. The memory could not be 'read'."

Have sent crash logs to FrameMaker failure reporting.

Help, please.

Thanks!

Dave Stamm
_______________________________________________


You are currently subscribed to Framers as ***@pavtech.com.

Send list messages to ***@lists.frameusers.com.

To unsubscribe send a blank email to
framers-***@lists.frameusers.com
or visit http://lists.frameusers.com/mailman/options/framers/kmcdaniel%40pavtech.com

Send administrative questions to ***@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Continue reading on narkive:
Loading...