Difference: 0LASubrConvertTranslate (2 vs. 3)

Revision 32012-02-10 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="APPXRuntimeSubroutineAPI"

.CONVERT TRANSLATE

Line: 24 to 24

This subroutine converts a string from one language to another. The first five parameters are required, if any are missing the subroutine will CANCEL. The <trans_type>, <trans_app_id> and <trans_ver_id> parameters are optional. The translation uses the Dictionaries and Translations you have entered in the applications. Note that this routine should be invoked via SUBR with a RELATED or DETACHED invocation to ensure none of your fields are changed.

Changed:

<
<

<trans_text> is the translated version of <source_text> (Required). This must be PASSed with Share "Y" to return the value.

>
>

<trans_text> returns the translated version of <source_text> (Required). This must be PASSed with Share "Y" to return the value.

Changed:

<
<

<trans_error> contains any addiitonal error messages from the translation (Required). This must be PASSed with Share "Y" to return the value.

>
>

<trans_error> returns any addiitonal error messages from the translation (Required). This must be PASSed with Share "Y" to return the value.

<source_text> is the text you want translated (Required).

Line: 42 to 43

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.

Changed:

<
<

>
>

<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.

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