Whenever I edit a post with a lot of spoiler blocks, it destroys everything after the first spoiler block. Can you change that?

Emo--This is a problem that has been happening for awhile. Currently the work around is to copy all the text into a separate doc and edit it their and bring it back. You will need to re-type all of your spoiler tags and content.

I haven't tried it yet, but you may be able to "Quote" your post so that it includes all the tags and copy that text to minimize what you have to retype.

HTH!

Okay... cool.

Do the admins know about this problem?

Yes, and personally, it drives me nuts. Unfortuantely, eidolon and I have limited abilities. Adam and Bull are the ones that would have to do anything, and they're both pretty swamped at the moment. In other words, make do until they get a chance to work on it I suppose.

We are aware of this bug -- and have been for years -- and it will not be fixed in this version of the software.

This is one of the reasons I do not suggest putting billions of spoiler tags in a post when posting a character sheet.

Have you talked to the people who made this software about the problem?

It's an older version of the forum software, they most likely don't support it anymore (their response would be "upgrade and ask us if it's still broken").

Unfortunately, when software advances, you either advance with it or learn to fix it yourself. (Or both, but you don't usually have to.)

Hmmm will this go away no that we upgraded??


block 1


block 2


Block 3

Hmmm this was spoilered with the insert button

Hmmm looks like multi-spoilers work now but all the text was blacked out......

So the new way to read spoilers is to highlight the blacked-out text? Is that how it is to be done? I'm not sure I like that, sometimes it was nice to hide huge blocks of text (like full character write-ups) in spoiler blocks, so that people could read them if they wanted. As it is, it would just turn into huge blocks of blacked-out text, right?

The spoiler issue is being looked into by Redjack. He said he was going to do his best to put them back the way they were before.

Spoilers fixed..
AND you can edit a post with multiple spoilers now.

When I edit a post sometimes the punctuation, such as apostrophes, dashes, quotes, etc. become blocks of unreadable code. Is this something fixable, and can we look forward to it being fixed in the future?

Just in the spoilers? Or anytime you edit a post? I do quite a bit of post editing and haven't noticed this phenomenon.

It's been predominantly in the spoilers, but once or twice today when I went to edit it happened in the main body of the post.

Editing a regular post elicits this problem much less frequently, at least in my experience to date.

WinterRat1 -- could you please either post here, or if you'd prefer PM Redjack and myself with your OS and browser (and version numbers)? I haven't seen this behavior on any of my machines/browsers, and I'd like to try to replicate it.

My apologies, I'm a technological idiot. How do I find my browser and version numbers?

I have to check what my OS (I assume this means Operating System?) is.

I think it might have something to do with when one writes up a post in MS Word (yes, it's the devil or whatever) and then cuts and pastes it into a post. I know that's what I do and it often has those issues when editing later.

In my case (in case it helps with the diagnosis) it's Firefox (Latest Upgrade, as of 2/7 I believe) and Word 2007.

I know my quotes come out all wonky looking in the copying and some of the other chars too (dashes on occasion as well).

Hope that helps!

If you're writing text "offline" to paste into the forums, I highly recommend you always do it in a plain text editor. If the editor can save and read RTF files, there's always the chance for wackiness in certain characters.

Oh sure.. NOW you tell me

Notepad it is!

If you're on a Mac, then it's click on the Apple, and select "About this Mac" That'll pop up your OS version. (e.g. 10.4.10)

If you're on windows, right-click the "My Computer" Icon and select properties. That should bring up a menu of information telling your version of Windows. (e.g. Windows 98 OSR2, Windows XP SP2, etc.)

From the browser, there'll be an "About <Insert Browser Name Here>" either under the application menu (Mac) or under the help menu (Windows). e.g. Firefox 2.0.0.11

Since you're not a technophile, I'm guessing you're not on another flavor of Unix, so I won't go into those details.

If you're using OS/2 or Plan 9, you probably just need to say that and skip the version for right now.

~J

Hah! I have discovered the issue!

Ok, the "quick edit" is broken past the point of uselessness into active harmfulness. It mangles unicode something fierce, and gives no warning while doing so.

Testing to confirm: †…—¡

Testing with full edit: everything works

Testing with quick edit: horribly broken

Yeah, I recommend disabling quick editing.

~J

I have yet to use the Full Edit, and have use the Quick Edit feature well into the high double figures (almost triple by now), and have yet to experience any kind of problem.

I even used the Quick Edit on this post.

You also didn't use any non-ASCII characters.

~J

You mean like â„¢?

Edit: Hmmmm... That was supposed to be ™.

Edit #2: But editing a second (and third and fourth and fifth) time doesn't screw up the second or third instance of ™.

Edit #3: I really like the Quick Edit feature, and am willing to edit ASCII characters in order to keep it.

Sorry about the delay in my reply! Here's my information:

Operating System: Microsoft Windows XP Professional Version 2002 Service Pack 2

Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12

Also, Kagetenshi is correct, the errors occur on ASCII characters when I use Quick Edit.

I agree with Fortune, I do like the Quick Edit, but it is a tremendous PITA to edit ASCII characters on large posts. If it can be fixed, it would be really nice.

Thanks for looking into this Dunner, let me know if there's anything more you need from me.

Incidentally, I did not edit the last (supposedly messed up on purpose) post above. The first instance of â„¢ in that post should still be messed up, as that is how I left it. Maybe the problem fixes itself after reloading (or some other mysterious reason).

Any updates on this, I'm still having problems with the Quick Edit function, from various computers.

There are no updates to this forthcoming. Unicode is not currently supported under Quick Edit. To get unicode support, use Full Edit.

OK thanks much. My apologies, but I'm kind of a computer moron so a little clarification would help me going forward.

What is 'unicode'?

Extended characters (beyond upper and lower case, numbers, standard punctuation on the keyboard) require special support. This is baked into the full editor, but not the quick editor. In order to use and retain these special characters, you will need to use the full editor.