Talk:Base64 encode data: Difference between revisions

→‎task requirements: added more comments on the task requirements. -- ~~~~
(→‎task requirements: comment on the tast requirements, showing the output. -- ~~~~)
(→‎task requirements: added more comments on the task requirements. -- ~~~~)
Line 10:
:But these would require a change on the task requirements, I guess I didn't thought that well, before.. creating this draft. [[User:Rainb|Rainb]] ([[User talk:Rainb|talk]]) 04:37, 28 August 2013 (UTC)
 
:: That's why the task is first made a draft. --- to iron out the requirements and make the task clearer.   Currently, the requirement is to use/convert the   ''favicon.ico''   (file),   but not to show the result.   How is anyone to know the currect result ''is'' if nobody comparecompares/verifies outputsthe OUTPUTs? &nbsp:; I would like to see if the programming examples can correctly handle the various padding variations   ('''=''' and '''==''' and no equal signs).   Unfortunately, the file to be used doesn't have any   '''='''   padding in the output.   So far, nobody has shown the 4,850 bytes of output ... until now. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 05:12, 28 August 2013 (UTC)
'''output''' from the REXX example using an eighty-byte wide screen:
<pre>