From rick@unicode.org Fri Feb 3 11:04:27 2006 Received: with ECARTIS (v1.0.0; list hebrew); Fri, 03 Feb 2006 12:13:36 -0600 (CST) Received: from izanami (c-67-180-167-17.hsd1.ca.comcast.net [67.180.167.17]) by unicode.org (8.13.4/8.12.11) with SMTP id k13H4BSw002652; Fri, 3 Feb 2006 11:04:12 -0600 Message-Id: <200602031704.k13H4BSw002652@unicode.org> To: unicode@unicode.org Subject: [hebrew] Announcement: CLDR 1.4 Data Submission Period Now Starting Date: Fri, 3 Feb 2006 09:04:13 -0800 From: Rick McGowan received: by Apple.Mailer (2.95.2) X-archive-position: 2992 X-Approved-By: cowan@ccil.org X-ecartis-version: Ecartis v1.0.0 Sender: hebrew-bounce@unicode.org Errors-to: hebrew-bounce@unicode.org X-original-sender: rick@unicode.org Precedence: bulk X-list: hebrew Mountain View, CA, USA - 2006-02-03 - The Unicode Consortium today announced the start of the submission period for locale and language data for CLDR Version 1.4. The Common Locale Data Repository (CLDR) project provides a general XML format for the exchange of language and locale data for use in application and system development, and gathers, stores, and makes available a common set of language and locale data generated in that format. CLDR Version 1.3 contained data for 96 languages and 130 territories. In addition to new data, CLDR 1.4 will add new structure to support, among other things: flexible date & time formatting (including quarters), measurement system names, segmentation (customized line & word break), and transliteration. For more information, see http://www.unicode.org/cldr/. During this period, the Unicode consortium encourages the submission of proposed new data and proposed corrections into the repository. Most of the data can be entered or viewed via the newly-revised Survey Tool at http://unicode.org/cldr/apps/survey. An "Instructions" link on that page provides usage information. At the end of the submission period (2006-03-15), there is a vetting period for the submitted data. CLDR 1.4 is scheduled for release on 2006-05-15. From rick@unicode.org Tue Feb 21 15:31:08 2006 Received: with ECARTIS (v1.0.0; list hebrew); Tue, 21 Feb 2006 15:37:55 -0600 (CST) Received: from izanami (c-67-180-167-17.hsd1.ca.comcast.net [67.180.167.17]) by unicode.org (8.13.4/8.12.11) with SMTP id k1LLUmxO004835; Tue, 21 Feb 2006 15:30:48 -0600 Message-Id: <200602212130.k1LLUmxO004835@unicode.org> To: unicode@unicode.org Subject: [hebrew] Announcement: Beta 2 of Unicode 5.0 Data Files Date: Tue, 21 Feb 2006 13:30:49 -0800 From: Rick McGowan received: by Apple.Mailer (2.95.2) X-archive-position: 2993 X-Approved-By: cowan@ccil.org X-ecartis-version: Ecartis v1.0.0 Sender: hebrew-bounce@unicode.org Errors-to: hebrew-bounce@unicode.org X-original-sender: rick@unicode.org Precedence: bulk X-list: hebrew The Unicode Consortium has decided to issue Beta 2 of the Unicode Character Database for Unicode 5.0. This extends the feedback period until May 9, 2006. The relevent public review issues for UAXes have also been extended to the same date. Some information on changes and updates to the UAX #9 beta will be announced soon. Data files will also be updated during this period. During the extended beta review period for Unicode 5.0, the UTC is seeking feedback on potential errors or inconsistencies in all of the data files. However, please note that some of the character properties will be frozen as of March 1. The freeze will apply to all properties defined in the following files: UnicodeData.txt, Scripts.txt, and EastAsianWidth.txt; to a specific list of properties from PropList.txt (White_Space, Hex_Digit, Diacritic, and Ideographic); and to two derived properties, Numeric_Value and Numeric_Type. Substantive feedback received after March 1 regarding any of those properties will be recorded and taken into consideration in review of future versions of the standard, but will not be reflected in modifications for Unicode 5.0. The Unicode 5.0.0 beta data files are available at http://www.unicode.org/Public/5.0.0/ucd/. General information regarding 5.0 data files is available at http://www.unicode.org/Public/5.0.0/. If you have comments for official UTC consideration, please post them by submitting your comments through our feedback & reporting page: http://www.unicode.org/reporting.html If you wish to discuss issues on the Unicode mail list, then please use the following link to subscribe (if necessary). Please be aware that discussion comments on the Unicode mail list are not automatically recorded as input to the UTC. You must use the reporting link above to generate comments for UTC consideration. http://www.unicode.org/consortium/distlist.html Regards, Rick McGowan Unicode, Inc. From rick@unicode.org Sat Feb 25 11:23:46 2006 Received: with ECARTIS (v1.0.0; list hebrew); Sat, 25 Feb 2006 14:57:57 -0600 (CST) Received: from izanami (c-67-180-167-17.hsd1.ca.comcast.net [67.180.167.17]) by unicode.org (8.13.4/8.12.11) with SMTP id k1PHNOKj010701; Sat, 25 Feb 2006 11:23:26 -0600 Message-Id: <200602251723.k1PHNOKj010701@unicode.org> To: unicode@unicode.org Subject: [hebrew] New Public Review Issue: UAX #9 Bidi Algorithm, Proposed Update Date: Sat, 25 Feb 2006 09:23:29 -0800 From: Rick McGowan received: by Apple.Mailer (2.95.2) X-archive-position: 2994 X-Approved-By: cowan@ccil.org X-ecartis-version: Ecartis v1.0.0 Sender: hebrew-bounce@unicode.org Errors-to: hebrew-bounce@unicode.org X-original-sender: rick@unicode.org Precedence: bulk X-list: hebrew The Unicode Technical Committee has posted a new issue for public review and comment. Details are on the following web page: http://www.unicode.org/review/ Review period for the new item closes on May 9, 2006. Please see the page for links to discussion and relevant documents. Briefly, the new issue is: Conformance to the Unicode Bidi Algorithm (UAX #9) has been tightened in the area of bidi mirroring. The list of characters with the Bidi_Mirrored property has also been extended for consistency. Several other editorial clarifications have been made. http://www.unicode.org/reports/tr9/tr9-16.html If you have comments for official UTC consideration, please post them by submitting your comments through our feedback & reporting page: http://www.unicode.org/reporting.html If you wish to discuss issues on the Unicode mail list, then please use the following link to subscribe (if necessary). Please be aware that discussion comments on the Unicode mail list are not automatically recorded as input to the UTC. You must use the reporting link above to generate comments for UTC consideration. http://www.unicode.org/consortium/distlist.html Regards, Rick McGowan Unicode, Inc.