Issue 9875 - Suggestion: Development of test documents for import/export
Summary: Suggestion: Development of test documents for import/export
Status: CLOSED WONT_FIX
Alias: None
Product: QA
Classification: Unclassified
Component: www (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial
Target Milestone: ---
Assignee: issues@qa
QA Contact: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-05 17:17 UTC by subv3rsiv3
Modified: 2003-05-28 11:40 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description subv3rsiv3 2002-12-05 17:17:50 UTC
Here at my work, we use a mixture of Office 97 and OpenOffice.  The mix works
OK, but not as smoothly as our end-users would like.  The primary issue seems to
be the way documents are saved into native Office 97 format from OpenOffice. 
Many of our end-users call with issues or complaints of formatting or page setup
being lost in the transition back to Excel or Word.  My suggestion is the
development of a complex document with several features for both Word and Excel.
 The idea is that during QA, the documents are imported, then re-exported back.
 After re-exporting, the documents should be examined to determine how much of
the data, metadata, and formatting survived during the transition.

This may not seem like a large issue in an all-OOo environment, but in a mixed
setup (like ours) it can make the difference between adopotion of a new (and
superiour) technology, or a forced upgrade to Office XP.  For an example, please
corss-reference bug 9873, "Print Range Definition fails to export into Excel".
Comment 1 Joost Andrae 2003-05-28 11:40:26 UTC
Joost->subv3rsiv3: I think it's better to discuss this within the
dev@qa.openoffice.org mailing list. Cannot accept this as an issue
Comment 2 Joost Andrae 2003-05-28 11:40:41 UTC
JA: closing issue