@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class TerminologyData extends Object implements Serializable, Cloneable, StructuredPojo
The data associated with the custom terminology. For information about the custom terminology file, see Creating a Custom Terminology.
Constructor and Description |
---|
TerminologyData() |
Modifier and Type | Method and Description |
---|---|
TerminologyData |
clone() |
boolean |
equals(Object obj) |
String |
getDirectionality()
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or
multiple (multi-directional).
|
ByteBuffer |
getFile()
The file containing the custom terminology data.
|
String |
getFormat()
The data format of the custom terminology.
|
int |
hashCode() |
void |
marshall(ProtocolMarshaller protocolMarshaller)
Marshalls this structured data using the given
ProtocolMarshaller . |
void |
setDirectionality(String directionality)
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or
multiple (multi-directional).
|
void |
setFile(ByteBuffer file)
The file containing the custom terminology data.
|
void |
setFormat(String format)
The data format of the custom terminology.
|
String |
toString()
Returns a string representation of this object.
|
TerminologyData |
withDirectionality(Directionality directionality)
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or
multiple (multi-directional).
|
TerminologyData |
withDirectionality(String directionality)
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or
multiple (multi-directional).
|
TerminologyData |
withFile(ByteBuffer file)
The file containing the custom terminology data.
|
TerminologyData |
withFormat(String format)
The data format of the custom terminology.
|
TerminologyData |
withFormat(TerminologyDataFormat format)
The data format of the custom terminology.
|
public void setFile(ByteBuffer file)
The file containing the custom terminology data. Your version of the AWS SDK performs a Base64-encoding on this field before sending a request to the AWS service. Users of the SDK should not perform Base64-encoding themselves.
The AWS SDK for Java performs a Base64 encoding on this field before sending this request to the AWS service. Users of the SDK should not perform Base64 encoding on this field.
Warning: ByteBuffers returned by the SDK are mutable. Changes to the content or position of the byte buffer will be seen by all objects that have a reference to this object. It is recommended to call ByteBuffer.duplicate() or ByteBuffer.asReadOnlyBuffer() before using or reading from the buffer. This behavior will be changed in a future major version of the SDK.
file
- The file containing the custom terminology data. Your version of the AWS SDK performs a Base64-encoding on
this field before sending a request to the AWS service. Users of the SDK should not perform
Base64-encoding themselves.public ByteBuffer getFile()
The file containing the custom terminology data. Your version of the AWS SDK performs a Base64-encoding on this field before sending a request to the AWS service. Users of the SDK should not perform Base64-encoding themselves.
ByteBuffer
s are stateful. Calling their get
methods changes their position
. We recommend
using ByteBuffer.asReadOnlyBuffer()
to create a read-only view of the buffer with an independent
position
, and calling get
methods on this rather than directly on the returned ByteBuffer
.
Doing so will ensure that anyone else using the ByteBuffer
will not be affected by changes to the
position
.
public TerminologyData withFile(ByteBuffer file)
The file containing the custom terminology data. Your version of the AWS SDK performs a Base64-encoding on this field before sending a request to the AWS service. Users of the SDK should not perform Base64-encoding themselves.
The AWS SDK for Java performs a Base64 encoding on this field before sending this request to the AWS service. Users of the SDK should not perform Base64 encoding on this field.
Warning: ByteBuffers returned by the SDK are mutable. Changes to the content or position of the byte buffer will be seen by all objects that have a reference to this object. It is recommended to call ByteBuffer.duplicate() or ByteBuffer.asReadOnlyBuffer() before using or reading from the buffer. This behavior will be changed in a future major version of the SDK.
file
- The file containing the custom terminology data. Your version of the AWS SDK performs a Base64-encoding on
this field before sending a request to the AWS service. Users of the SDK should not perform
Base64-encoding themselves.public void setFormat(String format)
The data format of the custom terminology.
format
- The data format of the custom terminology.TerminologyDataFormat
public String getFormat()
The data format of the custom terminology.
TerminologyDataFormat
public TerminologyData withFormat(String format)
The data format of the custom terminology.
format
- The data format of the custom terminology.TerminologyDataFormat
public TerminologyData withFormat(TerminologyDataFormat format)
The data format of the custom terminology.
format
- The data format of the custom terminology.TerminologyDataFormat
public void setDirectionality(String directionality)
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
directionality
- The directionality of your terminology resource indicates whether it has one source language
(uni-directional) or multiple (multi-directional).
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
Directionality
public String getDirectionality()
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
Directionality
public TerminologyData withDirectionality(String directionality)
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
directionality
- The directionality of your terminology resource indicates whether it has one source language
(uni-directional) or multiple (multi-directional).
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
Directionality
public TerminologyData withDirectionality(Directionality directionality)
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
directionality
- The directionality of your terminology resource indicates whether it has one source language
(uni-directional) or multiple (multi-directional).
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
Directionality
public String toString()
toString
in class Object
Object.toString()
public TerminologyData clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojo
ProtocolMarshaller
.marshall
in interface StructuredPojo
protocolMarshaller
- Implementation of ProtocolMarshaller
used to marshall this object's data.