Functions | |
void | Compute_Text_From_Text16 (int incount, const unsigned short *intext16, const char *encoding, char *outtext) |
Converts from string to integer-array representations of 16-bit characters. More... | |
void | Compute_Text16_From_Text (const char *intext, const char *encoding, int *outcount, unsigned short *outtext16) |
Converts from integer-array representations of 16-bit characters to string representations. More... | |
void Compute_Text16_From_Text | ( | const char * | intext, |
const char * | encoding, | ||
int * | outcount, | ||
unsigned short * | outtext16 | ||
) |
Converts from integer-array representations of 16-bit characters to string representations.
intext | - The characters in packed-byte format. |
encoding | - Any of the encoding constants described under Insert_Text() . |
outcount | - The number of characters unpacked into outtext16. Passed by reference always. Returned to user. |
outtext16 | - The characters in full 16-bit format, one per short element after unpacking. Passed by reference always. Returned to user. |
No additional details. See Compute_Text_From_Text16()
void Compute_Text_From_Text16 | ( | int | incount, |
const unsigned short * | intext16, | ||
const char * | encoding, | ||
char * | outtext | ||
) |
Converts from string to integer-array representations of 16-bit characters.
incount | - Number of characters in intext16. |
intext16 | - An array of 16-bit integers. Each integer represents one short character. |
encoding | - Any of the encoding constants described under Insert_Text() . |
outtext | - The characters from "intext16", in packed byte format. Passed by reference always. Returned to user. |
HOOPS routines such as Insert_Text_With_Encoding() and Show_String_With_Encoding() expect their input and output to be in a "packed byte" format described under Insert_Text() . It's more convenient, however, for your program to do its text work with the text packed exactly one character per 16-bit word. Compute_Text_From_Text16() and Compute_Text16_From_Text() make this conversion for you.
The Compute_XXX() routines that require information about display drivers, do not work if they are called from an included segment. Display information must be associated with a window to return information about the display.
Calling Compute_XXX() routines to obtain data associated with a display generates an update. On most devices, this poses no problem. However, for hardcopy devices such as Postscript or CGM, this can generate a blank page. To avoid this problem, applications often open a temporary driver subsegment, call the compute routine, retain the computed information, and then discard the temporary driver subsegment.