{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
2/16/2009 10:57:39 AM
26
* The text contains extended characters that are not allowed
I was just posting part of a fanfic in a group, when I got this message, disabling me from posting.
I don't have any long sequences of letters in the piece, and I've tried editing the swear words to -blam!- (I literally did just type out the word the filter applies) or inserting a 1 into ...faeces. Still getting nothing. Any ideas? Want me to post the piece?
-
[quote][b]Posted by:[/b] Elite Mouse It isn't that hard to just copy your damn post before you click submit.[/quote] I use it solely when it takes more than one post to hold it all. EDIT: Well apparently we can still use invisible characters... [Edited on 03.18.2009 3:18 PM PDT]
-
[quote][b]Posted by:[/b] BadBall3r47 Is there a point to it anyway?[/quote] For the most part, it prevents the use of adding an invisible character to a curse word to make it come out perfectly clear. Found that out a few days ago, oh well. It isn't that hard to just copy your damn post before you click submit.
-
noted
-
Happened to me. If you typed it in Word, [b]every[/b] apostrophe and quotation mark is not postable. You have to open it in Notepad and replace every single one. You'll know it's working because the replaced ones are straight and bigger. Or do what CAVX says, lol. [Edited on 03.18.2009 2:56 PM PDT]
-
I hope this doesn't count as a bump; especially since I actually used the search bar rather than making some complaint topic about this. [quote][b]Posted by:[/b] CAVX 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". -Close Word and re-open the document you just saved to see the changes. [/quote] So does this mean the odd things I see in the text (in this case being words surrounded by question marks as well as the word Barrier) are the same things causing the issue? If I simply have to remove them this could be a life-saver for a two to three post thread I'm working on. -Not a bump whatsoever
-
[quote]harder to bypass the filter[/quote] They failed pretty badly. I can still curse like a sailor using the alt + 0173 trick in Private Groups and the Mains if I wanted.
-
[quote][b]Posted by:[/b] CAVX [quote][b]Posted by:[/b] Tartan 118 I kept having to go to the editing page of my Freewebs page and then wait for all apostrophes and quotation marks to appear as small question marks on diamonds before I knew Bnet wouldn't screw it over. That absorbed some time. =/[/quote] May I also suggest simply typing your posts through Bungie.net or through Notepad then? Typing posts in Word will often generate those characters, especially quotation marks, unless you change a lot of settings. You're far more likely to construct a passable post through Notepad or simply through the post box on this site. (Copying and pasting into Notepad or the post box won't delete the characters, but Notepad and the post box here don't have silly formatting that easily adds extended unicode when you type. Essentially they'll prevent that extended unicode from being added but they won't keep it out if you C&P.)[/quote] I'm quite happy to do spontaneous posting with this text box, but as I said, it's a fanfic that I was trying to post, with chapters around 8 or 9 pages long, and with 16 chapters. So retyping the entire thing on here, with formatting (which I may have grown used to now, I can't tell) will be awfully time-consuming, even if it [i]is[/i] only one chapter per week.
-
[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.
-
[quote][b]Posted by:[/b] Mister Magoo It appears now that there are several pinned topics in my group that cannot be edited. For example, we have an archive of all of our helpful resources and now I cannot edit it to add new information.[/quote] If you have Microsoft Word, copy and paste your threads into a Word document and follow the steps I listed a few posts above. You'll be able to locate any extended characters because they'll turn into question marks when you open the document again. Generally you're looking at bullet points and fancy quotation marks as your culprits.
-
It appears now that there are several pinned topics in my group that cannot be edited. For example, we have an archive of all of our helpful resources and now I cannot edit it to add new information.
-
[quote][b]Posted by:[/b] Tartan 118 I kept having to go to the editing page of my Freewebs page and then wait for all apostrophes and quotation marks to appear as small question marks on diamonds before I knew Bnet wouldn't screw it over. That absorbed some time. =/[/quote] May I also suggest simply typing your posts through Bungie.net or through Notepad then? Typing posts in Word will often generate those characters, especially quotation marks, unless you change a lot of settings. You're far more likely to construct a passable post through Notepad or simply through the post box on this site. (Copying and pasting into Notepad or the post box won't delete the characters, but Notepad and the post box here don't have silly formatting that easily adds extended unicode when you type. Essentially they'll prevent that extended unicode from being added but they won't keep it out if you C&P.) [Edited on 02.16.2009 8:54 AM PST]
-
I kept having to go to the editing page of my Freewebs page and then wait for all apostrophes and quotation marks to appear as small question marks on diamonds before I knew Bnet wouldn't screw it over. That absorbed some time. =/
-
[quote][b]Posted by:[/b] Lord Snakie I think the idea behind this was a smart one, but I also think that it's becoming increasingly apparent that this was a bad move on the WebTeam's part.[/quote] 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. 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". -Close Word and re-open the document you just saved to see the changes. [Edited on 02.16.2009 8:57 AM PST]
-
Yea, I got this on a 3-post, almost 30,000 character report I typed up for one of my Private Groups. I was [i]not[/i] pleased. 5 hours of my life was dedicated to fixing that problem- and I only got through the first two posts without any major issue. For the third, I had to actually literally map out every single one of the problem spots using process of elimination, and manually type up every problem spot- link and all- from the open Word document that I had, straight into Bungie. What I did was take the text from the thread, then I cut it down, line-by-line, until I was able to post it. I did this from the bottom of the text to the top, and then the top to the bottom. Then I cut out the sections that hinted they had problems with it from the Word Document, and I cut out sentence-by-sentence until I was able to post it, and (using this) I was able to find the exact lines that were causing issue. I then rolled over to Word, and mapped the entire post with highlighters. I found out that I had three sections with major issues in them, one of them was simply a line (which I bit the bullet on and just cut out) but the other two sections were large, and important. So I had to go to a Bungie.net window and type these things up, word-for-word, hyperlinks and all, until I got past those sections and was able to post it. I think the idea behind this was a smart one, but I also think that it's becoming increasingly apparent that this was a bad move on the WebTeam's part. This is the one part of the update that I, hands-down, think is absolutely horrible.
-
It means that you have a character in your text that is not allowed on B.Net. The only way to get rid of this is to cut different paragraphs out of your text and then click preview. If then the message goes away, delete the cut text and try and manage without it. If the message persists, cut out another random paragraph etc. Repeat these steps until you find the source of the problem.
-
I only get the message when I try to insert some special characters such as superscript TM. I updated that section of the update into my OP (in the other thread) just a second ago.
-
[quote][b]Posted by:[/b] burritosenior [quote][b]Posted by:[/b] BadBall3r47 Is there a point to it anyway?[/quote] Gets rid of pictures things you can copy and paste I suppose.[/quote]Well they should allow quotation marks.
-
[quote][b]Posted by:[/b] BadBall3r47 Is there a point to it anyway?[/quote] Gets rid of pictures things you can copy and paste I suppose. But yeah, I just wrote two sentences in a thread and got it. I removed all punctuation... nothing. Tried retyping it, nothing. Reworded it completely... nothing. Kinda sucks if you did type something long -.-
-
Is there a point to it anyway?
-
[quote][b]Posted by:[/b] BlueSkyfish I think this new forum restiriction is working against quality posts. Those who do make decent intricate posts have often typed them into word first to use spelling help or to save the text and avoid it getting lost due to browser or net problems. Now that it is nearly impossible to copy past from normal writing documents, more texts will be lost and usuallydon't bother to retype long posts, or if they do, its not going to be as good as the first one usually.[/quote] Yup, that happened with the group refits a while back, and, when my laptop -blam!-s up, i.e. I press backspace and it goes back a page rather that deleting a single character.
-
I think this new forum restiriction is working against quality posts. Those who do make decent intricate posts have often typed them into word first to use spelling help or to save the text and avoid it getting lost due to browser or net problems. Now that it is nearly impossible to copy past from normal writing documents, more texts will be lost and usuallydon't bother to retype long posts, or if they do, its not going to be as good as the first one usually.
-
[quote][b]Posted by:[/b] Omnicent Yeah, it's been happening alot. To fix it you must take your work, copy it into notepad then copy it into your post-box. If that doesn't work, try to find the part with the bad characters and re-type it. Word will simply not work, infact, if you copied from word then that's your problem, it doesn't like that.[/quote] Mkay. Guess it's not too bad then. Just double the amount of copy and paste. Thanks. Maybe just retyping it straight from Word into the post body may work. I have a Freewebs page. I'll try that. [Edited on 02.16.2009 3:34 AM PST]
-
[quote][b]Posted by:[/b] PETERSON4 [quote][b]Posted by:[/b] Omnicent Yeah, it's been happening alot. To fix it you must take your work, copy it into notepad then copy it into your post-box. If that doesn't work, try to find the part with the bad characters and re-type it. Word will simply not work, infact, if you copied from word then that's your problem, it doesn't like that.[/quote] Notepad didn't work, and I frankly didn't feel like typing the damn thing over again. [/quote] I know the feeling, I had to re-write my map submission because of this problem. . . 3 hours of my life I'll never get back. . . But I saved some time by isolating the problem areas and just redoing those.
-
[quote][b]Posted by:[/b] Omnicent Yeah, it's been happening alot. To fix it you must take your work, copy it into notepad then copy it into your post-box. If that doesn't work, try to find the part with the bad characters and re-type it. Word will simply not work, infact, if you copied from word then that's your problem, it doesn't like that.[/quote] Notepad didn't work, and I frankly didn't feel like typing the damn thing over again.
-
Yeah, it's been happening alot. To fix it you must take your work, copy it into notepad then copy it into your post-box. If that doesn't work, try to find the part with the bad characters and re-type it. Word will simply not work, infact, if you copied from word then that's your problem, it doesn't like that.
-
I know, it sucks. I screenshotted the story, got the pics on photobucket, and posted them. The crappy alternative, and the main reason I hate this update.
