From owner-soc-status@FreeBSD.ORG Fri Jun 20 01:47:45 2014 Return-Path: Delivered-To: soc-status@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DC927773; Fri, 20 Jun 2014 01:47:45 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C14F214D; Fri, 20 Jun 2014 01:47:44 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id mc6so1973996lab.13 for ; Thu, 19 Jun 2014 18:47:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:date:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=5vUVydsT67k2LW7ENBNIT+5ftogK3ilWTMTTgV3RhF8=; b=KVm10xumsPj+O0BIBfVnXlf0Va/ZkcodQXJdDUGBcX8RsSC6U4VZtaKtRnk6KDrI4b 5YuK5HS1hbkJLWMtTvvQ391bVTrNpT1Kqg4cVQ0xj1dZXVdcdbR5C4wQEqE9nF9lcJxr vCgyhPldITFiwq1HhPAr5HAxp/yr6nf1GYnBcYew2edofnwBcGbhBR+JddtqFRGf8x3h iigHievOx/pHc48+OVqjLiHoWJ90NBuE7coSSxmN4lxCe5JJa5JUItbsbSwjlb34xa6c llnNEMdN3RlQCA+b1G36XlIfGWFOkrm/35t8i5+MdAqTPePni7IPknKgERfYSeAycdVp pYtA== X-Received: by 10.152.20.71 with SMTP id l7mr159080lae.4.1403228862854; Thu, 19 Jun 2014 18:47:42 -0700 (PDT) Received: from openSUSE.linux ([176.100.246.237]) by mx.google.com with ESMTPSA id b3sm5419667lbi.15.2014.06.19.18.47.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Jun 2014 18:47:42 -0700 (PDT) From: Dmitry Selyutin X-Google-Original-From: Dmitry Selyutin Message-ID: <53A3929E.6080006@gmail.com> Date: Fri, 20 Jun 2014 05:47:10 +0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: soc-status@FreeBSD.org, Pedro Giffuni , David Chisnall Subject: Report #2: Unicode support X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2014 01:47:45 -0000 Hello everyone! I'm glad to tell that we made a progress in the implementation of the Unicode Normalization Algorithm, which is required before string collation. I've recently implemented its composition form, so we can move to NFD and NFKD parts, which are certainly more difficult. It was really difficult to understand how to preprocess Unicode Database files to receive a some working form of data to work with; I've tried to ask for help in ICU mailing lists, but have received no answer yet, so I had to work on my own. However, I'm already sure that I can implement NFD and NFKD without help from them, though I'd appreciate any help from people who know Unicode world better. However, I'm almost sure that I'll finish NFD and NFKD till Monday. I could have done it even on Saturday, but unfortunately I also have to solve some bureaucratic issues in my University. I need to provide several medical documents, that means that I needed to spent the entire two days to visit all doctors and make them sure that I'm healthy to graduate. :-) Sounds strange, but unfortunately that really requires a lot of time in Russia. I'll need to finish these issues on Monday, but I hope that I'll be free since that time. So the plan is to implement the NFD and NFKD till Monday, then test it using a file from Unicode Database, then move to collation part. Still looking for people who knows the Unicode Standard (except of ICU people; as I said, I've written them a letter already, so I hope to receive an answer yet). As usually, I'd like to thank my mentors, especially Pedro, who had a patience during this week while seeing my style issues. Pedro, I didn't forget about style issues; I'll get to correct it all when I'll implement the NFD and NFKD, since during active work it's sometimes difficult to keep code clean. :-) Thanks to everyone who read this letter! -- With best regards, Dmitry Selyutin