http://bugs.winehq.org/show_bug.cgi?id=14980
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-01 02:20:57 --- (In reply to comment #8)
One could check if loading of RichEdit component is requested using full path outside of standard locations (system32) - the way Office does - and try the one from private path first before falling back to standard load order behaviour.
I asked Alexandre once if changing LoadLibrary behaviour when it's called with full path to avoid loading a builtin in that case is possible/feasible (windows\system32 case works automatically if there is a placeholder DLL there). Alexandre answered that it's a bad idea, I don't remember real arguments off the top of my head right now.