Japanese-format ASCII causes book PS files to crash Frame [long]

["Deborah Snavely" <dsnavely@xxxxxxxxxxx>]

Dear Framers,

A new mystery! Frame 6, Acrobat 4, Windows 2000 Pro...

Background:
	My legacy doc project from Hades...
1. I dumped GhostView ASCII from Frame-source PDFs for which I had no
source 
	Frame files.
2. Opened ASCII files, copied/pasted into clean template, applied tags,
saved.
3. A volunteer assistant learning Frame learned how to do item #2 and
did some 
	files in book (open/copy/paste/re-tag/save, return file to me).
4. Files reassembled into book and I finished up the draft for review.
5. Generate PDF from book file using RELIABLE standard in-house
procedure to 
	produce a bookwide *.ps file for Distillation.

...and crash Frame repeatedly!  "serious error and must quit". 
	(The Bug report is in Adobe's hands with data and error logs.)

Symptoms: always crashes on the SAME page of the same file. (HINT!)

My Tests:
I experimented with *that* file, generating a PS file of only it from
the book and from the file itself. (Same crash, same page.) 

Experimented with splitting the PS file until I identified the one page
causing crash. (All other pages in file generated distillable PS files.)

Opened file and examined problem page. Plain old text (a procedure). Not
a graphic in sight (except the master page showthrough). Not a floating
text block or invisible unanchored frame or any other anomalies on the
page. 

Tried saving the file to MIF and back; no luck.

Copied content of that page only into a new empty Frame file, saved it
to text only, opened THAT text file in FrameMaker...and got the usual
plain text dialog box but with the text settings in a popup menu set to
use "Japanese(JIF)". 
(I didn't notice...the first time.) 

Copied and pasted just that page into a clean template file, applied
tags, tried creating PS, and crash! 

Now (20-20 hindsight) I remember that default popup menu setting and try
again from the plain text file, this time changing the setting to use
ASCII.  That fixed it. Fixed the file, and that file within a
book-generated PS file.

BUT... I try running the book again and the crash happens again...this
time on the next file in the book. I discover this affects every file I
didn't do.

Ki, yi. So I'm looking for a way to get Frame to IGNORE this Japanese
ghost (no Japanese characters anywhere in source PDF or in our Frame
files). 

Question: 	(At last!)

I've checked the book file's MIF and found no mention of "Japanese" or
"JIF". 
In the chapter file's MIF, I find two lines of document properties that
point towards something Japanese in here that I don't expect. I include
several lines that appear to be related to them, although I don't know
what "Rubi" refers to.

------------
<Document 
...
 <DRubiSize  50.0%>
 <DRubiOverhang No>
 <DRubiAlignAtLineBounds No>
 <DNarrowRubiSpaceForJapanese Proportional>
 <DWideRubiSpaceForJapanese Proportional>
 <DNarrowRubiSpaceForOther Narrow>
 <DWideRubiSpaceForOther Narrow>
------------

I find the same exact lines of code in Frame files that do not crash,
however, so I doubt that my first thought (delete these lines of unused
properties and save) is going to handle this.

Can anyone suggest any fast way to deal with this issue? 

Right now my fix means crashing Frame to identify the next problem page,
copy and save each problem page to ASCII, open the ASCII file correctly
this time, recopy guts into my working file and re-do all the tags and
layout and other stuff on that page, save and test that file to make
sure it works, put it back into book...

...and do it all again for the next problem page.  I can't find ANY
indicators in the Frame files to tell me which page/s in a file will
glitch.

There's GOT to be a better way!

Wearily,

Deborah Snavely


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **