>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 22.03.00, 14:14:00, Hubert Figuiere <[EMAIL PROTECTED]> wrote
regarding messages opening Word file:
> I'm attempting to open a word document with AbiWord current. (it does
not
> open correctly with StarOffice... ROFL).
> I'm getting these error messages:
> wvWarning: Must be 1, not 2 as specs, test algor gives 22
> wvError: (escher.c:87) Eating type 0xf00b
> wvError: (escher.c:87) Eating type 0xf122
> wvError: (escher.c:525) Eating type 0xf122
> wvError: (escher.c:525) Eating type 0xf122
> wvError: (escher.c:525) Eating type 0xf122
> wvError: (escher.c:525) Eating type 0xf122
> wvError: (escher.c:525) Eating type 0xf122
> wvError: (escher.c:177) Eating type 0xf004
> wvError: (escher.c:177) Eating type 0xf005
> wvError: (escher.c:525) Eating type 0xf122
> wvError: (escher.c:525) Eating type 0xf122
> (I can send the document for debugging purpose).
> What is it ?
That would be a problem with the escher parser. The graphics in word
are stored in this format, the parser has found unimplemented fields
and attempted to skip them, either
a) all is well and the fields were skipped ok, the doc loads and no
crashes ?
b) the previous recognized field was not handled correctly leaving the
parser out of step with the datafile and all hell breaks loose.
c) the "field eater" has gotten it wrong and ate too much, again
leaving everything in a useless state
>From memory those field identifiers all fit the profile of a valid
entry i.e. they are f???. If this is a crashes I imagine that the
problem is likely to be that one record contained another but the
parser was too simplistic to figure it out. Send me on the document
and I will look into it.
C.
> Hub
