Pangram README claims input will only have ASCII

[shaleh]

The README says:

The alphabet used consists of ASCII letters `a` to `z`, inclusive, and is case
insensitive. Input will not contain non-ASCII symbols.

There are German characters in one test which causes failures if not ignored or counted. But even then tests fail if code does not handle characters outside of ASCII. Specifically, Russian.

--- FAIL: TestPangram (0.00s)
pangram_test.go:37: Pangram test [Широкая электрификация южных губерний даст мощный толчок подъёму сельского хозяйства.], expected [false], actual [true]
pangram_test.go:39: [Широкая электрификация южных губерний даст мощный толчок подъёму сельского хозяйства.] should not be a pangram because : Panagram in alphabet other than ASCII

I am OK with having to check if a rune is ASCII or not. But the README explicitly says not to worry about it. Or is 'symbols' here meant to mean things other than letters like braces, emoji, and the like? Either way the README is at best not clear and at worst wrong.

[tleen]

Thanks @shaleh, you are exactly right. That line does not make a lot of sense when you look at the test input. Should be fixed in #802.

Thanks for letting us know!

[tleen]

Going to keep the README but remove the non-ASCII compatible test entries.

[shaleh]

@tleen, I have not made it through all of the exercises yet. It would be good to have some of them show the capabilities of modern languages to in handling global inputs. I did not mind the Russian or German it was a good demonstration of not assuming English text. How many projects have we seen with the changelog entry "oh yeah, this ought to work outside of the US"?

[tleen]

I agree, especially considering how go really works the rune concept over characters as they are known in any other language. It is one of the pain points and great strengths of the language.

The way we addressed this specific issue is more or less to keep it consistent with the way this exercise is implemented across all all the Exercism tracks. It was decided that ASCII-only was the way to go here. We were an outlier. It is still a fairly early exercise in most tracks so that makes sense not to bring up character set issues just yet.

Don't worry there are definitely exercises coming up with non-ASCII stuff. Runetime!

[shaleh]

Make sense. Sounds good.