Word Processors & vBulletin UTF-8 Stripped Posts (Possible Fix?)

[Asilouhuette]

I tried this fix and unfortunately it didn't work for me.

I'm not sure that it is really a bug so much as a poor choice of character encoding on my part. Choosing UTF-8 may have let me avoid this.

I tried fixing it myself, with varying amounts of success. I tried placing an str_replace() that replaces smartquotes and other special characters with their $blah; counter parts. This gave me some improvement, however, I couldn't find the most optimal place to put this. I tried having it change the $dataman->['pagetext'] after the various _presave hooks but that didn't fix all cases. It would only work with edits || new posts, not both, for example.

Could anyone point me to which hook would be caught by all posts/post edits and which variable would be best to change at that hook?

I think it would be fairly trivial to do this if I didnt use a hook, but that of course makes maintaing updates much harder. Here is the str_replace I'm using...

PHP Code:

    $wordentities = array(chr(128), chr(130), chr(131), chr(132), chr(133), chr(134), chr(135), chr(136), chr(137), chr(138), chr(139), chr(140), chr(145), chr(146), chr(147), chr(148), chr(149), chr(150), chr(151), chr(152), chr(153), chr(154), chr(155), chr(156), chr(159));                
    $htmlwordentities = array('€', '‚', 'ƒ', '„', '…', '†', '‡', 'ˆ', '‰', 'Š', '‹', 'Œ', '‘', '’', '“', '”', '•', '-', '—', '˜', '™', 'š', '›', 'œ', 'Ÿ');
    return str_replace($wordentities, $htmlwordentities, $text); 


Thanks in advance.