Format fix 2012/hamano/README.md
This commit is contained in:
1 parent
3753579f6b
commit
21428fa40b
1 file changed
+15
-13
+15
-13
@@ -21,7 +21,11 @@ make
|
|||||||
./hamano < README.md > hint.pdf
|
./hamano < README.md > hint.pdf
|
||||||
```
|
```
|
||||||
|
|
||||||
You can read output.pdf with PDF reader acroread hint.pdf or evince hint.pdf.
|
You can read `hint.pdf` with a PDF reader like `acroread hint.pdf` or `evince
|
||||||
|
hint.pdf`. With macOS you can do `open hint.pdf` which by default will open
|
||||||
|
`Preview.app`. You may of course use your pdf view to open the file directly
|
||||||
|
instead.
|
||||||
|
|
||||||
|
|
||||||
To deobfuscate:
|
To deobfuscate:
|
||||||
|
|
||||||
@@ -39,7 +43,7 @@ cc -Wno-implicit-function-declaration -xc hello.pdf -o hello2
|
|||||||
./hello3
|
./hello3
|
||||||
```
|
```
|
||||||
|
|
||||||
## Judges' remarks
|
## Judges' remarks:
|
||||||
|
|
||||||
This entry treads into a new territory for IOCCC - generating PDF files.
|
This entry treads into a new territory for IOCCC - generating PDF files.
|
||||||
|
|
||||||
@@ -63,22 +67,20 @@ So what do those flags really mean?
|
|||||||
|
|
||||||
The [Dancing men algorithm][1] might be useful.
|
The [Dancing men algorithm][1] might be useful.
|
||||||
|
|
||||||
Don't forget to take a look at the generated PDF, perhaps you might even want
|
Don't forget to take a look at the generated PDF. Perhaps you might even want
|
||||||
to compile the output with a C compiler. When you run it, what does it
|
to compile the output with a C compiler. When you run it, what does it
|
||||||
output?
|
output?
|
||||||
|
|
||||||
## Author's remarks
|
## Author's remarks:
|
||||||
|
|
||||||
This program obfuscate text file into PDF file with Dancing men
|
This program obfuscate text file into PDF file with [Dancing men
|
||||||
algorithm.
|
algorithm](http://en.wikipedia.org/wiki/The_Adventure_of_the_Dancing_Men).
|
||||||
|
|
||||||
<http://en.wikipedia.org/wiki/The_Adventure_of_the_Dancing_Men>
|
Probably, the output PDF file is compliant with PDF 1.3 and it's also
|
||||||
|
|
||||||
Probably, the output PDF file is compliant with PDF 1.3. And also
|
|
||||||
available to compile as C code.
|
available to compile as C code.
|
||||||
|
|
||||||
I've been tested with GCC 4.7 and Clang 3.0 on Linux, and following
|
I've tested it with GCC 4.7 and Clang 3.0 with Linux, and the following
|
||||||
PDF Reader:
|
PDF Readers:
|
||||||
|
|
||||||
* Adobe Acrobat Reader
|
* Adobe Acrobat Reader
|
||||||
* Evince
|
* Evince
|
||||||
@@ -87,8 +89,8 @@ PDF Reader:
|
|||||||
|
|
||||||
### Obfuscations
|
### Obfuscations
|
||||||
|
|
||||||
This program is obfuscated by using classical methods.
|
This program is obfuscated by using classical methods. But can you find the
|
||||||
But can you find out the embedded font from fragmented glyph?
|
embedded font in the fragmented glyph?
|
||||||
|
|
||||||
## Copyright and CC BY-SA 4.0 License:
|
## Copyright and CC BY-SA 4.0 License:
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user