More bugs from the AAC
-
The Article Approval Community has made a real mess out of my article MFC PowerShells Easily: A JSON API and Random Numbers[^]. They made the images with PowerShell code with proper color syntax vanish, and also made the only code currently visible, full of span tags. The tag for PowerShell language is buggy, thus cannot be used: it does not add color syntax properly, and worse change the code by insertion of many hyperlinks! Clearly, inside pre tags, except for color syntax, nothing should be changed, let alone with insertions of hyperlinks. So, the article is published with the images missing and many span tags in the only visible code that uses the pre tags. Please, publish my original article exactly as I posted/submitted and delete the article as it is currently published. Also, don't make it a tip; read the articles after mine in the C++ page and you'll see they follow the pattern as mine. Thanks.
-
The Article Approval Community has made a real mess out of my article MFC PowerShells Easily: A JSON API and Random Numbers[^]. They made the images with PowerShell code with proper color syntax vanish, and also made the only code currently visible, full of span tags. The tag for PowerShell language is buggy, thus cannot be used: it does not add color syntax properly, and worse change the code by insertion of many hyperlinks! Clearly, inside pre tags, except for color syntax, nothing should be changed, let alone with insertions of hyperlinks. So, the article is published with the images missing and many span tags in the only visible code that uses the pre tags. Please, publish my original article exactly as I posted/submitted and delete the article as it is currently published. Also, don't make it a tip; read the articles after mine in the C++ page and you'll see they follow the pattern as mine. Thanks.
I would republish your first version, but I think the ideal would be to use the images you included so that the code looks correct to you. I have made the changes, please let me know if that looks OK.
Thanks, Sean Ewington CodeProject
-
I would republish your first version, but I think the ideal would be to use the images you included so that the code looks correct to you. I have made the changes, please let me know if that looks OK.
Thanks, Sean Ewington CodeProject
First version? There's no second version. Please, don't be confused: the writing made with don't publish keep it private check-button set are not versions to be published. The only version to be published, is the the one I submitted with the publish check-button set, and this one got the images in place of the buggy pre tags for PowerShell. Please, publish the article I submitted to be published: it contains no errors. All the errors came from AAC intervention doing what they don't understand. Thanks.
-
I would republish your first version, but I think the ideal would be to use the images you included so that the code looks correct to you. I have made the changes, please let me know if that looks OK.
Thanks, Sean Ewington CodeProject
-
Is it not this? MFC PowerShells Easily: A JSON API and Random Numbers[^]
Thanks, Sean Ewington CodeProject
-
Is it not this? MFC PowerShells Easily: A JSON API and Random Numbers[^]
Thanks, Sean Ewington CodeProject
-
Yes, it is correct now; many thanks. By the way, my article MFC PowerShells Easily: Using RunAsync and CSS3 Gradients[^] was transformed in tip/trick by someone. Would you, please, transform it back into an article? Many thanks once more.
-
-
The Article Approval Community has made a real mess out of my article MFC PowerShells Easily: A JSON API and Random Numbers[^]. They made the images with PowerShell code with proper color syntax vanish, and also made the only code currently visible, full of span tags. The tag for PowerShell language is buggy, thus cannot be used: it does not add color syntax properly, and worse change the code by insertion of many hyperlinks! Clearly, inside pre tags, except for color syntax, nothing should be changed, let alone with insertions of hyperlinks. So, the article is published with the images missing and many span tags in the only visible code that uses the pre tags. Please, publish my original article exactly as I posted/submitted and delete the article as it is currently published. Also, don't make it a tip; read the articles after mine in the C++ page and you'll see they follow the pattern as mine. Thanks.
For sure the 'Random Numbers' is NOT an article. It also has a lot of design problems... Your other article about 'CSS3 Gradients' is also a border-case. Please read some articles and also read writing guidelines here:http://www.codeproject.com/info/submit.aspx[^]. It also seems to me, you do not understand the nature of community approval here...All who participate in moderation doing it voluntary in spare time. More of that all of them are human, and make mistakes from time-to-time...So be patient and consider that no-one on-purpose ruin your work... (And by the way, if you look into the revision history of your work, you can see that no-one removed your images/code but it some magic work of the editor).
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
For sure the 'Random Numbers' is NOT an article. It also has a lot of design problems... Your other article about 'CSS3 Gradients' is also a border-case. Please read some articles and also read writing guidelines here:http://www.codeproject.com/info/submit.aspx[^]. It also seems to me, you do not understand the nature of community approval here...All who participate in moderation doing it voluntary in spare time. More of that all of them are human, and make mistakes from time-to-time...So be patient and consider that no-one on-purpose ruin your work... (And by the way, if you look into the revision history of your work, you can see that no-one removed your images/code but it some magic work of the editor).
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
For sure the article is an article(!), which means you don't know what you're writing about. You should read some posts that are been accepted as an article, telling that complex numbers have 2 types! Complex number have no 2 types! A complex number has 2 very common representations (and if you are creative enough, you can add a representation of your own). Moreover, this post accepted as an article, is just bloating the post with trivialities like 2+2=4, but 1+3=4 too! This is not an article! Maybe a technical post for naive academic purposes. I do understand the the nature of community approval here: it's voluntary (and looking for high status, right?), which means that if you don't like it, don't do it, and mainly, don't complain doing it. Right? By the way, if you cared to see the article posted by the AAC (Article Approval Community) you'd had seen an article full of problems created by them, not by me (I previewed my article, and it was OK). And with no images! And with a formatted code full of extraneous span tags! Once more, you don't understand what you're writing about. Also, if they just checked what they posted, they'd have seen the problems, but for sure, they didn't. By the way, it's the 2nd post you did against me; what's your problem? Don't you have something else (that you understand) to write about? And don't come back to tell about the voluntary work you (and others) do. I'm not interested, as much as I'm not interested in your opinion about article/tip classification. Thanks for reading. :) ADDED: by the way, I'd have down voted your post, but it's impossible. You all do rules to protect all of you right?
