Intro_jfp(1) (JFP Reference Manual 1 : User Commands)

JFP Reference Manual 1 : User Commands

Intro_jfp(1)

NAME

Intro_jfp, intro_jfp- introduction to JFP commands and application programs

AVAILABILITY

This section indicates which package contains the commands being described on this page. To be able to use the command, the indicated package must have been installed with the operating system. For information on how to add a package see pkgadd(1).

DESCRIPTION

This section describes, in alphabetical order, JFP commands available with this operating system.

OTHER SECTIONS

See these sections of the JFP Reference Manual for more information.

Section 1M in this manual for JFP system maintenance commands.
Section 4 of this manual for information on JFP file formats.
Section 5 of this manual for descriptions of publicly available JFP files and miscellaneous information pages.

Manual Page Command Syntax

Unless otherwise noted, commands described in the SYNOPSIS section of a manual page accept options and other arguments according to the following syntax and should be interpreted as explained below.

name [–option...] [cmdarg...] where:

[ ]: Surround an option or cmdarg that is not required.
...: Indicates multiple occurrences of the option or cmdarg.
name: The name of an executable file.
{ }: The options and/or arguments enclosed within braces are interdependent, such that everything enclosed must be treated as a unit.
option: (Always preceded by a ``–''.) noargletter... or, argletter optarg[,...]
noargletter: A single letter representing an option without an option-argument. Note that more than one noargletter option can be grouped after one ``–'' (Rule 5, below).
argletter: A single letter representing an option requiring an option-argument.
optarg: An option-argument (character string) satisfying a preceding argletter. Note that groups of optargs following an argletter must be separated by commas, or separated by a tab or space character and quoted (Rule 8, below).
cmdarg: Path name (or other command argument) not beginning with ``–'', or ``–'' by itself indicating the standard input.

Command Syntax Standard: Rules

These command syntax rules are not followed by all current commands, but all new commands will obey them. getopts(1) should be used by all shell procedures to parse positional parameters and to check for legal options. It supports Rules 3-10 below. The enforcement of the other rules must be done by the command itself.

Command names (name above) must be between two and nine characters long.
Command names must include only lower-case letters and digits.
Option names (option above) must be one character long.
All options must be preceded by ``–''.
Options with no arguments may be grouped after a single ``–''.
The first option-argument (optarg above) following an option must be preceded by a tab or space character.
Option-arguments cannot be optional.
Groups of option-arguments following an option must either be separated by commas or separated by tab or space character and quoted (–o xxx,z,yy or –o "xxx z yy").
All options must precede operands (cmdarg above) on the command line.
``––'' may be used to indicate the end of the options.
The order of the options relative to one another should not matter.
The relative order of the operands (cmdarg above) may affect their significance in ways determined by the command with which they appear.
``–'' preceded and followed by a space character should only be used to mean standard input.

ATTRIBUTES

See attributes(5) for a discussion of the attributes listed in this section.

DIAGNOSTICS

Upon termination, each command returns two bytes of status, one supplied by the system and giving the cause for termination, and (in the case of ``normal'' termination) one supplied by the program [see exit(2)]. The former byte is 0 for normal termination; the latter is customarily 0 for successful execution and non-zero to indicate troubles such as erroneous parameters, or bad or inaccessible data. It is called variously ``exit code'', ``exit status'', or ``return code'', and is described only where special conventions are involved.

WARNINGS

Some commands produce unexpected results when processing files containing null characters. These commands often treat text input lines as strings and therefore become confused upon encountering a null character (the string terminator) within a line.

LIST OF COMMANDS

Name: Description
Intro_jfp(1): introduction to JFP commands and application programs
atok12(1): ATOK12 Japanese language input system
atok12migd(1): Merges an ATOK8 dictionary to ATOK12 dictionary
atok12migs(1): Migrates the style setting from ATOK8 to ATOK12
atok12setup(1): Set up ATOK12 for Japanese input in X environment
cs00toatok(1): conversion cs00 user dictionary to ATOK user dictionary
euctoibmj(1): Code conversion between Japanese EUC and IBM-Japanese
euctojis(1): See jistoeuc(1)
euctosj(1): See jistoeuc(1)
evftobdf(1): convert evfont file to BDF format
ibmjtoeuc(1): See euctoibmj(1)
jistoeuc(1): Code conversion between JIS, PC kanji, and Japanese EUC
jistosj(1): See jistoeuc(1)
jpostprint(1): PostScript translator for Japanese text files
jprconv(1): Filter for printing Japanese text on a dot-matrix Kanji printer or Japanese language page printer
jtops(1): postscript filter for printing Japanese characters on Sun Laser Writer or Japanese postscript printer
jtty(1): set Japanese terminal characteristics
kanji(1): show the list of Kanji codes
kkcvtocs00(1): conversion from kkcv user dictionary to cs00 user directory
sdtudctool(1): Solaris gaiji tool
sdtudc_convert(1): User defined character conversion utility
sdtudc_extract(1): User defined character conversion utility
sdtudc_extract_ps(1): User defined character conversion utility
sdtudc_register(1): Intermediate utility to register user-defined characters
sjtoeuc(1): See jistoeuc(1)
sjtojis(1): See jistoeuc(1)
uum(1): Kana-Kanji conversion front end processor
Wnn6(1): Wnn6 Japanese language input system
wnn6setup(1): Set up Wnn6 for Japanese input in X environment
wnnatod(1): Convert an EUC text dictionary to a binary dictionary
wnnbushu(1): Wnn6 radical input utility
wnndictutil(1): Dictionary utility
wnndtoa(1): Convert a binary dictionary to an EUC text dictionary
wnnenvutil(1): Environment setting utility
wnnotow(1): User dictionary converter
wnnstat(1): Print the status of Wnn6 Kana-Kanji conversion server
wnntouch(1): Rewrite and format the file header according to the inode.
xjsi(1): Wnn6 Kana-Kanji conversion server/htt interface module

SunOS 5.9 Last Revised 10 Dec 1999