Contenues dansTrouver plus de documentationRessources d'assistance comprises | Télécharger cet ouvrage au format PDF (1010 Ko)
Part III System Administrator InformationThis part includes system administration information. Chapter 8 Configuring a Korean Solaris SystemYou can use the procedures this chapter to set a system-wide default locale or to add a new locale from the Solaris DVD and CD media. You also change the font path set by the Xsession script included in the Korean Solaris Operating System. The following sections are included in this chapter. Setting the Default LocaleYou can use the procedure in this section to make a system-wide change to the default locale. How to Set the Default Locale
Using Aliases to Set the LocaleYou can use aliases to change a terminal-emulation window between the Korean locales and ASCII/English locale without typing long command lines or editing your .dtlogin file and running source every time. How to Set Locale Aliases for the Korn ShellPut aliases such as the following in your .profile file.
How to Set Locale Aliases for the C ShellPut aliases such as the following in your .cshrc file.
Chapter 9 Managing the htt Input Method ServerThe input method server (IM Server) handles Korean input for Korean Solaris software. The IM Server receives keyboard input and makes the input available as Korean characters to Korean Solaris system applications. The IM Server can serve any internationalized X Window application that uses the X Windows Input Method (XIM) application program interfaces (API) to receive language input. This following sections in this chapter explain the basic display features of the IM Server. Input Method Server Basic PropertiesThe Korean Solaris Operating System starts the IM Server automatically when you log in to a locale that requires an input method. The Korean Solaris applications that use the IM Server for Korean character input typically find the IM Server running when the applications starts. To connect to the IM Server for language input, the IM Server should be running before the application starts. If the IM Server is not running before the application starts, the application might not be able to connect to the input service. Even if the IM Server starts later, the application might not be able to connect to the input service. Three htt ProcessesThe input method server comprises three related programs. The htt, htt_server, and htt_xbe, processes are run together. One process controls the properties of the input method server. A watch dog process controls the population of the input method server and a third process handles the input methods of clients. Usually, you don't need to know the details of these three processes. When htt starts, the htt_props and htt_server start also. htt Application DisplayThe following figure shows a typical application display when the htt input method is in use.
How and When htt is StartedAny application that uses the IM server to receive Korean characters must find htt running before the server can receive Korean character input. If the default locale is C, which does not require htt, and you change from C to another locale in a single Terminal, for example, you must start htt with a command line like the following:
With the locale set to ko_KR.EUC, htt starts automatically when the Korean windowing environment is started. In CDE, htt is started from a script, /usr/dt/config/Xsession.d/0020.dtims. The script is executed by Xsession, which runs at every initialization stage when you log in from dtlogin. The script ensures that htt is started before other applications in CDE. Using the iiim Server in the ko_KR.UTF-8 LocalesThe Internet Intranet Input Method Server (iiim) supports the European Local Input Methods that use the Compose key. The iiim server also supports the Asian Remote Input Methods that use IIIM Protocol. The default Language Engine is English/European which supports ASCII and some European Languages such as German and French. To switch to Korean Input Methods, press Control-spacebar. To switch to other language engines, click the left mouse button in the Status Area. The following language engine list appears.
The following language engines appear if the corresponding locales are installed:
For more information about how to use Korean input methods, see Chapter 4, Entering Korean Text. Chapter 10 FontsThe following sections in this chapter describe how to use and edit the Korean Solaris fonts. This chapter also describes how to convert BDF font files to Portable Compiled Format (PCF) format and how to make the fonts usable on your system. Display PostScript System (DPS)The Korean Solaris Operating System provides PostScript fonts in the Display PostScript System (DPS). This section describes what you need to use DPS in Korean Solaris software. For further details, see Programming the Display PostScript System with X, published by Adobe Systems. Using Korean PostScript Fonts and DPS FacilitiesThe Korean Solaris Operating System DPS provides the fonts listed in the following table. Table 10–1 Korean Solaris Operating System DPS Fonts
You can use the following Korean fonts just as you would use Roman fonts.
The following figure shows a sample of Kodig-Medium and Myeongjo-Medium text. ![]() ![]() You can also use the following Korean fonts for pure Hangul between the SO and SI characters with no intermediate ASCII (0x20) characters.
Creating Composite Korean FontsYou can create composite fonts using one Roman font and one of the following Korean fonts.
For example, the following PostScript code defines a sample composite font. The ASCII characters of the Times-Italic+Kodig-Medium font are combined with the Korean characters of the Kodig-Medium horizontal font.
Using Korean Fonts in DPS ProgrammingYou can use Korean fonts just as you use Roman fonts in DPS wrap definitions. This sample code creates the display which follows.
You can set PSWDisplayText in a C program to display the designated Korean text.
BDF and PCF FormatsYou must convert BDF fonts to PCF format to make the fonts usable in Korean Solaris applications. How to Convert BDF Fonts to PCF FormatUse the bdftopcf command to convert a BDF font to PCF format.
The -o option enables the matrix encoding used for Asian PCF font files. How to Install and Check an Edited Font
Changing Font DirectoriesThe Xsession script in /usr/dt/bin directory of the Korean Solaris Operating System includes the following font path: /usr/openwin/lib/locale/locale/X11/fonts, where locale is either ko or ko.UTF-8. To dynamically add a different font directory path, type the following commands:
Bitmap and TrueType FontsThe tables in this section list the bitmap and TrueType fonts that are supported for the ko, the ko.UTF-8, and the ko/ko.UTF-8 locales. The following table shows the Korean bitmap fonts for the ko locale. Table 10–2 Korean Bitmap Fonts for the ko Locale
The following table shows the Korean bitmap fonts for the ko.UTF-8 locale. Table 10–3 Korean Bitmap Fonts for the ko.UTF-8 Locale
The following table shows the Korean TrueType Fonts for the ko/ko.UTF-8 locales. Table 10–4 Korean TrueType Fonts for the ko/ko.UTF-8 Locales
Chapter 11 Korean Printing FacilitiesThis chapter includes the following sections: Printing Korean Output to a Line PrinterYou can use the commands in this section to print files of different formats to a line printer. Use this command to print an EUC file.
Use this command to print a Packed format file to a printer that supports Packed format.
Use this command to print a Johap format file to a printer that supports Johap format.
Use commands such as the following to print a ko.UTF-8 file to an EUC printer. The first command line converts the file to an EUC format. The second line prints the file.
Note – The printed output includes only the characters that are defined in the EUC code set. Use commands such as the following to print a ko.UTF-8 file to a Johap (KS C 5601-1992) printer. The first command line converts the file to a Johap format. The second line prints the file.
Note – The printed output includes only the characters that are defined in the Johap code set. Using the mp UtilityThe enhanced mp print utility is available in the current Korean Solaris release. You can use mp to print ko files in ko locale or UTF-8 files in ko.UTF-8 locales. The output from the utility is standard PostScript that you can send to any PostScript printer. Use the following command to print a file with the mp utility.
You can also use the utility as a filter because mp accepts stdin stream.
You can set the utility as a print filter for a line printer. For example, the following command sequence signals the print service that the printer lp1 accepts only mp format files. The command also installs the printer lp1 on port /dev/ttya. See the lpadmin(1M) man page for more details.
You can use the following command to add a filter for an LP print service.
The filter converts the default input type to PostScript output with the /usr/bin/mp command. To print a UTF-8 text file, use a command line such as the following.
For more details on the mp(1), see the man page. Using mp as an Xprt (X Print Server) ClientUsing mp as an Xprt client enables mp to print the output of any printer connected to a network supported by an Xprt print service. As an Xprt client, mp supports PostScript and many versions of PCL. The Xprt client attempts a connection to an Xprt server based on the following rules:
Chapter 12 TTY Environment and SupportThis chapter assumes that you are familiar with the following information.
This chapter includes the following sections: Refer to the termio(7I) man page for background information on STREAMS and TTY drivers. TTY STREAMSThe data path between a user's shell and the terminal is called a stream. The data on a stream contain characters and control information that affect data handling, such as the control sequences that precede a change in code set or communication protocols. Data that enters the stream from the terminal is raw or unprocessed. Data is sequentially processed by STREAMS modules for appropriate use by the shell or an application. STREAMS provides a way to modularize the processing on a line, allowing processing instructions to be grouped in functional modules. These modules can be added or removed from the line so that different environments can be provided to a terminal according to the user's needs. Traditional STREAMSThe traditional STREAMS TTY environment contains a raw device driver, a line discipline module, and a stream head. The raw device driver provides an I/O interface between the kernel and the hardware. Because it is closest to the physical hardware, it provides basic communication protocols, baud rate switching, and other low level services. The line discipline module is a set of instructions or disciplines that transforms the raw data to processed data. This includes handling the delete character, line kill character, and others. The stream head provides an interface between the user's process and the stream. Korean Solaris STREAMSThe Korean Solaris Operating System uses the modular nature of STREAMS to support Korean. In addition to the traditional TTY modules, this product implements code conversion in STREAMS. Hangul-Hanja conversion is typically supplied by many existing Korean TTYs and is not available in the Korean Solaris TTY environment. The Korean Solaris Operating System enhances the traditional modules. The line discipline of the operating system handles proper cursor movement for wide characters as well as normal protocols. The Korean Solaris code conversion modules convert between two different character code formats. For example, Packed format, combination code of KS C 5601-1987, can be converted to EUC format, completion code. Code conversion depends on the appropriate flags or parameters being set. For example, if a Packed code terminal is being used, the input from the terminal is converted to EUC and the output to the terminal is converted to Packed code. The major modules that can be pushed onto the stream are ldterm, kpack and kjohap.
TTY Utilitiesioctl (input/output control) calls are low-level routines for handling device input and output. The termcap and terminfo databases are used by applications to configure their terminal display appropriately. EUC ioctl FeaturesThe Korean Solaris Operating System uses ioctl STREAMS commands for general EUC handling. The table describes the ioctl requests. Table 12–1 ioctl Requests and Descriptions
Character code conversion to and from the terminal is controlled by EUC_OXLON and EUC_OXLOFF. The termcap databaseThe termcap and terminfo databases used to tailor the terminal characteristics for an application. The following table describes the variables of the termcap database. Table 12–2 termcap Variables and Descriptions
The terminfo databaseThe following are extensions to terminfo. The s0-s3 string values are used as data announcement mechanisms for the respective code sets during terminal I/O. Table 12–3 terminfo Variables and Definitions
TTY CommandsThe two commands for configuring and using the TTY environment are setterm and /bin/stty. setterm is used primarily to build the TTY stream for a particular terminal type, pushing the necessary modules onto the stream. stty changes the behavior of the modules in the stream. setterm Commandsetterm is used to configure the TTY STREAMS environment. It can inquire about and manipulate STREAMS modules for a particular TTY port. setterm allows users to tailor their TTY STREAMS environment using system-provided or user-provided STREAMS modules. setterm uses a terminal device name that reflects the devt (device type) field in the terminfo database for configuring STREAMS modules for a TTY port. This device name is matched with an entry of the same name in the setterm configuration file, /usr/share/lib/setterm/ko/conf.file or /usr/share/lib/setterm/ko.UTF-8/conf.file. This entry contains detailed instructions on which modules to pop and push in order to properly configure the STREAMS environment. setterm can also take the device type as a direct argument. This device type is similarly matched with an entry in /usr/share/lib/setterm/ko/conf.file or /usr/share/lib/setterm/ko.UTF-8/conf.file. The setterm configuration file uses a special language for instructions on what actions to take. This language allows users to determine the names of modules on the STREAMS stack, to push or pop modules on the stack, and to do other operations. setterm manipulates the STREAMS stack by making ioctl calls. /bin/stty CommandThe defeucw option to the /bin/stty command is for modifying STREAMS modules to reflect changes in the user's environment. It does not work with the /usr/ucb version of stty, which has not been internationalized. The following command queries the user's environment for information on EUC code set width and sets.
For example, if the user has the environment variable LC_CTYPE set to locale, this option gets information on the number of bytes per character and the screen width per character for the code sets in the ko and ko.UTF-8 environments and then sends this information to relevant modules in the stream. TTY Setup ExamplesThe system administrator can add setterm in the startup script in /etc/rcn.d directory (where n is the run level), to run at the system boot time. Also, users can run the setterm command at login to configure the stream for their terminal, including the appropriate modules for Korean input code conversion. The following examples using setterm work as commands typed at a system prompt or included in system files such as .cshrc, .login, and the startup script. Such commands can either explicitly set the device type or use the terminfo database. Configuring STREAMS for Korean Solaris SoftwareYou can use the commands in this section to configure STREAMS modules. Use the following command to explicitly configure the STREAMS module for the EUC, completion code, terminal type.
Use the following command to explicitly initialize the Packed STREAMS module that supports the combination code of KS C 5601-1987.
Use the following command to explicitly initialize the Johap STREAMS module that supports a combination code of KS C 5601-1992.
Use this procedure to run a configuration command that references an entry in the terminfo database.
For setterm to work properly, the /usr/share/lib/setterm/ko/conf.file must contain an entry that corresponds to the device type. This entry gives setterm instructions for placing the appropriate conversion modules in the TTY stream. Add the following entry that corresponds to the device type to the /usr/share/lib/setterm/ko/conf.file.
Configuring STREAMS for the ko.UTF-8 LocaleYou can use the commands in this section to configure STREAMS modules the ko.UTF-8 Locale. Use the following command to explicitly configure the STREAMS module for the ko.UTF-8 locale.
Use the following command to explicitly initialize an EUC terminal to use the ko.UTF-8 locale
Use the following command to explicitly initialize the Johap STREAMS module. This module supports combination code of the KS C 5601-1992 terminal to use the ko.UTF-8 locale.
Use this procedure to run a configuration command that references an entry in the terminfo database.
For setterm to work properly, the /usr/share/lib/setterm/ko.UTF-8/conf.file must contain an entry that corresponds to the device type. This entry gives setterm instructions for placing the appropriate conversion modules in the TTY stream. Add the following entry that corresponds to the device type to the /usr/share/lib/setterm/ko.UTF-8/conf.file.
Terminal SupportThe Korean Solaris Operating System supports completion-code terminals and Packed-code terminals. The terminals should have built-in automata, Hangul/Hanja fonts, and Hangul/Hanja input methods. Note – Packed code is also called combination code, KS C 5601-1987 and KS C 5601-1992. Installing a TerminalIf you have not added a terminal to your system before, first try installing a terminal in ASCII mode only. How to Install a Terminal to Support KS C 5601
How to Set Up a ttya Port from the Command LineUse the following procedure to set up a terminal on ttya port from the command line.
How to Verify TTY Set UpUse the following procedure to verify that the TTY is properly set up.
This is the last step in setting up a terminal. The default setting of a Korean terminal is the completion-code mode. Continue to the next section to install a Packed-code TTY. How to Use Packed Code and Johap TTY in the ko LocaleIf you use a Packed code (KS C 5601-1987) terminal , you must load the kpack STREAMS module into the kernel.
How to Use Combination Code and Johap TTY in the ko LocaleIf you use a combination code (KS C 5601-1992) terminal , you must load the kjohap STREAMS module into the kernel.
How to Use the EUC TTY in the ko.UTF-8 LocaleIf you use an EUC (KS C 5601-1987-0) terminal , you must load the ku8euc STREAMS module into the kernel.
How to Use the Johap TTY in the ko.UTF-8 LocaleIf you use a Johap (KS C 5601-1992-3) code terminal , load the ku8johap STREAMS module into the kernel.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||