On approximately 11/5/2008 11:47 PM, came the following characters from
the keyboard of Stephen J. Turnbull:
Glenn Linderman writes:
> But the API could speak Unicode, and do the appropriate translations.
> Or in some cases, inappropriate translations.
You've written that kind of thing three or four times by now. As far
as I can see, you just don't care about any requirements beyond your
own.
I suppose you could interpret it that way. I thought I was describing
how to handle things for different cases. It would help if you could
elucidate and enumerate the requirements you see, that you don't think
that I see, or point to some place where they already are elucidated and
enumerated, so I could learn what they are.
> Please be specific; just mentioning bit-flicking, or error cases, or bad
> encoding sounds terrible, but provides little information as to how it
> can be handled via some theoretical bytes interface that cannot be
> handled equally as effectively (although perhaps not equally
> efficiently) via a transliterated Unicode data stream.
I did. You missed it. Reread my example of mixing types. That is
not theory, that is Emacs practice. And it's not good practice.
There is no reference to the word emacs or types in any of the messages
you've posted in this thread, maybe you are referring to another thread
somewhere? Sorry, I'm new to this party, but I have read the whole
thread... unless my mail reader has missed part of it.
--
Glenn -- http://nevcal.com/
===========================
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
