http://bugs.winehq.org/show_bug.cgi?id=14980
--- Comment #6 from Anastasius Focht focht@gmx.net 2008-08-25 04:31:20 --- Hello,
--- quote --- Thank you for the detailed explanation. Yes, setting riched20 to native,builtin does enable Powerpoint 2007 to open normally.
So is this a WONTFIX? --- quote ---
The version shipped with M$ Office suite can be seen as a 'private' one, entirely under control of Office Dev Team.
From my knowledge, Wine RichEdit is aimed at v2.0/v3.0 shipped with Windows OS
and implements the public API/Interfaces described in the SDK.
If the Windows OS folks decide to release a newer RichEdit version with features of the "bleeding edge" Office RichEdit component backported and the SDK is updated describing the new features then Wine should keep up.
So, yes - currently I tend to say "WONTFIX" because this (internal) stuff is subject to Office RichEdit only. Though that could change one day ...
Maybe you could add some comment to APPDB, stating that for PowerPoint 2007 (and potentially other Office components) to work correctly, the load order for riched20.dll has to be changed to "native-then-builtin". The statement to use native "riched20.dll" (copy or winetricks) is plain wrong. Office will load the 'private' one, skipping the native from system32.
Various Office 2007 HOWTO's seem outdated anyway and need some cleanup.
Regards