module function · N/machineTranslation
createDocument()
machineTranslation.createDocument(options)
Creates a document to be used as source content when calling the translation service.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1machineTranslation.createDocument({2 id: /* string, required */,3 text: /* string, required */,4 language: /* string, optional */5});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.id | string | required | The ID of the document. |
| options.text | string | required | The text of the document. |
| options.language | string | optional | The language of the document. Use values from the machineTranslation.Language enum to set the value of this parameter. If you don't specify the document language, the translation service detects the language automatically when you pass the document to machineTranslation.translate(options) . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to machineTranslation.createDocument(options) today. How should it read?
C
community proposals
Competing syntax for createDocument, from GitHub Discussions. Select two or more to compare them side by side.
Loading proposals from GitHub…
D
suggest an alternative
Write the Mynt you wish you could write.
A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.
- Clarity. Does it say what happens, without ceremony?
- Consistency. Does it read like
load,saveandRef[field]? - Expressiveness. Does it cover the cases people actually write?
- Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?