[mythtv-users] UTF-8 Support in MythTV still looks messed up to me

[Michael T. Dean]

On 09/24/2008 10:01 AM, leo fischer wrote:
> I don't wish to cause offense either but:
>
> >If we knew where, it would be there. What we need/ed/ were reports of
> >where the data handling breaks so that we could inspect the code and
> >find the missing (or, in some cases, possibly redundant) conversions
>
> The poster stated that the problem is observable using XMLTV's
> tv_grab_jp script.
> 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
> http://www.gossamer-threads.com/lists/mythtv/users/246353?search_string=utf-8;#246353)
> Is it necessary to open a ticket to bring it to someone's attention? 

Well, I still don't know where to fix the code.  Finding out would
require digging through the code and a) guessing or b) trying to set up
some kind of environment in which I could reproduce the issues.  And,
for me, it's not worth the effort (as I don't observe any bugs).

> > IMHO, the proper way of dealing with it in 0.21-fixes is to live with
> >the problems/mangled text.
>
> 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.
>
> 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.
>
> The xml created by the grabber does seem to be well formed, so I'd
> think the problem is somewhere downstream. 

Yeah, it's likely an unreported/undiagnosed but in MythTV 0.21-fixes and
below.  Unless a -fixes user were to identify and fix the problem, it's
/very/ unlikely to ever be fixed.  Instead, it will most likely be fixed
in 0.22 (has most likely been fixed in trunk) as a symptom/side-effect
of the major changes introduced with the Qt4 switch.  Though, if you're
really interested in making sure 0.22 works right, you may want to set
up a development/test box and verify that trunk works and, if not, fix
it or at least report the issue.

Mike