Although the consortium has considered this issue, there are no
current plans for the development or certification of programmatic
---Bob Verbrugge <firstname.lastname@example.org> wrote:
> Are there any plans for adding programs/benchmarks which test the
> complience of programs implementing technical reports? In my opnion
> would be usefull for developers as well as the Unicode consortiom
> 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 <email@example.com>
> > To: Unicode List <firstname.lastname@example.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
> > discussion or approval. These papers can have significant impact
> > recommendations for implementations and on Unicode conformance.
> > how Unicode text is normalized for program identifiers and on the
> > Unicode text should line-break, how to deal with characters that
> > have full-width or half-width in East Asian contexts, and how to
> > characters.
> > If you have any feedback on these topics, be sure to review the
> > send your feedback to contact point listed in each paper. For
> > any UTC meeting, you should make sure that your comments are sent
> > 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
> > include how to handle Unicode characters in regular expressions,
> > and terminology for character encodings, handling Unicode on
> > 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
> > 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