If it were easy to see what's a number and whats a string, type confusions a la YAML's fun wouldn't exist: Is "no" a string, a country, a boolean? Is 0 a boolean, a number, or char[48]?

This is specifically an area that "text" is quite bad and is the source of much woe. Your provided example would be parsed by most parsers today as a string, since it mixes spaces (non-numeric) and surrounds it with quotes.

In fact, given well-defined binary, it is rather simpler to turn it into "text" than the reverse. It seems like you've forgotten that "0x32 0x20 0x37 0x20 0x2A..." is literally what is in that file you would view. Plain text is, after all, just one example of a binary format.