[Date Prev][Date Next][Subject Prev][Subject Next][ Date Index][ Subject Index]

Re: Using XyWrite file in Word and saving as text document



Further to this question, I find that there is some sort of poison
pill in the file I was trying to convert (my collection of list posts
for the month of November): when I run SA/RTF on that whole file, I
get a bare header file. Thinking the lack of any formatting on a
compilation of plain-text e-mails might be the spanner in the works, I
slapped margins and UFCourier on the file and tried again. The exact
same bare header was all that was created. Here's a copy, if anyone
with more knowledge of RTF coding that I can see what it means:

{\rtf1\ansi \deff0 {\fonttbl {\f0\froman Tms Rmn;}
{\f1\fswiss Helv;}{\f2\fmodern Courier;}}
{\colortbl;\red0\green0\blue0;\red0\green0\blue127;\red0\green127\blue0;\red0\green127\blue127;\red127\green0\blue0;\red127\green0\blue127;\red127\green127\blue0;\red127\green127\blue127;\red192\green192\blue192;\red0\green0\blue255;\red0\green255\blue0;\red0\green255\blue255;\red255\green0\blue0;\red255\green0\blue255;\red255\green255\blue0;\red255\green255\blue255;}\linex0 \sbknone
\margl1800 \margr1800 \margt1440 \margb1440 \plain }
When I compared that with the beginning of a properly converted RTF file, I noticed that I had not specified paper size. So I put that at the head and tried again. Still the same short RTF file results. What COULD be gumming up the works?
Apart from that crazy file, SA/RTF works fine, not merely on this
fairly speedy PC, but also on one of my antiques, a K6/2 450 MHz with
128 Mb of RAM, running Win 98 initial release. That would seem to rule
out timing as a cause of Harry's problems.

May one assume that the
[JM_]2.AwaitDel[Q2_]

accomplishes the same thing as the

"echo WAIT a few seconds for conversion to delete temp files
pause"
in Robert's original batchfile for conversion? I do see that SA/RTF calls Kmd.exe in Win, thus running the actual conversion in a separate VDM, and so avoiding OOM.


--
Patricia M. Godfrey
PriscaMG@xxxxxxxx