This looks great to me.
> On Apr 15, 2016, at 7:04 AM, kellen sunderland <[email protected]> > wrote: > > Yes we’re using Joshua as a library and will be sharing some more code soon > (hopefully tomorrow) that should help a little for this. I think it might > make sense to come up with a simple v0.1 API that we could start using to > call Joshua in an interoperable manner. > > > A simple API could look like this: > > > StructuredTranslation translate(String source); > > > Where StructuredTranslation contains the translated string, but also some > information about how it got the translations (n-best lists, etc). > > > -Kellen > > > > > On 4/12/16, 5:09 PM, "Matt Post" <[email protected]> wrote: > > > Hi Tommaso, > > > There isn't really, unfortunately. I have never used Joshua as a library; > it would be nice if the Amazon folks (who I infer have done so, from a > comment on their last commit) would contribute a doc on this front. > > > What is the preferred avenue for developer documentation? Javadocs, or > something else? > > > matt > > > > On Apr 12, 2016, at 6:09 AM, Tommaso Teofili <[email protected]> > wrote: > > > Hi all, > > > I am going through the code (so I'll probably figure it out at some point), > > however I wonder if there's a quick guide on how to start using Joshua > > programmatically as I am start having a look at how it could be integrated > > into other projects. > > > Regards, > > Tommaso
