http://bugs.winehq.org/show_bug.cgi?id=14980
--- Comment #7 from dimesio@earthlink.net 2008-08-25 13:34:34 --- (In reply to comment #6)
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.
That makes sense, but then shouldn't Wine automatically use the richedit provided with Office? That's how it works in Windows. Is an "automatic override" feasible, or would it cause too many other problems? I ask because this seems likely to be the underlying cause of more Office bugs than just this one (and bug 14041), and Office is often one of the first apps installed by newbies who don't have a clue how to set an override.
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".
Done.