Sha256: 827ce8661b3d14546a2a0ba07eea29a068e4694fd3962bd2374acc0cf72eee5f

Contents?: true

Size: 1.66 KB

Versions: 83

Compression:

Stored size: 1.66 KB

Contents

Implement the classic method for composing secret messages called a square code.

Given an English text, output the encoded version of that text.

First, the input is normalized: the spaces and punctuation are removed
from the English text and the message is downcased.

Then, the normalized characters are broken into rows.  These rows can be
regarded as forming a rectangle when printed with intervening newlines.

For example, the sentence

> If man was meant to stay on the ground, god would have given us roots.

is normalized to:

> ifmanwasmeanttostayonthegroundgodwouldhavegivenusroots

The plaintext should be organized in to a rectangle.  The size of the
rectangle (`r x c`) should be decided by the length of the message,
such that `c >= r` and `c - r <= 1`, where `c` is the number of columns
and `r` is the number of rows.

Our normalized text is 54 characters long, dictating a rectangle with
`c = 8` and `r = 7`:

```plain
ifmanwas
meanttos
tayonthe
groundgo
dwouldha
vegivenu
sroots
```

The coded message is obtained by reading down the columns going left to
right.

The message above is coded as:

```plain
imtgdvsfearwermayoogoanouuiontnnlvtwttddesaohghnsseoau
```

Output the encoded text in chunks.  Phrases that fill perfect squares
`(r X r)` should be output in `r`-length chunks separated by spaces.
Imperfect squares will have `n` empty spaces.  Those spaces should be distributed evenly across the last `n` rows.

```plain
imtgdvs fearwer mayoogo anouuio ntnnlvt wttddes aohghn sseoau
```

Notice that were we to stack these, we could visually decode the
cyphertext back in to the original message:

```plain
imtgdvs
fearwer
mayoogo
anouuio
ntnnlvt
wttddes
aohghn
sseoau
```

Version data entries

83 entries across 83 versions & 1 rubygems

Version Path
trackler-2.2.1.39 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.38 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.37 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.36 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.35 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.34 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.33 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.32 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.31 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.30 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.29 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.28 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.27 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.26 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.25 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.24 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.23 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.22 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.21 problem-specifications/exercises/crypto-square/description.md
trackler-2.2.1.20 problem-specifications/exercises/crypto-square/description.md