On Dec 17, 2010, at 10:33 PM, Michael Schade wrote: > On Fri, Dec 17, 2010 at 10:09 PM, Peter Hosey <bore...@adium.im> wrote: >> What if the plug-in simply invoked the Service? The Service would remain >> available for use in all applications, and the plug-in would enable >> automatic use of it in Adium. > > Slick idea, I like it! > >>> - The Services menu cannot be dynamically populated, so we are unable to >>> send updated lists of languages and would have to hard code them all. > > Nice, but OS X isn't going to be able to detect our languages, > especially not on short strings. Our list of 100+ languages is at > http://accentuate.us/languages if interested. > > I can, however, hard code the languages into the Service and it won't > be a horrible setup that way. Our languages list probably won't change > too frequently--the important bit is that we can still update the > models on our end to improve accuracy. > > I still have some work to do on the OS X Service. Mainly, adding a > feedback item (so people can correct accents if incorrectly placed, > send the corrected text back to us, and we can use it as additional > training data) and hard coding the languages. > > Would you be able to do a plug-in to call the Service once I get it > going better? You'd be much more familiar with the Adium source than > myself and I still have that scheduling problem :) > > Thanks a ton for your help!
The LaTeX plugin might be a very useful starting point for such a plugin; as I recall, it utilized the Equation Service to perform a similar substitution. The plugin will probably require some changes to compile against current adium source - it hasn't had an active maintainer in some time. The fundamentals should be intact, though. Cheers, Evan
