module function · N/machineTranslation

translate()

machineTranslation.translate(options)

Translates a set of documents into the specified language.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
machineTranslation.translate(options)
Returns
Object
Governance
100
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2025.1
call shapefrom Oracle's parameter table
1machineTranslation.translate({2    documents: /* machineTranslation.Document [], required */,3    timeout:   /* number, optional */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.documentsmachineTranslation.Document []requiredThe documents to translate.
options.timeoutnumberoptionalThe timeout period to wait for a response from the translation service, in milliseconds. The default value is 30,000 (30 seconds).
B

No Mynt syntax yet.

Nothing in the language compiles to machineTranslation.translate(options) today. How should it read?

C

Competing syntax for translate, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

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, save and Ref[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?

N/machineTranslation · machineTranslation.translate(options)

Suggest syntax for translate