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

Hika van den Hoven hikavdh at gmail.com
Tue Apr 7 17:14:07 UTC 2015


Hoi Karl,

Tuesday, April 7, 2015, 7:09:07 PM, you wrote:

> On Tue, Apr 7, 2015 at 9:53 AM, Hika van den Hoven <hikavdh at gmail.com>
> wrote:

>> Hoi Michael,
>>
>> Tuesday, April 7, 2015, 6:43:52 PM, you wrote:
>>
>> > On 04/07/2015 11:25 AM, Hika van den Hoven wrote:
>> >> Hoi Michael,
>> >>
>> >> Tuesday, April 7, 2015, 5:18:35 PM, you wrote:
>> >>
>> >>> On 04/07/2015 11:03 AM, Hika van den Hoven wrote:
>> >>>> It then doesn't do so good a job outside the US. It doesn't understand
>> >>>> nl_NL.UTF-8. It tries to make it us_NL.UTF-8 which doesn't exist. ;(
>> >>> You don't have to use us.  You'd use:
>> >>> export LC_ALL=nl_NL.UTF-8
>> >>> export LANG=nl_NL.UTF-8
>> >>> The only part you have to have is the UTF-8 (encoding) part--and any
>> >>> valid locale.  (Since MythTV doesn't change any of what you set, I'm
>> >>> assuming you understood my message to say that you have to use "us" in
>> >>> there somewhere?)
>> >> No It is set to nl_NL.UTF-8, but always complains it cannot find
>> >> us_NL.UTF-8. Which is correct for it does not exist. And everything
>> >> seems to go OK, so it's not more then annoying.
>>
>> > No, I'm guessing it's set for nl_NL.UTF8 or nl_NL.utf8, which is /not/
>> > nl_NL.UTF-8.  It will /only/ complain when it's not set to the right
>> > value, so if you're getting the warning, you (or your distro) have got
>> > it set incorrectly (for Qt's needs).  It's possible Qt's code has been
>> > updated so that it will all handle UTF8 as well as UTF-8 (the hyphen
>> > being the thing that's required, not the capitalization), but some parts
>> > of Qt didn't when the code was added to MythTV to give that warning, so
>> > MythTV explicitly tells people to set it in a way that it will always
>> > work, on any distro or any Unix-like OS. Things /will/ go wrong if Qt
>> > doesn't pick up the right encoding--even if you don't notice things
>> > going wrong.
>>
>> > Unfortunately, though, users can't seem to figure out that UTF8 !=
>> > UTF-8, then write off the warning as "just more MythTV brokenness"
>> > because obviously the problem can't be my configuration.  And, when they
>> > don't notice issues, they think all is good.  But, hey, if you don't
>> > notice any problems, that means everything's good, right?  Just ask any
>> > smoker.
>>
>> It seems you're right. I did a qt upgrade last week (4.8.5 to 4.8.6)
>> and it now sings a different tune. It's no longer talking about
>> us_NL.UTF-8 but about nl_NL.utf8 and that's a first. I before tried
>> changing the string without effect? I'll try again.
>>

> Hika,

> Check `eselect locale` on Gentoo. Pick the one with "UTF-8". That may be
> all you need.

> Karl

Thanks, I know, but even though I set it right in /etc/locale.gen
locale-gen changes the strings.
I have
en_US.UTF-8 UTF-8
nl_NL.UTF-8 UTF-8
and some others in there, but eselect only offers em_US.utf8 and
nl_NL.utf8 (and those others for iso8859)

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens



More information about the mythtv-users mailing list