So let's go.
NOTE: this installation procedure was tested on Office11 Pro (Office2003 Pro). It can be adapted for another versions.
 
- You need fresh wine. 0.9.29 is suitable for our needs. Download, configure, make, make install
- ITS HIGHLY recomended to set environment variable LANG to "C", before running "wineprefixcreate". There is some i18n related issues between wine, InstallShield and etc. Later, if you app support your native language, you can use it inside app. Of course wine must be properly configured.
- tools/wineprefixcreate will make working ~/.wine directory.
- Now switch environment variable LANG back. Well, LANG manipulations
were needed to force above script use only ASCII characters in ~/.wine directory. Maybe it is not needed. But sometimes apps wont install without this workaround. You might choose to experiment with this and see what happens :)
 
- Make sure you have msxml3.dll working. You can use native (msxml3.dll msxml3a.dll msxml3r.dll) or builtin (not tested) version. In native case do "wine regsvr32.exe msxml3.dll" in the windows/system32 directory. Also override dll settings for msxml3 in winecfg(msxml3.dll must be only native). If msiexec will complain about xml or xml2 at startup - you've done something wrong :).
 
- Wine is ready. But not the Office11 itself :-/. All installation instructions resides into .msi files, shipped with program.
In our case it is OWC10.MSI(needed by uninstall? ) OWC11.MSI, and PRO11.MSI. And we need some edit tool for them.
 
- I used Orca from astebner.sts.winisp.net/Tools/Orca.zip. It contains stand-alone .msi file(~1.6 Mb), instead of full Platform SDK (~250Mb). You can install it as usual:
wine msiexec /I Orca.Msi from directory where you download files.
 
NOTE: This program requires NATIVE msi installer to work and MFC42u.dll. You can find MFC42u.dll here: www.dll-files.com.
INSTMSIW.EXE is installer's archieve. Google for it. Then create SEPARATE .wine directory (use --prefix option for wineprefixcreate or just rename existing .wine directory. Later, you can simply make symlink to switch back). Remove or rename msi.dll and msiexec.exe from system32 and in winecfg force wine to use native ones. Run "wine INSTMSIW.EXE" !!TWO!! times( wine behaves strange: after the first invocation it fails, after the second - installs normally). Then do "wine msiexec /I Orca.Msi". Then copy MFC42u.dll to drive_c/windows/system32 directory and regserv it ( "wine regsvr32.exe mfc42u.dll" cd into system32 directory before regserving). Orca ready.
 
- Now copy all the content of you Office11 CD to HDD, open .msi files, mentioned above, one by one in Orca and do same things with each:
- Choose table InstallExecuteSequence from the left. You will see content of this table in front of you. Search in "Action" column for strings "ShedSecureObjects" and "ExecSecureObjects". Cut them (scissor icon in toolbar )
- Save the results and edit next .msi
 
- Switch back to fresh .wine, which you create at the first step (make a symlink - it is simplier). From the folder where fixed .msi resides
run "wine msiexe /I PRO11.MSI" (in you version this file may have different name - use .msi with maximum length ;) ). Follow the instructions.
 
Installer may fail with unhandled exception. BUT after the registration! So just run the same command once more, choose repair option and wait. After that you will have working word excel and powerpoint ( don't forget to choose them and only them in customization dialog during install).
 
P.S. There was a long way, don't it? :). You and maybe I could make some mistakes. Please try this way and report your results. I will
keep an eye on this thread.
 
P.S.S Maybe more installation steps in .msi must or may be excluded? Maybe even native install can deal with wine and stripped .msi? I dont know yet. More investigation needed. Another sad thing - your can't fine tune your installation due to unfinished msi.dll in wine... I hope they will work on it :)