Talk:Bacon cipher: Difference between revisions

 

:::: I don't mind asking for a task's requirements (or wording) to make the requirements clearer (or the definitions being used), but I've been on the receiving end of people changing (to the point of being a different task), often for the worse, to the point of the task not making any sense, and the changes made without any discussion.   I thought a purpose of encrypting (using a cipher) was to make the code hard (well, harder) to crack (understand), and using one Latin letter (both the lowercase and uppercase version of '''S''') certainly went a long way towards that goal for this task's intent.   I took a a set of characters (or glyphs) one step further (as witnessed above), which I thought were nice looking to boot.   Some Latin letters make great choices for that purpose:   Cc, Kk, Oo, Ss, Uu, Vv, Ww, and Xx come to mind.   -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 07:55, 12 September 2015 (UTC)

: I could see standardizing some aspects of the task. Perhaps requiring a specific text (either to encrypt or to hold the encrypted text or both), for example. Though I could also see it being more interesting with variation being either allowed or specified. But the font aspect is something of a problem - if you seriously wanted font support, you should first implement a Rosetta Code task which involves multiple fonts. But since there's no file upload capability, the only way to see correctness would be to render to html or wiki-markup. So that might be a dead-end. So perhaps for this task we should just standardize on using letter case in place of font? --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 19:36, 10 September 2015 (UTC)