Publishing process at Code Project
-
I do not know what's going on. Sean has, as usual, been a great help. But there are serious problems with the publishing process at Code Project. 1. In attempting to use a PNG within a recent article, I was thwarted by something I had no control over. Were it not for Sean, the PNG would never have appeared in the final published article. 2. When I viewed the published article, I found that an HTML end-tag was removed. The original HTML was If set true, the first row will be treated as .... In the published article it appeared as (note the missing ): If set true, the first row will be treated as .... This of course caused the word "true" and all following text to appear in RoyalBlue. 3. There appears to be no way in which to colorize objects within a
block. In my current article this requires a significant increase in the concentration needed to understand the article. What was simple became difficult because I could not color-code some pseudo-code. What concerns me is that these kinds of bugs are rampant. Furthermore, the paper that was finally published diverged significantly from my intent. It does not matter if I check "keep your fingers off my HTML". The changes are occurring somewhere within the Code Project publishing paradigm. By including the Code Project stylesheets in the of my documents, I thought that I could preview what I expected to see in the final Code Project article. But when it gets published, the results are different from what I saw in Firefox. This is unacceptable from an authoring standpoint. I put a lot of work into creating an article for Code Project. I appreciate the overarching philosophy to have all articles appear with the same styling. But, when I follow the "rules" and bad things happen, I must question the process involved. It's time to fix the publishing process at Code Project! I, as usual, stand ready to help. [Edited: turned on "Treat my content as plain text, not as HTML" to allow Gus' HTML tags to appear in the text] Gus Gustafson
-
I do not know what's going on. Sean has, as usual, been a great help. But there are serious problems with the publishing process at Code Project. 1. In attempting to use a PNG within a recent article, I was thwarted by something I had no control over. Were it not for Sean, the PNG would never have appeared in the final published article. 2. When I viewed the published article, I found that an HTML end-tag was removed. The original HTML was If set true, the first row will be treated as .... In the published article it appeared as (note the missing ): If set true, the first row will be treated as .... This of course caused the word "true" and all following text to appear in RoyalBlue. 3. There appears to be no way in which to colorize objects within a
block. In my current article this requires a significant increase in the concentration needed to understand the article. What was simple became difficult because I could not color-code some pseudo-code. What concerns me is that these kinds of bugs are rampant. Furthermore, the paper that was finally published diverged significantly from my intent. It does not matter if I check "keep your fingers off my HTML". The changes are occurring somewhere within the Code Project publishing paradigm. By including the Code Project stylesheets in the of my documents, I thought that I could preview what I expected to see in the final Code Project article. But when it gets published, the results are different from what I saw in Firefox. This is unacceptable from an authoring standpoint. I put a lot of work into creating an article for Code Project. I appreciate the overarching philosophy to have all articles appear with the same styling. But, when I follow the "rules" and bad things happen, I must question the process involved. It's time to fix the publishing process at Code Project! I, as usual, stand ready to help. [Edited: turned on "Treat my content as plain text, not as HTML" to allow Gus' HTML tags to appear in the text] Gus Gustafson
And this report was edited badly by the publishing software. I did not number my paragraphs. I used static text This is the type of problem I am weary of.
Gus Gustafson
-
And this report was edited badly by the publishing software. I did not number my paragraphs. I used static text This is the type of problem I am weary of.
Gus Gustafson
Try disabling markdown if you still have it enabled. You can find the option under the message edit and preview area.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
Try disabling markdown if you still have it enabled. You can find the option under the message edit and preview area.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
I am unaware of any such option. Please be more specific. Recall that I'm referring to article authoring.
Gus Gustafson
-
I am unaware of any such option. Please be more specific. Recall that I'm referring to article authoring.
Gus Gustafson
Reply to or edit a message, and scroll down until you get just under the preview. There are four checkboxes, one of which is 'Use Markdown Formatting'. Uncheck that one if it's checked.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
Reply to or edit a message, and scroll down until you get just under the preview. There are four checkboxes, one of which is 'Use Markdown Formatting'. Uncheck that one if it's checked.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
Once again, I am not referring to the replying to or editing a message. Rather I am referring to difficulties when authoring an article. Your comments refer to messages. My concerns are with authoring articles.
Gus Gustafson
-
I do not know what's going on. Sean has, as usual, been a great help. But there are serious problems with the publishing process at Code Project. 1. In attempting to use a PNG within a recent article, I was thwarted by something I had no control over. Were it not for Sean, the PNG would never have appeared in the final published article. 2. When I viewed the published article, I found that an HTML end-tag was removed. The original HTML was If set true, the first row will be treated as .... In the published article it appeared as (note the missing ): If set true, the first row will be treated as .... This of course caused the word "true" and all following text to appear in RoyalBlue. 3. There appears to be no way in which to colorize objects within a
block. In my current article this requires a significant increase in the concentration needed to understand the article. What was simple became difficult because I could not color-code some pseudo-code. What concerns me is that these kinds of bugs are rampant. Furthermore, the paper that was finally published diverged significantly from my intent. It does not matter if I check "keep your fingers off my HTML". The changes are occurring somewhere within the Code Project publishing paradigm. By including the Code Project stylesheets in the of my documents, I thought that I could preview what I expected to see in the final Code Project article. But when it gets published, the results are different from what I saw in Firefox. This is unacceptable from an authoring standpoint. I put a lot of work into creating an article for Code Project. I appreciate the overarching philosophy to have all articles appear with the same styling. But, when I follow the "rules" and bad things happen, I must question the process involved. It's time to fix the publishing process at Code Project! I, as usual, stand ready to help. [Edited: turned on "Treat my content as plain text, not as HTML" to allow Gus' HTML tags to appear in the text] Gus Gustafson
Gus, You've entered a bunch of HTML tags in the content of your message and our forum system interprets HTML tags as, well, HTML (and has since we started CodeProject) unless you check "Treat my content as plain text, not as HTML". I've edited your message and ticked this box. We also added support for Markdown[^]. Your message had the "Use Markdown formatting" box ticked as well which was causing the paragraphs to be numbered. I unticked this box. Your concerns 1. I'll talk to Sean about the image issue. Did he provide you any guidance or explanation of what went wrong our end? 2. Can you please send me the original HTML you were attempting to post directly? I'll see what was happening with the HTML parser. I'm surprised an ending tag was removed. I've not seen that before. 3. We don't support coloursing code within PRE blocks. This isn't a bug, it's a style decision.
cheers Chris Maunder