Just for benefit of the forum. Solution was found and solution already in latest public A1 Sitemap Generator version.
Here is what happens when A1 Sitemap Generator tries to determine charset / encoding in a document (which is vital when interpreting the content returned by server)
step 1)
A1SG checks for charset in (if any) content-type HTTP header
step 2)
A1SG checks if content has a UTF leading BOM
step 3)
A1SG checks mimetype is e.g. text/html.
If text/html the default charset becomes iso-8859-1
UTF-8 is selected as default for anything XML
step 4)
The final step for A1 Sitemap Generator in determining
what character system is used if above gives no definitive
answer (notice that step 3 is more of a fallback)
A1 Sitemap Generator looked for
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
and close variants. (i.e. reads the charset value to determine how content is
parsed.)
However, the website in question used a HTML5 instruction:
<meta charset="utf-8">
and A1 Sitemap Generator therefore missed it.
But this issue has been fixed some days ago
