Title: Nabitel information broadcast mail
Sorry for interrupting you - click refuse for no more mail... - Welcome to Domain Free Auction site - Domain Auc
At 05:03 PM 1/8/2003 -0600, John Goerzen wrote:
Yes, there are UTF-8 versions available. Does everyone have them? Do we
enable them by default?
Everyone who has the most recent version. They're enabled by default if you're
running a UTF-8 locale, like they should be.
Do all other vendors sh
On Wed, 2003-01-08 at 18:03, John Goerzen wrote:
> Colin was advocating what amounted to exactly that. He was advocating
> removing all support for non-UTF8 terminals.
Um, woah there. The key word is *eventually*. Again: the only "must"
my present policy proposal introduces is for filenames in
On Wed, Jan 08, 2003 at 02:54:43PM -0800, David Starner wrote:
> At 02:32 PM 1/8/2003 -0600, John Goerzen wrote:
> >It's not just physical terminals we're talking about here. We're talking
> >about the vast majority of the state of the art terminal emulators *today*.
>
> I'd have a hard time des
At 02:32 PM 1/8/2003 -0600, John Goerzen wrote:
>It's not just physical terminals we're talking about here. We're talking
>about the vast majority of the state of the art terminal emulators *today*.
I'd have a hard time describing a terminal emulator that doesn't support
UTF-8 as "start of the a
On Tue, Jan 07, 2003 at 03:50:45PM -0800, David Starner wrote:
> If you're using a terminal that can't support UTF-8, you always have the
> option of running
> something like GNU screen to translate the system charset to the terminal
> charset.
> It seems more important to get a systemwide encodi
On Wed, Jan 08, 2003 at 01:30:09AM -0500, Colin Walters wrote:
> > I like
> > the idea that I can download any old program written in a past
> > decade and just type make.
>
> Yay for broken software.
Unicode did not exist until fairly recently. Lots of useful software was
written prior to its i
Hello .. i'm not in this ML, but got the smell of this thread
it from newsletter and couldn't resists to pitch in with my
way of cleaning the home.
Here is what I to get rid of various junk in my $HOME:
1. Have a directory ~/... ( just like ~/.etc, however
'...' looks really good in ls -
On Tue, Jan 07, 2003 at 10:23:14AM -0500, Colin Walters wrote:
> On Tue, 2003-01-07 at 04:29, Denis Barbier wrote:
>
> Uploading packages with UTF-8 control fields is not ok. It will simply
> put, not work for anyone who's not using a UTF-8 terminal, which is
> unfortunately probably most of our
On Wed, Jan 08, 2003 at 01:10:36AM -0500, Colin Walters wrote:
> On Tue, 2003-01-07 at 18:50, David Starner wrote:
> > If you're using a terminal that can't support UTF-8, you always have the
> > option of running
> > something like GNU screen to translate the system charset to the terminal
> > c
On Tue, 2003-01-07 at 03:07, Jakob Bohm wrote:
> I agree, this is the only way to go. Naive, simple, classic
> UNIX-style programming should continue to "just work",
Naïve, simple, classic UNIX-style programs are ASCII-only. Then someone
got the idea to bolt this huge "locale" kludge on top of
At 01:10 AM 1/8/2003 -0500, Colin Walters wrote:
>That is interesting advice. I am not sure I understand exactly how it
>would work though. Would you just tell screen that all input is in
>UTF-8? It seems like this would not be true if the user has legacy
>filenames, and they do something simple
On Mon, 2003-01-06 at 16:15, Jochen Voss wrote:
> Hello Colin,
>
> On Fri, Jan 03, 2003 at 09:50:26PM -0500, Colin Walters wrote:
> > In summary, UTF-8 is the *only* sane character set to use for
> > filenames.
> At least I agree to this :-)
Cool.
> I think that we need filename conversion betwe
On Tue, 2003-01-07 at 11:58, Denis Barbier wrote:
> On Tue, Jan 07, 2003 at 10:23:14AM -0500, Colin Walters wrote:
> [...]
> > It looks to me like at this point almost everyone agrees with the
> > content of my proposal in #99933, and we are discussing implementation
> > details. Agreed?
>
> No.
On Tue, 2003-01-07 at 18:50, David Starner wrote:
> If you're using a terminal that can't support UTF-8, you always have the
> option of running
> something like GNU screen to translate the system charset to the terminal
> charset.
> It seems more important to get a systemwide encoding working, t
On Tue, 2003-01-07 at 15:10, John Goerzen wrote:
> Colin Walters <[EMAIL PROTECTED]> writes:
>
> > On Tue, 2003-01-07 at 13:50, John Goerzen wrote:
> >
> > Sorry, we have to start somewhere. Unicode is the way of the future,
> > and if we wait until every vendor of some random terminal updates it
16 matches
Mail list logo
