Re: New draft Unicode technical reports available for review

From: Mark Davis (mark_macchiato@yahoo.com)
Date: Tue Nov 03 1998 - 21:02:04 EST


Although the consortium has considered this issue, there are no
current plans for the development or certification of programmatic
compliance tests.

Mark

---Bob Verbrugge <bob_verbrugge@nl.compuware.com> wrote:
>
> Mark,
>
> Are there any plans for adding programs/benchmarks which test the
Unicode
> complience of programs implementing technical reports? In my opnion
this
> would be usefull for developers as well as the Unicode consortiom
itself in
> certifying implementations to be Unicode compliant.
>
> Bob Verbrugge.
>
>
> > From unicode.org!unicode@alushta.NL.net Mon Nov 2 20:45 MET 1998
> > Mime-Version: 1.0
> > Content-Transfer-Encoding: 8BIT
> > X-Uml-Sequence: 6401 (1998-11-02 19:10:25 GMT)
> > From: Mark Davis <medavis2@us.ibm.com>
> > To: Unicode List <unicode@unicode.org>
> > Date: Mon, 2 Nov 1998 11:10:24 -0800 (PST)
> > Subject: New draft Unicode technical reports available for review
> > Content-Transfer-Encoding: quoted-printable
> >
> > Unicode Technical Committee (UTC) meeting #78 will be held the
first week of
> > December. As at every meeting, technical reports on
> > http://www.unicode.org/unicode/reports/techreports.html will come
up for
> > discussion or approval. These papers can have significant impact
on the
> > recommendations for implementations and on Unicode conformance.
Topics include
> > how Unicode text is normalized for program identifiers and on the
web, how
> > Unicode text should line-break, how to deal with characters that
can either
> > have full-width or half-width in East Asian contexts, and how to
sort Unicode
> > characters.
> >
> > If you have any feedback on these topics, be sure to review the
documents, and
> > send your feedback to contact point listed in each paper. For
consideration at
> > any UTC meeting, you should make sure that your comments are sent
well before
> > the meeting dates.
> >
> > The draft technical reports include:
> >
> > UTR #15: Unicode Normalization Forms
> > UTR #14: Line Breaking Properties
> > UTR #13: Unicode Newline Guidelines
> > UTR #11: East Asian Character Width
> > UTR #10: Unicode Collation Algorithm
> >
> > In addition. we will be now be posting proposed draft technical
reports as they
> > become available. These are in an earlier stage of development,
and have not
> > yet been considered by the UTC, so feedback is especially
valuable. Topics
> > include how to handle Unicode characters in regular expressions,
the structure
> > and terminology for character encodings, handling Unicode on
EBCDIC systems,
> > coding annotations (Ruby), and the Unicode BIDI algorithm.
> >
> > UTR #18: Unicode Regular Expression Guidelines
> > UTR #17: Character Encoding Model
> > UTR #16: EBCDIC-Friendly UCS Transformation Format
> > UTR #12: Support for Interlinear Annotations
> > UTR #9: The Bidirectional Algorithm Reference Implementation
> >
> >
> > (UTR #6: Standard Compression Scheme for Unicode (SCSU) has also
been
> > updated--editorial fixes only.)
> >
> >
>
>
>

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com



This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:42 EDT