Created attachment 36111 [details]
Example word document that fails to import to 2.0.2

MRU->FLR: the "sequence" field right at the beginning of the text should be
imported as hidden text; on this way the field switch \h from MS Word could be
interpreted for it.

But it was also the case in OO 1.1.x, so no Regression. Other things look good
IMO. Please describe more precisely if I missed something.

NO THIS IS *NOT* THE CASE. 1.1.5 opens the sample document fine. ABIWord and
KWord alos open the test file. ONLY 2.0.2 exhibits this problem and so IT IS A
REGRESSION.  Please take the necessary steps to get this fixed for 2.0.3 as it
is a MAJOR bug.

Created attachment 36127 [details]
How OO 1.1.5 imports the attached doc

See my attachment; it looks the same in OO 1.1.5 and OO 2.0.2.
Also, the fact that it is a regression foes not justify P2 for this. P2 is
reserved for crashes.

p3 is okay however;I think that P2 is appropriate according to the definitions:

P2
    P2 marks severe problems which affect a significant number of customers
    Issues with this priority must be fixed before the target release (see
Target milestone), which usually is the next major release, and should be dealt
with as soon as possible.
    Not fixing them for the target release is not acceptable.
Measures/Examples

    * An essential product feature - e.g. Printing - does not work at all, and
no workaround exists
    * User data is corrupted in an easy-to-encounter way;
      e.g. saving a document corrupts the resulting file and renders it unusable
    * Crashs or freezes during normal operations of the application
    * A critical usability problem;
      e.g. a user interface which renders the underlying functionality
incomprehensible for the majority of users
    * Severe performance problems in often-used/basic functionality;
      e.g.
          o every application startup takes 5 minutes
          o saving/loading of usual small-sized document takes several minutes
    * Huge memory leaks in common or easy-to-reach functionality;
      e.g. a mail merge operation which leaks 1 MB per merged document
    * UI responsiveness of a non-essential feature is extremely poor, rendering
the feature unusable;
      e.g. a File/Open dialog which needs 5 minutest to open

This one in particular:

* A critical usability problem;
      e.g. a user interface which renders the underlying functionality
incomprehensible for the majority of users

You might want to reconsider.

No, we won't reconsider the priority.
This problem is of course not critical. The application does not crash nor it
interfers an essential feature.
Also, there exists a VERY easy workaround for it: just press DEL in at the
beginning of the document.
Additionally, it is not a regression as my screenshot shows.

Okay. Let me see if I understand. You are syaing this is not a regression. Is
that correct? If yes, then I would like to point out that "A regression is when
the software "relapses to a less perfect or developed state". (American Heritage
Dictionary) This usually means that a feature or function was working in earlier
builds and is now broken. It may also mean that speed or stability has gotten
worse. It's often useful to notice that something is a regression, because it
may point out that a bug "fix" was actually not appropriate or proper." 

Now you have confirmed that 1.1.5 does indeed import the file correctly but that
2.0.2 does not yet you refuse to treat this as a REGRESSION. Why? 

assigned to hbrinkm

*** Issue 75170 has been marked as a duplicate of this issue. ***

I have a similar issue that may be related. When opening documents produced in
Word2000/2003, OO 2.0 loses formatting information for sequence fields ("SEQ"
field in Word). In particular, a SEQ field formatted with the "\*alphabetic"
switch (to be displayed as "a, b, c") gets reset to the default arabic "1, 2,
3"). This seems to happen only if the additional switch "\*MERGEFORMAT" in Word
is activated. Fields created in Word without the mergeformat switch are imported
correctly. Test document (test.doc) and OpenOffice screenshot showing the error
attached.

Created attachment 45593 [details]
test .doc showing import failure with SEQ field using "\*alphabetic" switch

Created attachment 45594 [details]
screenshot of test.doc opened in OO2.0.2. The first of the two SEQ fields is displayed wrongly.

*** Issue 113057 has been marked as a duplicate of this issue. ***

Reset assigne to the default "issues@openoffice.apache.org".