about summary refs log tree commit diff
path: root/daily/285easy/problem1.html
diff options
context:
space:
mode:
authorRaphael McSinyx <vn.mcsinyx@gmail.com>2016-10-08 09:56:43 +0700
committerRaphael McSinyx <vn.mcsinyx@gmail.com>2016-10-08 09:56:43 +0700
commit2a7bc10f6c011d19fb3b0e73068f7e1a9c30ace0 (patch)
tree95190a32ec1c7098494849eea5a5ba6b53289585 /daily/285easy/problem1.html
parent207cc2ae9893b0cdecd20119b9ede37f73cd4a1e (diff)
downloadcp-2a7bc10f6c011d19fb3b0e73068f7e1a9c30ace0.tar.gz
Initial commit
Diffstat (limited to 'daily/285easy/problem1.html')
-rw-r--r--daily/285easy/problem1.html61
1 files changed, 61 insertions, 0 deletions
diff --git a/daily/285easy/problem1.html b/daily/285easy/problem1.html
new file mode 100644
index 0000000..bf843e7
--- /dev/null
+++ b/daily/285easy/problem1.html
@@ -0,0 +1,61 @@
+<p>You are trapped at uninhabited island only with your laptop. Still you don't want your significant other to worry about you, so you are going to send a message in a bottle with your picture or at least a couple of words from you (sure, you could just write down the words, but that would be less fun). You're going to use uuencoding for that.</p>
+<p>Uuencoding is a form of binary-to-text encoding, which uses only symbols from 32-95 diapason, which means all symbols used in the encoding are printable.</p>
+<h1 id="description-of-encoding">Description of encoding</h1>
+<p>A uuencoded file starts with a header line of the form:</p>
+<pre><code>begin &lt;mode&gt; &lt;file&gt;&lt;newline&gt;</code></pre>
+<p><mode> is the file's Unix file permissions as three octal digits (e.g. 644, 744). For Windows 644 is always used.</p>
+<p><file> is the file name to be used when recreating the binary data.</p>
+<p><newline> signifies a newline character, used to terminate each line.</p>
+<p>Each data line uses the format:</p>
+<pre><code>&lt;length character&gt;&lt;formatted characters&gt;&lt;newline&gt;</code></pre>
+<p><length character> is a character indicating the number of data bytes which have been encoded on that line. This is an ASCII character determined by adding 32 to the actual byte count, with the sole exception of a grave accent &quot;`&quot; (ASCII code 96) signifying zero bytes. All data lines except the last (if the data was not divisible by 45), have 45 bytes of encoded data (60 characters after encoding). Therefore, the vast majority of length values is 'M', (32 + 45 = ASCII code 77 or &quot;M&quot;).</p>
+<p><formatted characters> are encoded characters.</p>
+<p>The mechanism of uuencoding repeats the following for every 3 bytes (if there are less than 3 bytes left, trailing 0 are added):</p>
+<ol style="list-style-type: decimal">
+<li><p>Start with 3 bytes from the source, 24 bits in total.</p></li>
+<li><p>Split into 4 6-bit groupings, each representing a value in the range 0 to 63: bits (00-05), (06-11), (12-17) and (18-23).</p></li>
+<li><p>Add 32 to each of the values. With the addition of 32 this means that the possible results can be between 32 (&quot; &quot; space) and 95 (&quot;_&quot; underline). 96 (&quot;`&quot; grave accent) as the &quot;special character&quot; is a logical extension of this range.</p></li>
+<li><p>Output the ASCII equivalent of these numbers.</p></li>
+</ol>
+<p>For example, we want to encode a word &quot;Cat&quot;. ASCII values for C,a,t are 67,97,116, or <code>010000110110000101110100</code> in binary. After dividing into four groups, we get 010000 110110 000101 110100, which is 16,54,5,52 in decimal. Adding 32 to this values and encoding back in ASCII, the final result is <code>0V%T</code>.</p>
+<p>The file ends with two lines:</p>
+<pre><code>`&lt;newline&gt;
+end&lt;newline&gt;</code></pre>
+<h1 id="formal-inputs-outputs">Formal Inputs &amp; Outputs</h1>
+<h2 id="input">Input</h2>
+<p>a byte array or string.</p>
+<h2 id="output">Output</h2>
+<p>a string containing uuencoded input.</p>
+<h1 id="examples">Examples</h1>
+<p>Input: Cat</p>
+<p>Output:</p>
+<pre><code>begin 644 cat.txt
+#0V%T
+`
+end</code></pre>
+<p>Input: I feel very strongly about you doing duty. Would you give me a little more documentation about your reading in French? I am glad you are happy — but I never believe much in happiness. I never believe in misery either. Those are things you see on the stage or the screen or the printed pages, they never really happen to you in life.</p>
+<p>Output:</p>
+<pre><code>begin 644 file.txt
+M22!F965L(&#39;9E&lt;GD@&lt;W1R;VYG;&#39;D@86)O=70@&gt;6]U(&amp;1O:6YG(&amp;1U=&#39;DN(%=O
+M=6QD(&#39;EO=2!G:79E(&amp;UE(&amp;$@;&amp;ET=&amp;QE(&amp;UO&lt;F4@9&amp;]C=6UE;G1A=&amp;EO;B!A
+M8F]U=&quot;!Y;W5R(&#39;)E861I;F&lt;@:6X@1G)E;F-H/R!)(&amp;%M(&amp;=L860@&gt;6]U(&amp;%R
+M92!H87!P&gt;2#B@)0@8G5T($D@;F5V97(@8F5L:65V92!M=6-H(&amp;EN(&amp;AA&lt;&#39;!I
+M;F5S&lt;RX@22!N979E&lt;B!B96QI979E(&amp;EN(&amp;UI&lt;V5R&gt;2!E:71H97(N(%1H;W-E
+M(&amp;%R92!T:&amp;EN9W,@&gt;6]U(&#39;-E92!O;B!T:&amp;4@&lt;W1A9V4@;W(@=&amp;AE(&#39;-C&lt;F5E
+M;B!O&lt;B!T:&amp;4@&lt;&#39;)I;G1E9&quot;!P86=E&lt;RP@=&amp;AE&gt;2!N979E&lt;B!R96%L;&#39;D@:&amp;%P
+3&lt;&amp;5N(&#39;1O(&#39;EO=2!I;B!L:69E+C P
+`
+end</code></pre>
+<h1 id="bonuses">Bonuses</h1>
+<h2 id="bonus-1">Bonus 1</h2>
+<p>Write uudecoder, which decodes uuencoded input back to a byte array or string</p>
+<h2 id="bonus-2">Bonus 2</h2>
+<p>Write encoder for files as well.</p>
+<h2 id="bonus-3">Bonus 3</h2>
+<p>Make encoding parallel.</p>
+<h1 id="further-reading">Further Reading</h1>
+<p><a href="https://en.wikipedia.org/wiki/Binary-to-text_encoding">Binary-to-text encoding</a> on Wikipedia.</p>
+<h1 id="finally">Finally</h1>
+<p>This challenge is posted by /u/EvgeniyZh</p>
+<p>Also have a good challenge idea?</p>
+<p>Consider submitting it to /r/dailyprogrammer_ideas</p>