Currently, FeedMD does not support reading feeds in various non-Unicode encodings.
If the server header and/or the feed header declares some regional single-byte encoding, FeedMD returns an error: "System does not support 'xxx' encoding. "
Yes, UTF-8 encoding is already widespread, but a number of regional sites provide their feeds in regional single-byte encodings.
It would be great if FeedMD could read feeds in different encodings.
Since FeedMD's internal encoding is UTF-8 and items from different feeds can be written to a single file, it will probably be necessary to recode all feeds to UTF-8.
That is, if FeedMD detects something other than UTF-8, it will have to convert the content from the original encoding to UTF-8 before writing the result to the file.
Of course, this is not an bug report, but a feature request.
Currently, FeedMD does not support reading feeds in various non-Unicode encodings.
If the server header and/or the feed header declares some regional single-byte encoding, FeedMD returns an error: "System does not support 'xxx' encoding. "
Yes, UTF-8 encoding is already widespread, but a number of regional sites provide their feeds in regional single-byte encodings.
It would be great if FeedMD could read feeds in different encodings.
Since FeedMD's internal encoding is UTF-8 and items from different feeds can be written to a single file, it will probably be necessary to recode all feeds to UTF-8.
That is, if FeedMD detects something other than UTF-8, it will have to convert the content from the original encoding to UTF-8 before writing the result to the file.
Of course, this is not an bug report, but a feature request.