Hi Haris, Thanks for the feedback. We will certainly look into improving our documentation.
But to answer your question, For {slug} in TM, its a unique string value which is used for a specific collection of imported TM, e.g. "Id" field for when admin create the tm collection. As for Json file format support, can you please file a request in https://zanata.atlassian.net/. We generally use that as our backlog for all requests and bug tracker. --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Wed, May 11, 2016 at 10:53 PM, Haris Alijagić <haris.alija...@halcom.si> wrote: > Hi, > > Could you improve the documentation for Zanata rest API a bit? Mainly this > part translation Memory > <https://zanata.ci.cloudbees.com/job/zanata-api-site/site/zanata-common-api/rest-api-docs/resource_TranslationMemoryResource.html> > is giving me a bit of an issue… For example how should the {slug} > parameter look like? An example would be nice. Also right now it only > accepts and sends responses in XML.. it would be nice if you could make it > so that it can accept and return a json response as well, like with the > other resources J. > > > > _______________________________________________ > zanata-users mailing list > zanata-users@redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users >
_______________________________________________ zanata-users mailing list zanata-users@redhat.com https://www.redhat.com/mailman/listinfo/zanata-users