public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Darrell Shandrow" <nu7i@azboss.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Red Hat character set issues now resolved; thanks!
Date: Wed, 11 Dec 2002 22:54:06 -0700	[thread overview]
Message-ID: <000601c2a1a2$e52a6550$0201a8c0@nu7i> (raw)
In-Reply-To: <Pine.LNX.4.50.0212112247500.24280-100000@wb2flw.octothorp.org>

Hi Bill,

So, upon login, the /etc/sysconfig/i18n file is read?

Thanks.

----- Original Message -----
From: "William F. Acker WB2FLW +1-303-777-8123" <wacker@octothorp.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, December 11, 2002 10:50 PM
Subject: Re: Red Hat character set issues now resolved; thanks!


> Logging out and back in should have taken care of it.  Even better, export
> LANG=en_US in the current session.
>
>           HTH and 73.
> --
>           Bill in Denver
>
>
> On Wed, 11 Dec 2002, Darrell Shandrow wrote:
>
> > Hi all,
> >
> > Thanks to Janina for the excellent lead to the root of my issue with all
the "garbage" characters when remotely establishing a terminal to one of my
RH boxes.  I used locale -a to determine the correct locale setting, then
removed the .utf8 from the end of the lang spec in /etc/sysconfig/i18n,
rebooted and my issue is resolved.  Since I know most things in Linux should
not require a reboot, how could I have avoided this in this situation?
> >
> > Thanks.
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Darrell Shandrow
 ` William F. Acker WB2FLW +1-303-777-8123
   ` Darrell Shandrow [this message]
     ` William F. Acker WB2FLW +1-303-777-8123

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000601c2a1a2$e52a6550$0201a8c0@nu7i' \
    --to=nu7i@azboss.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).