I'm curious why HandsomeSoup has its own openUrl and fromUrl when
readDocument in HXT already exists and can use Network.HTTP?
The reason I ask is that openUrl current uses Network.HTTP's broken
String return option, which mangles non-ASCII data. I'm not sure what
readDocument does, but it seems on reading the docs to be
encoding-aware, which would be nice.
From my email.
I'm curious why HandsomeSoup has its own openUrl and fromUrl when readDocument in HXT already exists and can use Network.HTTP?
The reason I ask is that openUrl current uses Network.HTTP's broken String return option, which mangles non-ASCII data. I'm not sure what readDocument does, but it seems on reading the docs to be encoding-aware, which would be nice.