Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Encoding special characters (ISO 639-1)

See original GitHub issue

Hello,

I use rss-parser on some feeds in the Serbian language, which has several special characters, like: Š, Č, Ć, Ž. All of these are (in rss-parser 2.10.1) replaced with \ufffd.

Is there any way encoding can be improved to cover these (latin-extended, ISO 639-1 codes) characters? Same would apply to several other languages - Slovenian, Croatian, Bosnian, etc.

I love the simplicity of use, despite the lack of async/await support 😃 but I will have to find an alternative if I can’t solve this encoding issue.

Issue Analytics

State:
Created 6 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

rbrencommented, Jan 3, 2018

You’re right, we should set the encoding based on the content-type header if available.

I will try and put this into v3, as well as an option for specifying encoding manually. In the meantime, you can always download the URL outside of rss-parser and use parseString.

0reactions

fmsfcommented, Jan 17, 2018

That’s awesome! thanks