Unique Functions -
Major Features -
Unicode and ANSI Applications
- Input in Unicode mode for Unicode
applications. Applications such as Microsoft Office 97/2000/XP Suite,
Notepad, and several others are Unicode conformant. An application is
Unicode conformant if it processes each character in double byte and it
recognizes fonts that are structured by Unicode TrueType font definition.
Many new versions of applications will be Unicode compatible.
- Supports Japanese EUC(JIS) and SJIS code
standards. Unicode input mode is not available for regular ANSI (Non-Unicode)
applications because they have not been modified to accommodate Unicode.
However, JPNT30 has provided backward compatibility so that almost all
applications can be processed in JIS and SJIS code modes.
- Unicode and non-Unicode fonts. Fonts are
provided in both Unicode and non-Unicode formats. The non-Unicode font
facename begins with Jpn such as Jpn Mincho S TT.
They are suitable for ANSI applications. The Unicode font facename begins
with TSC such as TSC JpnMincho S TT. They
are to be used in Unicode applications.
Selection of Internal Code
- User no longer needs to select internal
code for Japanese input. User starts an input session by confirming his or
her Language Preference. A button on the Japanese Partner Control Center
displays the status of EUC(JIS) or SJIS Japanese preference. JPNT3
automatically select the appropriate display and input code mode based on
language preference's selection and the current application type. The user
may leave the "Input Code Using" feature at default ("Auto Select").
- Overriding system selected internal code.
User can force the input code of a specific type differ from the auto
choice offered. The system lists the type of internal codes that are
logically available to the user based on the preference of using Japanese
language. Forcing Unicode is not advisable.
Cursor Word Processing
Single cursor word processing means cursor
movements on any character work the same way as English characters. That is,
the cursor will no longer walk into a character because of its double-byte
and non-split nature. This is a great convenience to our users. Single
cursor word processing may be enabled from either one of the following cases:
- When a character is processed in Unicode
mode. Under Unicode standard, all language character sets are defined in
double byte so the processing of each Unicode character is by nature
- When JPNT3 is capable of controlling the
cursor in non-Unicode mode. For applications that are not Unicode
compatible, each Japanese character normally would require double cursor
movements. However, we have implemented a special coding scheme, which
recognizes certain programming classes, and reduce the double cursor
requirement to single cursor. Not all applications can enjoy single cursor
processing because some of them employ special programming code that does
not communicate with external programs such as the Japanese Partner for