Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

JSON string supported is much more cool #15

Closed
tianliang0123 opened this issue Apr 14, 2015 · 1 comment
Closed

JSON string supported is much more cool #15

tianliang0123 opened this issue Apr 14, 2015 · 1 comment

Comments

@tianliang0123
Copy link

I am not sure the use of the schema in the screenshot below:
translatetype
Sometimes the XML and JSON files will be translated, i am not sure whether the function is wanting to allow different types of input files to be translated. if so, very cool. What I mean is that the toolkit can allow us to perform multiple translations within a single call through using JSON object. Exactly the same JSON object will be returned back but with translated values.
@ales-t
Copy link
Member

ales-t commented Apr 14, 2015

The parameters docType and profileType are reserved for future use. The plan is to switch between systems optimized to translate different types of text (e.g. short queries vs. documents) or targeted for different kinds of users. For now they have no effect.

@ales-t ales-t closed this as completed Apr 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ales-t @tianliang0123