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