[mythtv-users] Issue with accents in titles and descriptions: Myth or Schedules Direct?

[Michael T. Dean]

On 04/06/2015 02:38 PM, Ian Evans wrote:
> On Mon, Apr 6, 2015 at 2:33 PM, Nicolas Riendeau wrote:
>> Hi!
>>
>> On 2015-04-06 2:14 PM, Ian Evans wrote:
>>
>>> Noticed an issue with accents in some shows and descriptions in the
>>> program grid. As I was scrolling through the listings, both on the TV
>>> and through Mythweb, I saw this show title:
>>>
>>> Justice for All With Judge Cristina Pérez
>>>
>> This sounds like UTF-8 which is parsed/shown as if it was ISO-8859-1 or
>> something similar..
>>
>> Is this a new problem?
>>
>>
> Just answered Karl but will put it here too. Seems to be intermittent. My
> eye just caught it today on a few titles, but I don't always notice it.
>
>
>
>>> on Zap2it it shows as Justice for All With Judge Cristina Pérez.
>>>
>>> I've noticed the same é issue on French Canadian shows. Just wondering
>>> if it's a Myth issue or possibly how it's being received from Schedules
>>> Direct.
>>>
>>>
>> If definitely sounds like properly encoded UTF-8 characters which are
>> shown as if it was another character set...
>>
>> Any idea when this started happening and what version of MythTV are you
>> running (master or -fixes and if -fixes, what version?)
>>
>> (If it is master then I might have an idea of a possible reason for
>> this...)
>>
>>
> Running .27-fixes. As above it's an intermittent problem. Karl suggested
> it might be a Schedules Direct issue.
>
> You have a nice day too.

Before going any farther with this issue, please make sure that neither 
mythbackend nor mythfilldatabase nor mythfrontend  logs (ideally on any 
of your hosts) output the warning:

This application expects to be running a locale that specifies a UTF-8 
codeset, and many features may behave improperly with your current 
language settings. Please set the LC_ALL or LC_CTYPE, and LANG 
variable(s) in the environment in which this program is executed to 
include a UTF-8 codeset (such as 'en_US.UTF-8').

If so, please fix that as the first step.  If you do not fix that, you 
/should/ be having problems with encodings/characters--as the logs 
state.  :)

Mike