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

Tue Apr 7 20:20:56 UTC 2015

On Tue, Apr 7, 2015 at 12:56 PM, Hika van den Hoven <hikavdh at gmail.com>
wrote:

> Hoi Karl,
>
> Tuesday, April 7, 2015, 9:42:34 PM, you wrote:
>
> > On Tue, Apr 7, 2015 at 11:22 AM, Hika van den Hoven <hikavdh at gmail.com>
> > wrote:
>
> >> Hoi Karl,
> >>
> >> Tuesday, April 7, 2015, 8:01:30 PM, you wrote:
> >>
> >> > On Tue, Apr 7, 2015 at 10:14 AM, Hika van den Hoven <
> hikavdh at gmail.com>
> >> > wrote:
> >>
> >> >> 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)
> >> >>
> >> >> I do seem to recall fighting with this a bit, but eselect locale
> offers
> >> > en_US.UTF-8 on my system. Here's my /etc/locale.gen:
> >>
> >> > # /etc/locale.gen: list all of the locales you want to have on your
> >> system
> >> > #
> >> > # The format of each line:
> >> > # <locale> <charmap>
> >> > #
> >> > # Where <locale> is a locale located in /usr/share/i18n/locales/ and
> >> > # where <charmap> is a charmap located in /usr/share/i18n/charmaps/.
> >> > #
> >> > # All blank lines and lines starting with # are ignored.
> >> > #
> >> > # For the default list of supported combinations, see the file:
> >> > # /usr/share/i18n/SUPPORTED
> >> > #
> >> > # Whenever glibc is emerged, the locales listed here will be
> >> automatically
> >> > # rebuilt for you.  After updating this file, you can simply run
> >> > `locale-gen`
> >> > # yourself instead of re-emerging glibc.
> >>
> >> > en_US ISO-8859-1
> >> > en_US.UTF-8 UTF-8
> >> > #ja_JP.EUC-JP EUC-JP
> >> > #ja_JP.UTF-8 UTF-8
> >> > #ja_JP EUC-JP
> >> > #en_HK ISO-8859-1
> >> > #en_PH ISO-8859-1
> >> > #de_DE ISO-8859-1
> >> > #de_DE at euro ISO-8859-15
> >> > #es_MX ISO-8859-1
> >> > #fa_IR UTF-8
> >> > #fr_FR ISO-8859-1
> >> > #fr_FR at euro ISO-8859-15
> >> > #it_IT ISO-8859-1
> >>
> >>
> >> > And here's /etc/env.d/02locale:
> >> > LANG="en_US.UTF-8"
> >> > LC_COLLATE="C"
> >> > #LC_CTYPE="en_US.UTF-8"
> >> > #LC_ALL=en_US.UTF-8
> >>
> >> Looks OK. I now have only LANG="nl_NL.UTF-8" in there. And it's in
> >> essence the same as mine. I only have three dutch strings extra:
> >> UTF-8, iso8858-1 and iso8859-15. But I normally only use dutch utf.
> >>
> >> What does eselect locale list offer on your system?
> >>
> >>  $ eselect locale list
> > Available targets for the LANG variable:
> >   [1]   C
> >   [2]   POSIX
> >   [3]   en_US
> >   [4]   en_US.iso88591
> >   [5]   en_US.utf8
> >   [6]   en_US.UTF-8 *
> >   [ ]   (free form)
>
> So you also have that wrong utf8 string. You also added the right one
> by hand (free form)? I Have these the nl_NL variants including 8859-15
> (with euro) and 'dutch' I guess that's the outdated alias pointing to
> nl_NL.iso-8859-1. Nothing hinting to nl_US??
>
> I can't remember. I may have typed it as "free form". I know I did have it
set to the utf8 string and was baffled why myth was still complaining
because that was the only UTF-8 option offered by the system. Also I think
I discovered that for some stupid reason it appears to be case sensitive in
addition to needing the hyphen. Yay, standards!

Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20150407/4fa1eb58/attachment.html>