@elextr I'm not 100% sure but I can't see how an encoding outside our list can end up here, it's not like we detect it with a regex. So I don't think it's a problem, and if there is one indeed it's a separate issue and this still fixes the problem at hand and doesn't introduce a new one. So, feel free to report a separate bug if needed.