Final fixes for IOCCC guidelines/rules #247
Conversation
Fixed broken links. Restored text that was accidentally removed during the emergency recovery of guidelines some days back. Moved some text that was in the wrong place. The formatting of the markdown files was changed for shorter lines (for those viewing the markdown in a viewer rather than a web browser). Added a <div id> to 2024/index.html so the guidelines (or maybe rules) could link to the important note from the judges in IOCCC28. Restore rewording of rule 2b done by @SirWumpus.
The text was actually already there (as I thought since I had added it some days back).
| </p> | ||
|
|
||
| See the [Guidelines for Rule 1 - C program](guidelines.html#guideline1-c). | ||
| See the [Guidelines for Rule 1 - C |
There was a problem hiding this comment.
Splitting Markdown links across lines causes Markdown viewer formatting problems. HTML doesn't have an issue.
There was a problem hiding this comment.
Splitting Markdown links across lines causes Markdown viewer formatting problems. HTML doesn't have an issue.
That's your viewer. I do not have that problem. But that's another matter entirely.
There was a problem hiding this comment.
Splitting Markdown links across lines causes Markdown viewer formatting problems. HTML doesn't have an issue.
That's your viewer. I do not have that problem. But that's another matter entirely.
... besides one does not click a link in a markdown file so the formatting problem is immaterial. And if you say that a markdown viewer allows for clicking links it would go to html files.
There was a problem hiding this comment.
Splitting Markdown links across lines causes Markdown viewer formatting problems. HTML doesn't have an issue.
That's your viewer. I do not have that problem. But that's another matter entirely.
... besides one does not click a link in a markdown file so the formatting problem is immaterial. And if you say that a markdown viewer allows for clicking links it would go to html files.
And beyond that some of the lines were really long and that can cause problems as I have noted before.
There was a problem hiding this comment.
Splitting Markdown links across lines causes Markdown viewer formatting problems. HTML doesn't have an issue.
That's your viewer. I do not have that problem. But that's another matter entirely.
... besides one does not click a link in a markdown file so the formatting problem is immaterial. And if you say that a markdown viewer allows for clicking links it would go to html files.
And beyond that some of the lines were really long and that can cause problems as I have noted before.
However see my comment here.
|
|
||
| **NOTE**: `iocccsize` does **NOT** calculate the filename length. | ||
| Check your source code using the latest official IOCCC size tool, | ||
| `iocccsize(1)`. The value printed **MUST NOT** exceed **2503**. |
There was a problem hiding this comment.
Works for me.
Well that's good. Sorry the other one does not. I have never seen that with a viewer. But then I don't have a viewer that is specifically for markdown viewing. Anyway it doesn't affect generation of links. I don't know why though that I did it since I have gone out of my way to prevent it with the FAQ links.
There was a problem hiding this comment.
Works for me.
Well that's good. Sorry the other one does not. I have never seen that with a viewer. But then I don't have a viewer that is specifically for markdown viewing. Anyway it doesn't affect generation of links. I don't know why though that I did it since I have gone out of my way to prevent it with the FAQ links.
Actually I do know why I did it. It's because the FAQ is just a list at the top. Here it's just too long lines that don't always wrap well. It's unfortunate that some viewers can't parse multi-line markdown links.
There was a problem hiding this comment.
Works for me.
Well that's good. Sorry the other one does not. I have never seen that with a viewer. But then I don't have a viewer that is specifically for markdown viewing. Anyway it doesn't affect generation of links. I don't know why though that I did it since I have gone out of my way to prevent it with the FAQ links.
Actually I do know why I did it. It's because the FAQ is just a list at the top. Here it's just too long lines that don't always wrap well. It's unfortunate that some viewers can't parse multi-line markdown links.
Even so if it is enough of a problem I hope your editor allows you to do it and then go ahead. It's unfortunate for you (and maybe others) and unfortunate for me (and maybe others) but I cannot deal with it now. I have other things I must do and it's too close to the time of the contest entering pending state.
Curious: what text was accidentally removed? Not asking for a diff, just a general description of what it was we out of curiosity. |
Well maybe that's not quite worded right. Text was split into two locations. It ended up with '...:' followed by (in next paragraph) something completely unrelated. The text was in the wrong place so I had to move it. And as I said also some links were broken. |
lcn2
left a comment
lcn2
left a comment
There was a problem hiding this comment.
Let's see how this looks (and by this we mean the HTML as viewed by browsers via the website) and see if the overall experience (again view a web browser viewing HTML) works well.
Thanks 🙏 @xexyl and @SirWumpus for your collaboration on this matter.
It seemed okay at a quick look. Given that mostly it was formatting with a few textual changes (mostly moving text) I'd guess it's fine. Like I said I forgot to move the description of the file to the top but maybe you wish to do that - or not. I have other things to do now.
Welcome on my behalf. I didn't look for typos (meaning I did not really read it) although when moving text about I did see a few that were fixed. Hopefully it's in good shape now - or at least in good enough shape for tomorrow (that's when I'll probably read it - or maybe on Thursday). |
3 participants
Fixed broken links.
Restored text that was accidentally removed during the emergency recovery of guidelines some days back.
Moved some text that was in the wrong place.
The formatting of the markdown files was changed for shorter lines (for those viewing the markdown in a viewer rather than a web browser).
Added a
Restore rewording of rule 2b done by @SirWumpus.