[quote][b]Posted by:[/b] CAVX I know it's a big inconvenience, but the webteam made the change to secure the website, make it harder to bypass the filter, prevent silly unicode hacks like some I've seen that would cause a lot of chaos, etc. It was still a good move.[/quote]Like I said, I think the idea behind it was an intelligent one. And I think that, if it didn't disrupt the normal motions of the site, it would be a great feature- one that I would be more than happy to have. But it's clearly interrupting some of the larger, more intelligent posts that come from the Community- I can't use Word anymore to create things to post on Bungie. I now have to do [i]everything[/i] in this window here. That's going to really, [i]really[/i] discourage me from making larger threads now, even if I wanted to. It's affecting debate, entertainment- hell, even map submissions to Atlas, which could affect Halo 3. A good experiment, in my opinion, but I think we all need to learn when enough is enough- I've had enough of this test, I'm not sure on the rest of you. Perhaps there's a different way to get the same results that would interrupt the site less. I doubt it, but maybe. Or perhaps there's a more watered-down version of this that could be put up that would decrease the possibility of such things occurring while still allowing the site to move normally. But personally, I'm saying right here and right now that I think we've (the Community) seen all we need to see to know that this isn't a flawless execution. [quote]I've been looking for easy ways to filter out unicode and I think I found one. I haven't experimented a lot with this method though but you should consider giving it a try. The method in question converts extended unicode characters to question marks. Note that I'm running Vista with Word 2007 installed. -Open Word. -Copy and paste your text into Word. -File > Save As. -Change "Save As Type" to "Plain Text". -Click "Save". -Change "Text Encoding" from "Windows (Default)" to "MS-DOS". -Click "OK".[/quote]It's a good idea if it works, and for those who have Word 2007. But I don't, so I can't use this feature. Part of the things we as a Community need to realize is that the problem isn't insulated to us- we shouldn't just talk amongst ourselves and find a way around it while we forget that the rest of the site is having this issue as well, and they don't know how to fix it. Rather, we need to be looking at the problem overall, and how we can fix it for [i]everyone[/i], not just ourselves. I've made my suggestions, I'd love to see others make theirs.