Quick Answers : code tags are not working
-
I just tried to edit that answer and when I clicked "Update answer!", it just navigated back to the question/answer and no new version was added (i.e., the change was not applied). Strange.
Dang.. looking into this now!
-
Dang.. looking into this now!
Is Dang one of the new site admins? :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
-
Is Dang one of the new site admins? :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra]
Actually.. it's one of the CP hamsters :)
-
Me too. At one point the Preview showed what appeared to be a correct rendition of the content, but when I pressed the Update button it reverted. I did notice that it is using a new version of the editor (maybe with Luc Pattyn's code validator?).
MVP 2010 - are they mad?
Hoi. Yes, my code has been adopted, and I don't know how they exactly use it, the goal was to call it only when actually pasting something; so simply typing text (even HTML tags) should work as before. I tried to edit that message; I am able to, I see a CODE tag, it simply doesn't get interpreted. So my guess is the logic works as if the "ignore HTML tags" is checked (which it often is). IMO the purpose AND the wording of the checkbox are wrong. The goal was to eliminate checkboxes as much as possible; IMO there should be: 1. a set of radio buttons, defaulting at auto (OK), just in case the logic fails to recognize what gets pasted; 2. a checkbox to deal [REWORDED] with HTML tags while something is being pasted and happens to be treated as text (because auto detect decided it was text, or the user forced it to be text) [/REWORDED]; so I would call it "escape HTML tags while pasting text"; that is quite different from the current wording, and I can't tell how it matches the current implementation. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
modified on Wednesday, January 20, 2010 5:13 PM
-
Actually.. it's one of the CP hamsters :)
Hi Thiru, I just added a reply to Richard's message above. Please have a look. Also, feel free to remove my edits to the answer message mentioned in the OP. Cheers.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
-
Hi Thiru, I just added a reply to Richard's message above. Please have a look. Also, feel free to remove my edits to the answer message mentioned in the OP. Cheers.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
No worries. I did the same kind of testing ;)
-
No worries. I did the same kind of testing ;)
It seems that quoting some others text is also getting language based styles. The whole text is coming in yellow background (like pre tag) and words like 'and' is highlighted.
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
-
It seems that quoting some others text is also getting language based styles. The whole text is coming in yellow background (like pre tag) and words like 'and' is highlighted.
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
Yikes. Thanks for the report.
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
-
'Code' tags for showing inline code blocks is not working. >>> Set the <code>src</code> property of the <code>iFrame</code> object to the page containing the new data you want to show. I tried to edit an answer[^] (with out checking who posted it!), but was not able to do it. It seems that the checked state of 'Ignore HTML tags' checkbox is always checked and is not getting saved properly.
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
Sorry - bug fixed.
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
-
Hoi. Yes, my code has been adopted, and I don't know how they exactly use it, the goal was to call it only when actually pasting something; so simply typing text (even HTML tags) should work as before. I tried to edit that message; I am able to, I see a CODE tag, it simply doesn't get interpreted. So my guess is the logic works as if the "ignore HTML tags" is checked (which it often is). IMO the purpose AND the wording of the checkbox are wrong. The goal was to eliminate checkboxes as much as possible; IMO there should be: 1. a set of radio buttons, defaulting at auto (OK), just in case the logic fails to recognize what gets pasted; 2. a checkbox to deal [REWORDED] with HTML tags while something is being pasted and happens to be treated as text (because auto detect decided it was text, or the user forced it to be text) [/REWORDED]; so I would call it "escape HTML tags while pasting text"; that is quite different from the current wording, and I can't tell how it matches the current implementation. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
modified on Wednesday, January 20, 2010 5:13 PM
The issue was a bug whereby you couldn't change the format of a post. This has been fixed. The wording for pasting is very clear - as provided by the radio buttons The "Ignore HTML in text (good for code snippets)" is needed for those who type in code manually. I'm open to suggestions for wording. [default: true] "I will be using HTML tags in this message" [default: false] "My text contains < and > - do not treat them as HTML tags" [default: false] "Display HTML tags and entities as code - do not process them" What's something clear and concise?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
-
The issue was a bug whereby you couldn't change the format of a post. This has been fixed. The wording for pasting is very clear - as provided by the radio buttons The "Ignore HTML in text (good for code snippets)" is needed for those who type in code manually. I'm open to suggestions for wording. [default: true] "I will be using HTML tags in this message" [default: false] "My text contains < and > - do not treat them as HTML tags" [default: false] "Display HTML tags and entities as code - do not process them" What's something clear and concise?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
I'll have to come back on this one. I'm on the way out right now, and I need to walk through all the use cases first. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
-
The issue was a bug whereby you couldn't change the format of a post. This has been fixed. The wording for pasting is very clear - as provided by the radio buttons The "Ignore HTML in text (good for code snippets)" is needed for those who type in code manually. I'm open to suggestions for wording. [default: true] "I will be using HTML tags in this message" [default: false] "My text contains < and > - do not treat them as HTML tags" [default: false] "Display HTML tags and entities as code - do not process them" What's something clear and concise?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
I like the second one best. The first is poor because what happens with code with inequality statements is ambiguous. The third isn't as good as the second due to the level of technical knowledge in the wording. At first glance I'd assume that only affected actual HTML things and that if i typed inequalities in my code that how they were displayed would be unaffected by it's setting.
3x12=36 2x12=24 1x12=12 0x12=18