9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] simplicity
Date: Tue,  9 Oct 2007 23:08:08 +0200	[thread overview]
Message-ID: <5d375e920710091408p7ae6c223kff983da360f016e9@mail.gmail.com> (raw)
In-Reply-To: <200710092008.l99K8KZV004052@skeeve.com>

> >This was some years ago, it might be fixed by now, but it demonstrates
> >how the locale insanity makes life so much more fun.
>
> It likely is fixed by now.  If not, I'd like to have a sample program and
> data and locale name to test under. And the truth is, even if it doesn't work,
> I can blame the library routines and locale and not my code. :-)

Yes, it is likely fixed now, and it was very likely a bug in the
libraries rather than awk, but illustrates the kinds of problems
locales create. And I can tell you, in a production environment it can
be a pain when who knows what tool who knows where in your whole
system starts to misbehave because it is not happy with your locale.

I also find most sad how in the name of 'localization' the output of
many tools (specially error messages) has become unpredictable. It
makes providing support most fun when you ask people "can you copy
paste the output you get when you run this", and they answer with a
bunch of stuff Aramaic. If you use unix, you are supposed to
understand English, period. (Or what is next? will they have a set of
'magic symlinks' that links '/bin/gato' to '/bin/cat' if your locale
is in Spanish?)

And now that you mention Gettext, if only I could get back all the
time I wasted trying to compile some stupid program (that should never
have been 'localized' in the first place) which is somehow unhappy
about the gettext version I have (or the other way around)...

uriel

P.S.: Oh, and people who insist in using encodings other than UTF-8
should be locked up in padded cells (without access to computers and
ideally even without electricity, unless it is to help them
electrocute themselves) for the good of mankind.


  reply	other threads:[~2007-10-09 21:08 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 18:55 Francisco J Ballesteros
2007-09-16 20:42 ` Anant Narayanan
2007-09-16 21:24   ` Francisco J Ballesteros
2007-09-17 15:22     ` Douglas A. Gwyn
2007-09-16 20:43 ` roger peppe
2007-09-16 20:53   ` Steve Simon
2007-09-17 15:22     ` Douglas A. Gwyn
2007-09-17 20:00   ` Scott Schwartz
2007-09-17  3:23 ` erik quanstrom
2007-09-17 15:22   ` Douglas A. Gwyn
2007-09-17 15:55     ` erik quanstrom
2007-09-18  8:38       ` Douglas A. Gwyn
2007-09-18 10:45         ` dave.l
2007-09-18 14:44           ` Iruata Souza
2007-09-18 15:41             ` Douglas A. Gwyn
2007-09-18 21:34               ` Iruata Souza
2007-10-10  3:30         ` Jack Johnson
2007-10-10  4:02           ` erik quanstrom
2007-10-10  6:17             ` Jack Johnson
2007-10-10 12:22               ` erik quanstrom
2007-09-18 15:27     ` Rob Pike
2007-09-18 15:38       ` Uriel
2007-09-19  8:50         ` Douglas A. Gwyn
2007-09-19 11:51           ` erik quanstrom
2007-09-19 15:02             ` Russ Cox
2007-09-19 14:17           ` Charles Forsyth
2007-09-19 14:21           ` Iruata Souza
2007-09-19 15:32           ` Skip Tavakkolian
2007-10-09 20:08         ` Aharon Robbins
2007-10-09 21:08           ` Uriel [this message]
2007-10-10  5:33         ` sqweek
2007-10-10 11:49           ` erik quanstrom
2007-09-17 14:52 ` ron minnich
2007-09-17 14:53 ` ron minnich
2007-10-10  7:36 John Stalker
2007-10-10  8:24 ` Charles Forsyth
2007-10-10 11:47 ` erik quanstrom
2007-10-10 14:05   ` John Stalker
2007-10-10 14:29     ` erik quanstrom
2007-10-10 15:26       ` John Stalker

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=5d375e920710091408p7ae6c223kff983da360f016e9@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).