|
Yes - the comment needs a word-break:break-work CSS rule to allow it to break in the middle of a "word".
word-break - CSS: Cascading Style Sheets | MDN[^]
I've edited the comment to wrap the massive lines in <pre> tags, so it should look better now.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks for the heads-up Richard, I wanted to edit it but decided to check first.
|
|
|
|
|
Did you really write this article?


|
|
|
|
|
It might be a good idea to ask for confirmation on the other side, before activelly listing "co-authors"
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
modified yesterday.
|
|
|
|
|
Was that article under review / moderation? We shouldn't be listed until we've confirmed we're authors.
cheers
Chris Maunder
|
|
|
|
|
In moderation, and flagged as spam. I think both article and perpetrator have now been removed.
|
|
|
|
|
OK, that makes sense.
But clearly we should make it clearer which authors are confirmed and which are not
cheers
Chris Maunder
|
|
|
|
|
In the user's messages list:

On the message itself:

The message in question[^].
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Just wondering if there should be a minimum required repo points before you can write an article.
Could limit the spamming.
|
|
|
|
|
Not sure that would work: you can't post anything until you have sufficient reputation, which you gain by posting things and having them up-voted.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Is there a markdown encoding for Sub/Super scripts? The html tags <sub> and <sup> work fine, but I'm sure I saw somewhere was using ^1^ for 1. Even if there's not something like that available, can a note be added to the Markdown tips on sub/super script, for the next time I can't remember them?
"A little song, a little dance, a little seltzer down your pants"
Chuckles the clown
|
|
|
|
|
|
Can you send me a link to a question that's been badly edited?
cheers
Chris Maunder
|
|
|
|
|
|
|
How do I change the color of messageboxes in my win32 application?[^]
25th October, edited 2 minutes ago:
- Removed a hyphen from "any-one";
- Changed "win32" to "Win32";
- Changed "c++" to "C++";
- Changed "googled" to "Googled";
I appreciate that some questions have egregious formatting or language problems and can benefit from being tidied up. But dragging old questions back up the list just to make minor edits like this, which don't in any way aid the readability of the question, seems pointless.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Maybe a question shouldn't be bumped after editing unless done by the original author, or something like that.
|
|
|
|
|
But all this editing is totally pointless. The questions are all clear enough to be investigated so none of the changes make any useful difference.
|
|
|
|
|
I might be wrong or I might have complained about the "revision" not being available because of faulty browsing (I have never updated FF on my current box (2018 easily). Ever!) but doesn't it occur to anyone else that the report should be centered on the "revisor" and not the post itself?
Isn't your issue with the editor? Tell him to lay off then. Surely the moderators forum would be the space in which to conduct the voir dire and from there you could prosecute the offender most easily.
So when is my trial date? 
|
|
|
|
|
RedDk wrote: Isn't your issue with the editor? Yes, but since the person in question is a staff member, it needs a decision at CodeProject management level.
|
|
|
|
|
.. ah, yes! She is isn't she?. From far off though that satchel looks like a cigar so you can appreciate the confusion I was still experiencing even while posting this rejoinder. 
|
|
|
|
|
A lot of times (and in specific scenarios), I delete rather than edit, to avoid this bothersome scenario. As Quick Answers works now, minor edits cannot be applied like this, so you will no longer see minor edits like this.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Maybe could be an idea to focus the CP-Editors to the publications and leave the Q&A to us users?
I can imagine there are enough "wrong format" flags to be more or less continously busy.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
Yes, I saw that the other day and was about to dig in but it looks like a caching issue that's resolved.
Thanks for letting me know.
cheers
Chris Maunder
|
|
|
|