From: james woodyatt <jhw@wetware.com>
To: The Trade <caml-list@inria.fr>
Cc: skaller@users.sourceforge.net
Subject: Re: [Caml-list] Bug with really_input under cygwin
Date: Wed, 10 Mar 2004 22:32:42 -0800 [thread overview]
Message-ID: <E6619982-7325-11D8-A2BF-000393B8133A@wetware.com> (raw)
In-Reply-To: <1078976542.2452.106.camel@pelican.wigram>
On 10 Mar 2004, at 19:42, skaller wrote:
>
> As long as these kinds of comments are labelled as 'rants' people will
> continue to write non-portable software and fail to face up to the
> issues.
Can I get an "Amen!" brothers and sisters.
And while we are categorizing difficulties handling text that too many
people are unwilling to face realistically, can we bring up the
constellation of issues revolving around lexicographical comparisons?
Text comparison (sorting), parsing and matching can be a royal pain in
the rear end if you're trying to maintain localization capabilities.
We all desperately need to pay more attention to localization—
especially if we are committed to retaining our cultural affinity for
dead and dying natural languages in the digital era.
--
j h woodyatt <jhw@wetware.com>
markets are only free to the people who own them.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-03-11 6:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 22:30 Eric Dahlman
2004-03-09 22:52 ` Karl Zilles
2004-03-10 3:06 ` skaller
2004-03-10 4:10 ` David Brown
2004-03-10 13:14 ` Richard Zidlicky
2004-03-11 4:11 ` skaller
2004-03-11 3:24 ` skaller
2004-03-10 15:25 ` Nuutti Kotivuori
2004-03-11 3:42 ` skaller
2004-03-11 5:02 ` Nuutti Kotivuori
2004-03-11 15:21 ` skaller
2004-03-11 6:32 ` james woodyatt [this message]
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=E6619982-7325-11D8-A2BF-000393B8133A@wetware.com \
--to=jhw@wetware.com \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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).