Talk:Bacon cipher: Difference between revisions

From Rosetta Code
Content added Content deleted
(added a comment.)
No edit summary
Line 4: Line 4:


: If you're referring to the REXX entry, I chose to use the decimal digits   '''1'''s   and   '''0'''s   (ones and zeroes)   instead of   '''A'''s   and   '''B'''s.   It may look like binary, but it tain't.   I had thought of using what the Rosetta Code task's example uses, but I went with another set of characters, just to show how faux "binary" would look like.   -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 19:23, 10 September 2015 (UTC)
: If you're referring to the REXX entry, I chose to use the decimal digits   '''1'''s   and   '''0'''s   (ones and zeroes)   instead of   '''A'''s   and   '''B'''s.   It may look like binary, but it tain't.   I had thought of using what the Rosetta Code task's example uses, but I went with another set of characters, just to show how faux "binary" would look like.   -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 19:23, 10 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)

Revision as of 19:36, 10 September 2015

Focus?

Hi is this task good to leave draft status or does it need more focus - thinking of the intermediate form which is historically to hide the secret message in font changes, which would shift the tasks focus away from the cipher side and would be hard to show output on RC and hard to get input in differing fonts for 'round-tripping' tests. Some have displayed the binary only; others have used capitalisation changes on either random text or some story.
--Paddy3118 (talk) 17:28, 10 September 2015 (UTC)

If you're referring to the REXX entry, I chose to use the decimal digits   1s   and   0s   (ones and zeroes)   instead of   As   and   Bs.   It may look like binary, but it tain't.   I had thought of using what the Rosetta Code task's example uses, but I went with another set of characters, just to show how faux "binary" would look like.   -- Gerard Schildberger (talk) 19:23, 10 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? --Rdm (talk) 19:36, 10 September 2015 (UTC)