ical issues -- compositing on the fly
still will not produce very pleasing results. (But it could produce legible
results.)
I'm sure a lot of the participants on this list are familiar with these
issues. But I think it is worth looking at them again. That's why I brought
them up.
Joel Rees
On 2001.02.25, Christopher John Fynn responded
> Joel Rees [mailto:[EMAIL PROTECTED]] wrote:
>
> ...
>
> > Maybe I'm a crackpot, but the need is there and people will use and
abuse
> > UNICODE in ways that you probably don't want to imagine. What I'm tryin
er attached to the Internet for every two people
alive?) The non-dense packing is the reason we are running out.
Joel Rees
each language take their own good time about registering.
The smaller approach will meet less resistance, be more flexible, and take
less time.
Joel Rees
- Original Message -
From: "Michael Everson" <[EMAIL PROTECTED]>
To: "Unicode List" <>
Sent: Monday, F
On 2001.02.23 19:42 Arnt Gulbrandsen <[EMAIL PROTECTED]> asked:
> Joel Rees <[EMAIL PROTECTED]>
> > I'm telling you that 17 planes is not enough, and it _will_ become a
painful
> > constraint in your lifetime.
>
> How? It looks likely to me that uni
On 2001.02.23 15:06, Curtis Clark wrote:
> At 07:04 PM 2/22/01, Joel Rees wrote:
> >I'm telling you that 17 planes is not enough, and it _will_ become a
painful
> >constraint in your lifetime.
>
> So Plane 9, say, can be nothing but surrogates-of-surrogates, to some 6
Ken,
Thanks for the consideration. I threw my ego away years ago.
> Joel,
>
> > > Note that I am just sending a response to you, not to the list.
> >
> > I wouldn't mind this being on the list. I was making bad assumptions
about
> > Sun's and others's reasons for wanting to do perverse things wi
Kenneth Whistler explained:
> Joel Rees responded:
>
> > >
> > > Idiosyncratic and personal characters are not encoded in Unicode.
> >
> > I find this a fault in UNICODE. When we go through the set algebrae in
the
> > introductory algebra courses for c
s, the jump to the next
standard will be a lot easier, and can be postponed a lot longer.
Joel Rees, Media Fusion
Amagasaki, Japan
rly in the transform parse.
You wouldn't want to show them C source, especially if you use a macro to
optimize direct conversion. I'm sure that wouldn't go down well at all.
Joel Rees, Media Fusion
Amagasaki, Japan
On 2001.02.23 08:37, Christopher wrote
>
> On Wednesday, February 21, 2001 8:50 PM
> Joel Rees [mailto:[EMAIL PROTECTED]] wrote:
>
>
> ...
>
> > Everyone could do what they want out there, but they would be
responsible
> > for publishing whatever needed to b
, and thanks for the references, Thomas. That's beautiful stuff.
Joel Rees, Media Fusion
Amagasaki, Japan
mple Java (I think) source for handling surrogate pairs
available either on the UNICODE site or the ISO site for ISO/IEC 10646. I
should have mentioned that in the earlier post, and I apologize.
Joel Rees, Media Fusion KK
Amagasaki, Japan
ard language for communicating about the
local standards as a vehicle for transmitting default character shapes for
exceptional characters that are not found in the UNICODE proper.
Joel Rees, Media Fusion, KK
Amagasaki, Japan
- Original Message -
From: "Thomas Chan" <[EMAIL PR
a program that would fill more than 64K of memory.
:)
Joel Rees, Media Fusion KK
Amagasaki, Japan
- Original Message -
From: "Marco Cimarosti" <[EMAIL PROTECTED]>
To: "Unicode List" <[EMAIL PROTECTED]>
Sent: Wednesday, February 21, 2001 5:53 PM
Subject:
I would still suggest you check out UTF-8 and see if that standard
transformation might make sense for your application.
Joel Rees, Media Fusion KK
Amagasaki, Japan
- Original Message -
From: "William Overington" <[EMAIL PROTECTED]>
To: "Unicode List" <[EMAIL P
arch purposes and for doing _something_ with
those characters that get invented for various technical purposes each year.
> . . .
I'd better quit fantasizing in public and get back to work. Thanks again.
Joel Rees, Media Fusion KK
Amagasaki, Japan
Hi!
I just signed up today after receiving a note from a fellow macperler that
3.1 (extension B) included 40,000+ new Kanji. I checked unicode.org and
noted that 3.1 was in beta at last update, but that the conference period
for errata had ended.
(http://www.unicode.org/unicode/standard/ver
18 matches
Mail list logo
