Re: Strange characters with pstree and ncurses apps -- i18n problem
From: Joe(theWordy)Philbrook (jtwdyp_at_ttlc.net)
Date: 07/11/04
- Previous message: Phil Dybvig: "Re: funky library linking problems in Fedora Core 2 x86_64"
- Maybe in reply to: Jason Aeschilman: "Strange characters with pstree and ncurses apps -- i18n problem"
- Next in thread: Mike Klinke: "Re: Strange characters with pstree and ncurses apps -- i18n problem"
- Reply: Mike Klinke: "Re: Strange characters with pstree and ncurses apps -- i18n problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: fedora-list@redhat.com Date: Sat, 10 Jul 2004 21:58:53 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It would appear that on Jul 10, Jason Aeschilman did say:
> Path: main.gmane.org!not-for-mail
> From: "Jason Aeschilman" <jason@fatpipeinc.com>
> Newsgroups: gmane.linux.redhat.fedora.general
> Subject: Strange characters with pstree and ncurses apps -- i18n problem
> Date: Sat, 10 Jul 2004 07:14:14 -0600
> Lines: 45
> Sender: fedora-list-bounces@redhat.com
> Approved: news@gmane.org
> Message-ID: <009901c4667f$cc1c1a10$9100000a@jasonpc>
> References:
> <200407101431.52437.fedora@universalgrid.nl><ECE72597196AF70EA3714829@[10.
> 0.0.4]><200407101449.41272.fedora@universalgrid.nl>
> <ccootg$v2i$1@sea.gmane.org>
<snip>
>
> Why does Red Hat 8 and later (including Fedora) default to UTF-8 characte=
> r
> encoding when most command line apps don't yet support it?
<SNIP>
Your question would have a better chance of reaching the guys with the
answers if you posted it as a NEW thread. (for threaded reading {and the
archives} changing the subject is not the same thing as starting a new thread.
I will admit that there isn't an actual "In-Reply-To:" header line in
your message, so I'm not completely sure that you started by hitting
reply to an existing message and then deleting everything you can see,
including the original subject. But I don't know how else the
"References:" header got there, and that too is used for threaded
reading...
In any case the result is your post looks to a threaded reader as if
it's a reply to a "tar" thread and quite possibly the UTF-8 experts
won't even see it.
This is sometimes called thread hi-jacking and is frowned on because of
the way it messes up threaded readers. To start a truly new thread you
need to start a NEW message. Editing a reply just doesn't work.
To the list:
Does anybody have a clue why his post didn't have an In- Reply-To: But
did have a References:????
- --
| ^^^ ^^^
| <o> <o> Joe (theWordy) Philbrook
| ^ J(tWdy)P
| ___ <<jtwdyp@ttlc.net>>
| ' `
##############################################################
# You can find my public gpg key at http://pgpkeys.mit.edu/ #
##############################################################
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA8J1NRZ/61mwhY94RAi9YAJ43DNTyfEvrDn5NJ9qKanJg1YiEMACfYxnv
0b+uT/G1zJZZmvViubCPdIM=
=NwDI
-----END PGP SIGNATURE-----
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
- Previous message: Phil Dybvig: "Re: funky library linking problems in Fedora Core 2 x86_64"
- Maybe in reply to: Jason Aeschilman: "Strange characters with pstree and ncurses apps -- i18n problem"
- Next in thread: Mike Klinke: "Re: Strange characters with pstree and ncurses apps -- i18n problem"
- Reply: Mike Klinke: "Re: Strange characters with pstree and ncurses apps -- i18n problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
