From ybf2u@curry.edschool.virginia.edu Tue Jan 24 13:37:14 1995 Received: from uvaarpa.Virginia.EDU by apollo.aoe.vt.edu via SMTP (920330.SGI/911001.SGI) for yacob id AA16580; Tue, 24 Jan 95 13:37:14 -0500 Received: from curry.edschool.virginia.edu by uvaarpa.virginia.edu id aa03351; 24 Jan 95 13:37 EST Received: (from ybf2u@localhost) by curry.edschool.Virginia.EDU (8.6.8/8.6.6) id NAA73787; Tue, 24 Jan 1995 13:37:04 -0500 From: Yitna Benyam Firdyiwek Message-Id: <199501241837.NAA73787@curry.edschool.Virginia.EDU> Subject: Re: Unicode (this time for sure) To: danEl yaKob , Yonas Fisseha , Abass Alamnehe Date: Tue, 24 Jan 95 13:37:04 EST In-Reply-To: <199501241628.LAA52584@curry.edschool.Virginia.EDU>; from "Daniel Yaqob" at Jan 24, 95 11:26 am X-Mailer: ELM [version 2.3.1 PL11] Status: R Selam UTC Members: In response to danEl's response to using ACG > . . .I do not think security would become > a problem. Would it be a good idea to keep our postings archived > for people who come into the discussion later (archived on web). Good. Yes, I think our communications should be archived, however, not made public until we are done. Those who join committee late, of course, would have access to it. > > . . .to include other members of the > software community in these discussions, I know of a few with email > accounts. Critical to its implementation will be the question of the > vendor "Can I use it?" I have seen some software packages that would > have had to limit what they offered if working with the first > proposal. Hence the value of their input during design of a table for I am not sure about including any vendors specifically for the above reason. I am not sure whether their issues could be immediately addressed, and I'm afraid their concerns might confuse us. If we invite participants who happen to be vendors, it should be for what they can contribute to to the problems posed by UNICODE, and not to address their commercial interest. On the other hand, I think it is important for us to know the various systems employed by vendors and how they relate to what we end up with. We had no such imput in the previous committee. Maybe we should have a list of names before we contact anyone. Personally, I think the four of us are enough, but would accept one or two more people. We do have to watch out not to have too many cooks. cheers, yTna