On Abot2, the content from the response is obtained before resolving charset encoding. As a result, the content presents issues with special characters on none UTF8 charsets. For instance, getting content with charset windows-1252. At the meantime, I'm overwriting WebContentExtractor with the Abot implementation.
The trick in the classic Abot implementation was passing the encoding (e) to the StreamReader. This is not currently done in the Abot2 implementation:
using (StreamReader sr = new StreamReader(memoryStream, e))
On Abot2, the content from the response is obtained before resolving charset encoding. As a result, the content presents issues with special characters on none UTF8 charsets. For instance, getting content with charset windows-1252. At the meantime, I'm overwriting WebContentExtractor with the Abot implementation.
The trick in the classic Abot implementation was passing the encoding (e) to the StreamReader. This is not currently done in the Abot2 implementation:
using (StreamReader sr = new StreamReader(memoryStream, e))