Reword the recent deobfuscation changes
In most cases the word was changed to 'obfuscation' as it was about
obfuscation, not deobfuscation. In some cases like 1995/leo since the
file was (in 1995/leo) about a secret switch it was changed to
'secret.md' (and 'secret.html') but there were others like that as well.
One entry had the words 'spoiling the size rule' but this had been
changed to 'deobfuscating the size rule' which was obviously wrong.
In the latter YYYY/README.md files the judges had written after some
entries (brief summaries) '...
...We'll stop spouting spoilers now. Have fun exploring all the
entries!
but that was changed to:
...We'll stop spouting deobfuscation information now. Have fun
exploring all the entries!
which wasn't really about deobfuscation but just a brief summary of what
the entries did.
And in the most problematic case (at least for me :-), 2018/ferguson) I
had put a joke in:
... but it's the only Easter egg I won't spoil
but it was changed to 'won't deobfuscate' which not only is not what it
is but it spoilt the joke.
In some cases the word was changed back to 'SPOILER' (or similar) but in
most cases not. I believe it should be better now. There are some
caveats, however, as below.
Although make find_missing_links is okay I do not remember if this will
catch links that refer to '%%REPO_URL%%' or other pandoc tokens. This
means I might have to go back to some earlier years to verify links are
okay. That should not take that much time I hope.
It might also be that some wording can still be improved some but it is
hoped this will be discovered when checking links and looking over the
manifest (which obviously changed).
This commit is contained in:
1 parent
a379c6296a
commit
1ac055fa85
193 files changed
+531
-524
No files matched your search
@@ -767,14 +767,14 @@ over there.</p>
|
||||
then use the <a href="contact.html">How to contact the IOCCC</a> information to ask
|
||||
a private question.</p>
|
||||
<p><strong>IMPORTANT</strong>: When you ask your question (in public or as a private question)
|
||||
<strong>PLEASE</strong> try to <strong>NOT</strong> discuss detailed about your pending submission.
|
||||
<strong>PLEASE</strong> try to <strong>NOT</strong> discuss detailed information about any pending submission.
|
||||
Try to ask for question in a more generic way as this will help others
|
||||
with a similar question and this will not <strong>give away</strong> what you might be doing
|
||||
with your submission. If the <a href="judges.html">IOCCC judges</a> truly need more
|
||||
information, they will ask (either in public or suggest a private conversation).</p>
|
||||
<p>Again, <strong>please</strong> don’t hesitate to ask: Your question may be something that
|
||||
others are wondering about as well.</p>
|
||||
<p>See also [FAQ about making suggestions)(#faq0_5).</p>
|
||||
others are wondering about as well!</p>
|
||||
<p>See also <a href="#faq0_5">FAQ about making suggestions</a>.</p>
|
||||
<div id="faq0_7">
|
||||
<div id="markdown">
|
||||
<h3 id="faq-0.7---what-are-the-ioccc-best-practices-for-using-markdown">FAQ 0.7: - What are the IOCCC best practices for using markdown?</h3>
|
||||
|
||||
Reference in new issue
Block a user