Hi Christian,
Christian Lippka - Sun Microsystems GmbH - Hamburg wrote:
> than this is a bug in Microsoft Office, most likely in the Mac version.
> OpenOffice.org can do nothing about it.
I can agree with you. I would say the same if I were in your shoes.
Regardless of whether OpenOffice.org itself would handle with the situation, I
would need to treat the situation since users in their workplace actually use
several versions of Office and OpenOffice.org is also used as a server process
to convert document files.
I guess, but I am not currently sure though, it might be relatively easy to
achieve it.
1. Determine a version number of Office which was used to edit the document.
I am not sure, but that seems around ...
svx/inc/svx/svdfppt.hxx
sd/source/filter/pptin.cxx
struct SVX_DLLPUBLIC PptCurrentUserAtom
{
sal_uInt32 nMagic;
sal_uInt32 nCurrentUserEdit;
sal_uInt16 nDocFileVersion;
sal_uInt8 nMajorVersion;
sal_uInt8 nMinorVersion;
String aCurrentUser;
struct PptUserEditAtom
{
DffRecordHeader aHd;
INT32 nLastSlideID; // ID of last
visible slide
UINT32 nVersion; // This is
major/minor/build which did the edit
UINT32 nOffsetLastEdit; // File offset
of prev PptUserEditAtom
UINT32 nOffsetPersistDirectory; // Offset to
PersistPtrs for this file version.
UINT32 nDocumentRef;
UINT32 nMaxPersistWritten; //
Gesamtanzahl der Persisteintraege bis hierher.
INT16 eLastViewType; // enum view
type
2. Reset the bits, fFlipH and fFlipV, in svx/source/msfilter/msashape.cxx
during importing the file if the version number matches certain criteria.
Any thoughts?
Regards,
Tora
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
