>I believe the library shouldn't be arbitrarily munging the content of data it is processing, it should be up to the caller to do EOL
>translation if necessary based on its knowledge of the platform and usage of the data.

That's why I brought the unicode example. We are already munging the data as we decode UTF8 by default. If we would return
texts as raw data in the high level API the consumer of the API always need to do these extra steps. I think the high level API
in the src/openpgp.js file (which is a thin layer anyway) should return normalized EOL to \n and decoded UTF8 by default 
and be "simple" and consistent in this respect.

This reduces complexity for the average use case and the good thing is that we have the Key and Message class 
for the more advanced use cases.
So instead of calling directly openpgp.decryptMessage (and get normalized EOF and UCS-2):
```
function decryptMessage(privateKey, message) {
  message = message.decrypt(privateKey);
  return message.getText();
}
```
You can simply do:
```
message = message.decrypt(privateKey);
message.getLiteralData()
```
And get the raw data.