Difference: 0LASubrConvertTranslate (4 vs. 5)

Revision 52015-02-23 - AlKalter

Line: 1 to 1

META TOPICPARENT	name="APPXRuntimeSubroutineAPI"

.CONVERT TRANSLATE

Line: 38 to 37

Changed:

<
<

Text: One or more paragraphs
Clause: One or more words or phrases within a sentence
Token: A TOKEN field or an ALPHA field with table values consisting of a word or a phrase which requires an exact match with a Token entry in the dictionary.
Message: Text from the system MESSAGE file requires an exact match with a Message entry in the dictionary.
Field: One or more phrases and words.

>
>

Text:One or more paragraphs
Clause:One or more words or phrases within a sentence
Token:A TOKEN field or an ALPHA field with table values consisting of a word or a phrase which requires an exact match with a Token entry in the dictionary.
Message:Text from the system MESSAGE file requires an exact match with a Message entry in the dictionary.
Field:One or more phrases and words.

<trans_app_id> is the Application Id whose dictionaries should be used for the translation (Optional). Defaults to the current application if not PASSed, or is blank.

Line: 51 to 50

If <trans_text> is too small to contain the translated text, --- .CONVERT TRANSLATE will contain 'Data was truncated'.

Changed:

<
<

Note that this routine will return the <source_text> in the <trans_text> field if it is unable to translate <source_text>. In other word, you will always get something back from this routine, either the translated text, or as best a translation as possible. This is especially true if you are translating text which contain paragraphs or sentences. If the translation routine always starts with the largest block of text and works it's way down until it has attempted everything. If it can find a match for the enter block of text, it will return that. If not, it will then look for matches of the paragraphs in the text. If it can find a match for the paragraph, it will return that. If not, it will look for matches at the sentence level. If it still cannot find a match, it will attempt to translate individual words, depending on the "Translate Words" setting on the <from_lang> file. Thus the result returned could be a mix of the original text and the portions that were able to be translated.

>
>

Note that this routine will return the <source_text> in the <trans_text> field if it is unable to translate <source_text>. In other word, you will always get something back from this routine, either the translated text, or as best a translation as possible. This is especially true if you are translating text which contain paragraphs or sentences. The translation routine always starts with the largest block of text and works it's way down until it has attempted everything. If it can find a match for the enter block of text, it will return that. If not, it will then look for matches of the paragraphs in the text. If it can find a match for the paragraph, it will return that. If not, it will look for matches at the sentence level. If it still cannot find a match, it will attempt to translate individual words, depending on the "Translate Words" setting on the <from_lang> file. Thus the result returned could be a mix of the original text and the portions that were able to be translated.

Comments:

Read what other users have said about this page or add your own comments.

Changed:

<
<

It appears that the fields <trans_app_id> and <trans_ver_id> are indeed required, as it doesn't always seem to default properly to the currently running application/version.

>
>

It appears that the fields <trans_app_id> and <trans_ver_id> are indeed required, as it doesn't always seem to default properly to the currently running application/version.

-- AlKalter - 2014-10-01

<--/commentPlugin-->

View topic | History: r8 < r7 < r6 < r5 | More topic actions...