On Thu, 2009-01-15 at 15:36 +0100, Jan Hnatek wrote: > Sebastien Roy wrote: > > On Thu, 2009-01-15 at 02:08 -0500, Suresh Chandrasekharan wrote: > >> Project team is not aware of thunderbird/firefox/openoffice binaries > >> having a private copy of hunspell library. (They may be having hunspell > >> sources directly compiled in their executables). Even if they do > >> maintain private copies of the library, it's up to each of these teams > >> to decide if they would like to link to the hunspell library that this > >> case provides and forgo their private dependencies. > > > > Maybe so, but I'd suggest that it's your job as a responsible engineer > > to go talk to those project teams and at least make them aware that > > you're doing this work. Have you done that? > > You're correct and I received the following information from Jeff Cai: > "Currently Enchant included an internal copy of Hunspell 1.2.2 > so Enchant can use Hunspell spell checker as a back end. > After Hunspell goes into Solaris, the internal copy can be removed from > Enchant." > > The above mentioned applications use Enchant as a unified spell checking > interface. > I'll work with Jeff to have the Enchant's internal copy of Hunspell removed > once this project gets into Solaris.
This is an excellent result, thank you. -Seb
