Comment 12 for bug 225532

en_NG is in fact missing from /var/lib/locales/supported.d/en . After
adding it there using gedit, like so: lang_LOCALE.encoding, gnochm no
longer crashes, however, it doesn't display the document text, and
still prints the error message. It populates the contents pane fine
though.

On 5/8/08, Fanen A. <email address hidden> wrote:
> Inspecting /usr/share/i18n/SUPPORTED lists "en_NG UTF-8". I observe
> that there is a missing 'period' between the en_NG part and the utf-8.
> I suppose that's a syntax error, and may well be the cause of the bug?
> The dots are missing in alternate entries.
>
> On 5/7/08, Lars L <email address hidden> wrote:
> > I believe there are two problems here. One is that some Python programs
> > doesn't have proper error handling (see also bug #131205). The fact that
> > locale.py throws an exception is fine, it's just that the applications
> > needs to catch this. The other problem is that en_NG is not a defined
> > locale for some reason. Have a look at "man locale-gen", it might shine
> > some light over that issue.
> >
> > On my system en_NG is listed in /usr/share/i18n/SUPPORTED, using locales
> > 2.7.9-4
> >
> > --
> > system-config-printer crashes on an unrecognised locale
> > https://bugs.launchpad.net/bugs/225532
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> Sent from Gmail for mobile | mobile.google.com
>

--
Sent from Gmail for mobile | mobile.google.com