From tiro@tiro.com Mon Jul 4 23:11:56 2005 Received: with ECARTIS (v1.0.0; list hebrew); Mon, 04 Jul 2005 23:17:25 -0500 (CDT) Received: from priv-edtnes28.telusplanet.net (outbound04.telus.net [199.185.220.223]) by unicode.org (8.13.4/8.12.11) with ESMTP id j654BtN0031239; Mon, 4 Jul 2005 23:11:55 -0500 Received: from [154.5.24.36] by priv-edtnes28.telusplanet.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050705041149.FLVE29501.priv-edtnes28.telusplanet.net@[154.5.24.36]>; Mon, 4 Jul 2005 22:11:49 -0600 Message-ID: <42CA0889.5020706@tiro.com> Date: Mon, 04 Jul 2005 21:11:53 -0700 From: John Hudson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 CC: Unicode List , Hebrew List Subject: [hebrew] Re: Baseline level line? References: <42C21ACF.2020006@adobe.com> <42C2299C.9090100@tiro.com> <42C25B6D.3030209@tiro.com> <20050629230619.23651@smtp.jhu.edu> <42C398A6.9040301@tiro.com> <42C4BAC8.2080405@kli.org> In-Reply-To: <42C4BAC8.2080405@kli.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2984 X-Approved-By: jcowan@reutershealth.com X-ecartis-version: Ecartis v1.0.0 Sender: hebrew-bounce@unicode.org Errors-to: hebrew-bounce@unicode.org X-original-sender: tiro@tiro.com Precedence: bulk X-list: hebrew Mark E. Shoulson wrote: is 0640 good for it, as suggested? I'd be very wary about using U+0640, since it is an Arabic character and will presumably be passed to the Arabic shaping engine by a script processor such as Uniscribe. I'm going to have to ask MS to add support for Hebrew combining mark positioning on the other generic bases (U+25CB, U+25A1): at the moment, only U+25CC and the space/nbsp work okay as generic base characters. I don't even want to suggest that I'd like to apply Hebrew marks to the Arabic tatweel (although I do have a manuscript example of Hebrew written with Arabic letters and Hebrew nikud!) John Hudson -- Tiro Typeworks www.tiro.com Vancouver, BC tiro@tiro.com Currently reading: Truth and tolerance, by Benedict XVI, Cardinal Ratzinger as was An autobiography from the Jesuit underground, by William Weston SJ War (revised edition), by Gwynne Dyer From rick@unicode.org Thu Jul 7 19:19:47 2005 Received: with ECARTIS (v1.0.0; list hebrew); Thu, 07 Jul 2005 19:36:10 -0500 (CDT) Received: from izanami (ip-216-36-75-240.sjc.megapath.net [216.36.75.240]) by unicode.org (8.13.4/8.12.11) with SMTP id j680JZmV010037; Thu, 7 Jul 2005 19:19:35 -0500 Message-Id: <200507080019.j680JZmV010037@unicode.org> To: unicode@unicode.org Subject: [hebrew] Unicode Consortium releases UTR #36: Security Considerations Date: Thu, 7 Jul 2005 17:19:34 -0700 From: Rick McGowan received: by Apple.Mailer (2.95.2) X-archive-position: 2985 X-Approved-By: jcowan@reutershealth.com 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 2005-07-07. The Unicode Consortium announced today the release of the first version of UTR #36: Unicode Security Considerations: http://www.unicode.org/reports/tr36/ Because Unicode contains such a large number of characters and incorporates the varied writing systems of the world, incorrect usage can expose programs or systems to possible security attacks. This document describes some of the security considerations that programmers, system analysts, standards developers, and users should take into account, and provides specific recommendations to reduce the risk of problems. Regards, Rick McGowan Unicode, Inc.