On Sat, May 31, 2008 at 12:53 AM, Mick <[EMAIL PROTECTED]> wrote:

> On Saturday 31 May 2008, Kevin O'Gorman wrote:
>
> > I did not have 02locale in /etc/env.d/dir, although there was a lot of
> > other stuff in that directory.
> > I added the two lines.
> > I ran env-update
> > I ctl-alt-backspace restarted my KDE/X system
> > I clicked k3b on the Multimedia submenu
> >
> > It barked at me again about x3.4-1968.
> >
> > So something isn't getting set up.
> >
> > I have a feeling about "02locale" being so specific.  Why "02".  Back in
> > the days when I had
> > a similar thing going on with SysV Init, we had such stuff in our rc.d
> > directory for run levels.
> > Most of those files got installed by particular owning packages.  Would
> > anyone who has
> > this file, and does not think they created it from scratch, please find
> out
> > what package
> > it belongs to?  Thanks.
>
> I can't comment on the 02locale, because I have not used it.  However, on
> my
> machine setting up either the LANG=en_GB, or LC_ALL=en_GB does the trick
> and
> k3b does not complain about charset ANSI_X3.4-1968 and what not.
>
> Just a thought - have you run # locale-gen first?
> --
>
> Just to be sure, I re-ran locale-gen just now.  It reported two problems
with a Polish
locale (that I do not use):

treat ~ # locale-gen
 * Generating 6 locales (this might take a while) with 1 jobs
 *  (1/6) Generating en_US.ISO-8859-1 ...  [ ok ]
 *  (2/6) Generating en_US.UTF-8 ...  [ ok ]
 *  (3/6) Generating es_MX.ISO-8859-1 ...   [ ok ]
 *  (4/6) Generating fr_FR.ISO-8859-1 ...     [ ok ]
 *  (5/6) Generating [EMAIL PROTECTED] ... [ ok ]
 *  (6/6) Generating pl_PL.ISO-8859-15 ...
/usr/share/i18n/locales/pl_PL:2130: LC_MONETARY: unknown character in field
`currency_symbol'
/usr/share/i18n/locales/pl_PL:2161: LC_TIME: unknown character in field
`day'                                                          [ !! ]
 * Generation complete
treat ~ #


I then ran env-update, restarted X, chose K3B from a KDE menu, and it
complained again.
So: no joy.


-- 
Kevin O'Gorman, PhD

Reply via email to