WYSIWYG

[Brian]

Thanks.

It seems to be breaking for me too in Safari, as well as in Firefox, so it may very well have to do with how the forum is handling the post.

I've submitted a bug report to the devs to see what's going on with that post. In the meantime, I'd like to request that you not make any modifications to the post.

[kpatch]

Thanks Brian! Not making modification shouldn't be a problem ... since I can't. LOL. I'm stepping away from the post.

[Tim Camara]

The problem was a stray character from whichever word processing program you were using to compose the post. I've handled the stray characters, so this will be fixed the next time we push out an update.

[Jessecast]

If you don't mind an extra step you can paste it in notepad then copy it to your forum so you wouldn't have to delete each extra space and what not

[kpatch]

Thanks Jessecast! Good suggestion. I tried that the other day and it worked like a charm.

And thanks for that information Tim Camara. Would it help me to know what the stray character was, so I can be on the lookout for it?

[Tim Camara]

It shouldn't matter now, the character will be automatically stripped out. It was this character, if you're interested.

[Chris]

Tim Camara from a coding perspective, are the other Unicode characters that ECMAScript says should be treated as whitespace also recognized?

• \u0009 — Tab — \t
• \u000a — Line feed — \n — (newline character)
• \u000b — Vertical tab — \v
• \u000c — Form feed — \f
• \u000d — Carriage return — \r — (newline character)
• \u0020 — Space
• \u00a0 — No-break space
• \u1680 — Ogham space mark
• \u180e — Mongolian vowel separator
• \u2000 — En quad
• \u2001 — Em quad
• \u2002 — En space
• \u2003 — Em space
• \u2004 — Three-per-em space
• \u2005 — Four-per-em space
• \u2006 — Six-per-em space
• \u2007 — Figure space
• \u2008 — Punctuation space
• \u2009 — Thin space
• \u200a — Hair space
• \u2028 — Line separator — (newline character)
• \u2029 — Paragraph separator — (newline character)
• \u202f — Narrow no-break space
• \u205f — Medium mathematical space
• \u3000 — Ideographic space

*proposal to also include

• \u0085 — Next Line

was also made pre-harmony

[Tim Camara]

The system should, by default, handle any escaped Unicode characters like the ones you posted. The original problem arose with the format U+2028. Even in that format though, the majority of Unicode characters should work just fine, since they don't cause a line ending. The only ones that should be an issue are these: www.ecma-international.org/ecma-262/5.1/#sec-7.3, which I believe are all handled now.

[kpatch]

I notice that WYSIWYG or Visual is now Preview. But I also notice that when I paste from an existing document, whether it's in Pages or from a text edit file, it looks all wrong before I hit Create Message, Create Post, or Create Thread, etc. It is totally squished together. No spaces between sentences or paragraphs. It looks like one long run-on sentence. But when I go ahead and post, it looks more or less the way it's supposed to look. My point is, I can't tell pre-posting whether it looks right, so what I see, is not what I get. Hope that made sense.
The only way I can recreate it is by doing a screen shot, pre-post, because once I post, as I said, it looks more or less okay, but I can't tell what it's going to look like before I post. So if there are any issues, I have to go in and edit after posting.

Thank you.


myhourglass.proboards.com

[Ryan Roos]

Apr 21, 2013 7:55:31 GMT -8 kpatch said:

I notice that WYSIWYG or Visual is now Preview. But I also notice that when I paste from an existing document, whether it's in Pages or from a text edit file, it looks all wrong before I hit Create Message, Create Post, or Create Thread, etc. It is totally squished together. No spaces between sentences or paragraphs. It looks like one long run-on sentence. But when I go ahead and post, it looks more or less the way it's supposed to look. My point is, I can't tell pre-posting whether it looks right, so what I see, is not what I get. Hope that made sense.
The only way I can recreate it is by doing a screen shot, pre-post, because once I post, as I said, it looks more or less okay, but I can't tell what it's going to look like before I post. So if there are any issues, I have to go in and edit after posting.

Thank you.


myhourglass.proboards.com

When you paste from somewhere else you should paste into BBCode mode. We do not have any guarantee or promise that pasting into Preview mode is going to keep or maintain any formatting. I don't know if we've done so yet, but we plan to actually strip all formatting when someone pastes (into Preview) because people keep getting confused like yourself. So if it isn't doing it already it will be just plain text when you paste soon. But you should be composing posts yourself in one of the two the editors we provide you for the best experience. I hope that helps you in the future.