Talk:Firefox/Projects/FTS and Awesomebar

--Jmdesp 15:29, 19 March 2010 (UTC) Drew, did you try to open any public discussion on this topic ? I don't find a bug where it would be possible to discuss the implementation strategy ? There will indeed be much reticence to import a good part of ICU just for that.

In bug 7969 for thai line breaking, the ICU approach had been rejected already. The platform specific i18n methods used instead are much more compact.

nsUniscribeBreaker.cpp does word breaking detection based on the uniscribe API, nsCarbonBreaker.cpp does the same based on ATSUI/Carbon, finally nsPangoBreaker.cpp does the same under Linux.

So, you should aime to reuse the approach used there instead of what you are thinking of currently.