<div dir="ltr">I don't wish to cause offense either but:<br><br>>If we knew where, it would be there. What we need/ed/ were reports of<br>>where the data handling breaks so that we could inspect the code and<br>
>find the missing (or, in some cases, possibly redundant) conversions<br><br>The poster stated that the problem is observable using XMLTV's tv_grab_jp script.<br>The same information is also on the linked wiki page. I've seen the problem mentioned several times, but I haven't seen any useful responses. (like this almost 2 years ago, completely ignored <a href="http://www.gossamer-threads.com/lists/mythtv/users/246353?search_string=utf-8;#246353">http://www.gossamer-threads.com/lists/mythtv/users/246353?search_string=utf-8;#246353</a>)<br>
Is it necessary to open a ticket to bring it to someone's attention? <br><br>> IMHO, the proper way of dealing with it in 0.21-fixes is to live with<br>>the problems/mangled text.<br><br>As someone who has tried this as well, this is a total non-solution. The text that's displayed in the guide isn't just slightly damaged, it's mangled. junk. The whole schedule is the equivalent of $%!@%^T!TG$!#F!$!% If you would find your system with no guide data, I'd be surprised.<br>
<br>Now, that being said, I'd really like to have my system working properly as well, and am capable of reviewing the code, and even doing some debugging if someone were to be helpful enough to point me in the right direction.<br>
<br>The xml created by the grabber does seem to be well formed, so I'd think the problem is somewhere downstream. <br></div>