Comments and quotes!
Comments on Games Diner content can now make use of quoting. Note the "quote" link underneath content; click that instead of "reply", and you'll get a reply with quote inserted, courtesy of code tags.
It's a similar setup to the SJG forums: you'll have to do some manual editing to pare down the quoted stuff to the part you want, and cut-paste to quote multiple times, but the procedure should be obvious.
Also, word processor-style markup should be available to all comment posters. Sorry, this wasn't visible to some early visitors.
Comment (and quote) away!
Delicious
Digg
Google
Yahoo
Plain text input
The trouble I had was that the "preview" showed me a comment post that looked as expected; then the actual posted comment looked different, all mooshed into a single paragraph.
I immediately disable the gawky "word-processor style" input. I just type in my comment as plain text, like an email message, with blank lines separating paragraphs. If I can't continue to do that and have the comment unmangled, I'll probably stop posting comments.
Let's see what happens to this one.
mangling input for plain text
The trouble I had was that the "preview" showed me a comment post that looked as expected; then the actual posted comment looked different, all mooshed into a single paragraph. I immediately disable the gawky "word-processor style" input. I just type in my comment as plain text, like an email message, with blank lines separating paragraphs. If I can't continue to do that and have the comment unmangled, I'll probably stop posting comments. Let's see what happens to this one.
For some reason the text that appears quoted has been HTML-entity mangled; even for regular ASCII characters like ['] and ["] that should just appear as is because they're supported in every character set. Makes it very awkward to read. The preview shows up correctly; then, the form for posting the comment has reverted to wacko-fancy input. It should be remembering the fact that I've chosen plain-text input.
test using quote and plain text
The trouble I had was that the "preview" showed me a comment post that looked as expected; then the actual posted comment looked different, all mooshed into a single paragraph. I immediately disable the gawky "word-processor style" input. I just type in my comment as plain text, like an email message, with blank lines separating paragraphs. If I can't continue to do that and have the comment unmangled, I'll probably stop posting comments. Let's see what happens to this one.
For some reason the text that appears quoted has been HTML-entity mangled; even for regular ASCII characters like ['] and ["] that should just appear as is because they're supported in every character set. Makes it very awkward to read. The preview shows up correctly; then, the form for posting the comment has reverted to wacko-fancy input. It should be remembering the fact that I've chosen plain-text input.
Test by tbone. Hit "quote", then disabled rich text, then added this line. Quoted text full of HTMLey oddball characters. Will preview.
Preview looked good, but text in input box is back to rich text. Disabled again, added this line. Back to odd HTML characters. Will post without further preview.
mangling input for plain text (reply)
The trouble I had was that the "preview" showed me a comment post that looked as expected; then the actual posted comment looked different, all mooshed into a single paragraph. I immediately disable the gawky "word-processor style" input. I just type in my comment as plain text, like an email message, with blank lines separating paragraphs. If I can't continue to do that and have the comment unmangled, I'll probably stop posting comments. Let's see what happens to this one.
For some reason the text that appears quoted has been HTML-entity mangled; even for regular ASCII characters like ['] and ["] that should just appear as is because they're supported in every character set. Makes it very awkward to read. The preview shows up correctly; then, the form for posting the comment has reverted to wacko-fancy input. It should be remembering the fact that I've chosen plain-text input.
How about in your post to which I'm replying here? You quote yourself in that post, a good way to check things out. Are you seeing mangled input in your post, or the quote within your post? They both look fine to me. They both include apostrophes/quotes, which also look fine to me.
There may be a problem with the system not remembering the plain-text input choice, as I've experienced some bugs when trying to input code when using plain-text input. But that wouldn't explain why your latest post looks fine to me (quote and all) but not to you.
But then there's this thought: if you're selecting plain text input, how are you designating quoted material to begin with? Are you clicking on "quote", then disabling rich text? Not sure whether that should work, as the quote function requires markup tags... Will experiment and report.
Later edit: Reporting on experiment: In the resulting post (test using quote and plain text ), the output looks good to me – almost. I see two different text sizes for my pre-preview input and my post-preview input, and I don't like that. Also, I don't like that I have to switch back to plain text a second time, after doing a preview. But otherwise, while I saw HTML code gibberish in my quoted text after disabling rich text, I didn't see any such gibberish in my outputs, whether preview or post.
I don't know whether that matches your trials, or whether you're seeing garbled final output too. I do appreciate your kindly helping troubleshoot so far. I may need to look into replacing the input system, or possibly the site theme.
If you'd like to add more on the problem, please do – here or by email ( tbone@gamediner.com ). Thanks!
Testing input 2
Logged back in... Things look good for me, with output matching Preview pretty well. I wonder if it's an OS / browser quirk on your side?
(Edited for additional info:)
If you let me know the OS / browser combination, I can try to duplicate the problem. I would like posts to work seamlessly for all.
Also, if line returns are disappearing for you, you could try shift-return instead of regular return at the end of the line. Such workarounds shouldn't be necessary, but it's something to try until everything's working right.
Sorry, I can't offer much else in the way of suggestions without additional info. I'll keep testing on this side, meanwhile.
Testing input
The trouble I had was that the "preview" showed me a comment post that looked as expected; then the actual posted comment looked different, all mooshed into a single paragraph.
T Bone here, test posting as a non-logged-in user. Let's see how the Preview looks, vs the final product...
And a second paragraph, for good measure. No other fancy business.
Post new comment