From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roger Willcocks Subject: Re: [PATCH 07a/13] xfsprogs: add trie generator for UTF-8. Date: Tue, 23 Sep 2014 19:34:19 +0100 Message-ID: <1411497259.4842.163.camel@localhost.localdomain> References: <20140918195650.GI19952@sgi.com> <20140918203114.GN4482@sgi.com> <20140919160612.GF4482@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, tinguely@sgi.com, olaf@sgi.com, xfs@oss.sgi.com To: Ben Myers Return-path: In-Reply-To: <20140919160612.GF4482@sgi.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org On Fri, 2014-09-19 at 11:06 -0500, Ben Myers wrote: > +#define AGE_NAME "DerivedAge.txt" > +#define CCC_NAME "DerivedCombiningClass.txt" > +#define PROP_NAME "DerivedCoreProperties.txt" > +#define DATA_NAME "UnicodeData.txt" > +#define FOLD_NAME "CaseFolding.txt" > +#define NORM_NAME "NormalizationCorrections.txt" > +#define TEST_NAME "NormalizationTest.txt" Is there a reason why you're using multiple text-based data files (and hand-parsing them) when there's an xml formatted flat file available ? http://www.unicode.org/Public/UCD/latest/ucdxml/ And a 2nd question - why does the trie need to encode "the the unicode version in which the codepoint was assigned an interpretation" ? -- Roger Willcocks _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs