On 3/12/07, David Huynh <[EMAIL PROTECTED]> wrote: > Hi all, > > With Ryan's help, Babel is now back up! > > There are a few updates to Babel: > > [...] > > - It now supports translation through HTTP GET, not just HTTP POST. > http://simile.mit.edu/wiki/Babel/How_to_call_translator_using_HTTP_GET > > - There is JSONP output, documented in that wiki page (maybe Johan's > importer framework can take advantage of that).
Cool; that sounds interesting. > [...] &mime-type=output-mime-type [...] > > [...] > > output-mime-type can be anything you want. It is entirely optional. That doesn't quite seem to work; misdocumented? I fail to override the application/json(p) output of writers exhibit-json(p): http://simile.mit.edu/babel/translator?reader=bibtex&writer=exhibit-jsonp&mime-type=text/plain&url=http%3A//www.la.dlr.de/cgi-bin/bibtex2.pl%3Ftyp%3Dg%26optauthor%3Deins%26author%3D%26optbook%3Deins%26booktitle%3D%26opttitle%3Deins%26title%3D%26year1%3D1990%26year2%3D2006%26ausgabe%3Dbibtex%26num%3D1%26Suchen%3DSuchen%26.cgifields%3Dyear1%26.cgifields%3Doptbook%26.cgifields%3Dnum%26.cgifields%3Dyear2%26.cgifields%3Dtyp%26.cgifields%3Doptauthor%26.cgifields%3Dausgabe%26.cgifields%3Dopttitle > You can change callback to your own function name by adding another URL > parameter called out-callback. Could I please request that to accept the callback URL parameter named just "callback" (, too, if you'd like to keep out-callback for clarity)? It's what is considered standard JSONP practice, and interoperates better with Exhibit, for instance (in that you don't have to bother with the callback parameter on your own at all then). -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
