Issue 25915 - MSWord document filter handles Docproperties unexpectedly
Summary: MSWord document filter handles Docproperties unexpectedly
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: All All
: P4 Trivial with 4 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 27516 61855 64540 (view as issue list)
Depends on:
Reported: 2004-02-26 17:16 UTC by trimble
Modified: 2013-02-07 22:41 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

document demonstrating strange handling of docproperties in MSWord filter (19.50 KB, application/msword)
2004-02-26 17:18 UTC, trimble
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description trimble 2004-02-26 17:16:59 UTC
See attached document.

Documents created in MSWord that make use of user-defined document properties 
(File->Properties->Custom) do not get imported well through the filter in 
OOo's word processor.  Specifically, the custom fields seem to magically 
become the predefined "Title" field on import.

Opening the attached document in MSWord and OOo demonstrates the issue.
Comment 1 trimble 2004-02-26 17:18:05 UTC
Created attachment 13450 [details]
document demonstrating strange handling of docproperties in MSWord filter
Comment 2 jack.warchold 2004-03-01 14:05:07 UTC
reassigend to mru

can you please take a look on this issue?
Comment 3 michael.ruess 2004-03-02 15:38:38 UTC
OpenOffice does not support custom document properties like MS Office does.
Comment 4 trimble 2004-03-03 16:14:28 UTC
Is "OpenOffice does not support custom document properties like MS Office does"
in conflict with (from the 1.1 - Product Description page) "You
can of course continue to use your old Microsoft Office files without any
problems - and if you need to exchange files with people still using Microsoft
Office, that's no problem either."
Comment 5 michael.ruess 2004-04-15 12:53:24 UTC
*** Issue 27516 has been marked as a duplicate of this issue. ***
Comment 6 michael.ruess 2006-02-10 08:33:17 UTC
*** Issue 61855 has been marked as a duplicate of this issue. ***
Comment 7 nsydenham 2006-02-10 12:40:55 UTC
The lack of this enhancement is preventing Word/OO document interchange,
especially in corporate environments. The priority should be changed to P2.
Comment 8 michael.ruess 2006-04-20 09:14:12 UTC
*** Issue 64540 has been marked as a duplicate of this issue. ***
Comment 9 jmab 2006-05-23 19:06:39 UTC
A similar issue is discussed in <a
regarding the import of MSWord document variables.  As of v 2.0.2, these are
being imported as user-defined metadata of value-type "string", but omitted on
export back to MSWord file formats.

MSWord document variables can only be set through macros, but custom doc
properties are accessible through the UI in both MSWord and Writer, so I think
they should get at least as much support.  Having the data actually import
properly would be the first step, then preserving the field structure on import
(and export!) would be feasible.

Ideally, instead of always being "string", the value-type used for the imported
data should be "docvar" for the variables and "string", "number", "date", or
"boolean" for the custom document properties, so that the exporter or other
document converter could put the pieces back into place for greater MSWord
Comment 10 bgoncalves 2006-08-17 11:12:18 UTC
OO Writer 2.0.3 is almost there.

Until this compatibility is completely provided it is hard to switch from MS
Word do OO Writer.
1. My company use MS Word format to produce documentation, as many companies do
issue 5091).
2. Every document has at least 6 Custom Fields.
3. If I edit a document in Writer I will lose all these Custom Fields.

Please check my simple test with Writer 2.0.3:

1. import Word document with Custom Fields to Writer
2. in Writer save document as Microsoft Word 97/2000/XP (.doc)

. After step 1: the Custom Fields are successfully imported to Writer as
Variables and are dynamic in text in page.

. After step 2: the Variables are successfully exported to Word as Custom Fields
BUT ARE NOT dynamic in text, i.e., the variable text is all static in the page!
Comment 11 bettina.haberer 2010-05-21 14:56:50 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".