Simon, You asked about relevance. The UTF-8 to UTF-16 bottleneck is widely cited in literature on XML processing performance.
For example, in SAX processing, Psaila finds that transcoding takes > 50% of XML processing time. Giuseppe Psaila, "On the problem of coupling Java Algorithms and XML Parsers 17th Int. Conf on Database Systems and Applications, 2006. > > I downloaded the source, but I agree with your concerns and will not > look further. Note that the OSL 3.0 license contains discussion about > patents, and give us some rights to the patented technology. It is > not clear to me whether the author intended this. > > I have to wonder where this technology would be relevant. Converting > between UTF-8 and UTF-16 is a very quick operation even if implemented > fairly poorly. Does anyone know where this operation is a serious > bottleneck worth optimizing? I'd like to see such analysis. > Remember, "premature optimization is the root of all evil"... > > /Simon > > -- > Linux-UTF8: i18n of Linux on all levels > Archive: http://mail.nl.linux.org/linux-utf8/ -- Robert D. Cameron, Ph.D. Professor of Computing Science Simon Fraser University -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
