crypto-square: Clarifying how whitespace should be handled

[smaclell]

I was a little confused by the description for how extra whitespace should be handled in the crypto-square problem. Based on the tests in the xecmascript instead of evenly spacing the extras whitespace across multiple rows, the whitespace appeared to be added to the final row.

I have updated the wording to try to better reflect how the whitespace was handled. Thank you for such an awesome project and being so open to contributions.

[rbasso]

Imperfect squares will have n empty spaces. Those spaces should be distributed evenly across the last n rows.

From my understanding, this is referring to the square after transposition.

If I'm not getting this wrong, this change will make the description incompatible with the current tests, right?

[Insti]

This is a modification rather than a clarification.
The correct thing to do would be to fix the apparently broken tests in the xecmascript track.

[petertseng]

now reading the text top to bottom, it will be misaligned - before this change it was "if man was meant to stay on the ground god would have given us roots", and now it is "if man was meant to etay on tho ground gad would huve given s rootss" - is that okay? One can argue it is a measure to obscure the plain text, in which case we should just pick a group size unrelated to the square size, such as "always 5"

You can read previous discussion about it in #190, but it does appear the https://github.com/exercism/x-common/blob/master/exercises/crypto-square/canonical-data.json file matches the version before this PR rather than after it.

[smaclell]

I am going to trust the canonical data and will instead go fix the specs in the ecmascript track. You are also correct that my description change would have misaligned the data. Thank you for responding.

[smaclell]

Thanks everyone for your feedback! @Insti, I will take your suggestion and go submit a PR to fix the bad specs in the ecmascript track. Have a great day!

[Insti]

Great. Thanks for taking the initiative to try and fix the problem you found @smaclell