Using the SCOadmin internationalization facility

Message file format

The format of the .msg file is similar to a standard message catalog source file. mkcatdecl(1) processes the .msg files. The format of the .msg files is defined by the following rules:

Multiple message source files are not supported. There must be a one to one correspondence between .msg file and target file.
A ``$ '' (dollar-space) starting in column one is a comment.
Blank lines are ignored.
A new message set for a module is defined with the $moduleset declaration. All messages following this declaration up to the next $moduleset will belong to the message set associated with this module:
```
   $moduleset MODULE C=C-DECL Tcl=TCL-DECL
```
MODULE
module id

C-DECL
base name of the C/C++ declaration and external file to generate. The declaration file will have .msgd.h append to the name and the external file will have .msg.h append to the name. If this file is to go in another directory, the path should be specified relative to the directory containing the .msg file. This keyword and value are omitted if no C declaration is to be generated.

TCL-DECL
base name of the Tcl declaration file to generate. The declaration file will have .msg.tcl append to the name. If this file is to go in another directory, the path should be specified relative to the directory containing the .msg file. This keyword and value are omitted if no C declaration is to be generated.
A message is defined by a line starting with a symbolic message number and a quoted default string (separated by one or more white-space characters). Currently the only quote character supported is double quote ("). The quote character may be included in the line by escaping it with a backslash (\). All back-slashed characters are passed to gencat unchanged.

NOTE: There must be a one-to-one mapping between module ids and message catalog/message set pair. That is, messages associated with a given module ID are found in only one message set of one message catalog. Multiple modules may share a single message catalog. The module ID is used to determine the message catalog and message set number. The message set number is never used directly by the client programs, only the internationalization and error managers. All messages are referenced in the programs by the module ID and the message number.

``Sample message catalog'' is an example of a .msg file conforming to these standards.

Sample message catalog

$ food.msg - Sample message catalog for software that does something $ with food. $ %\Z% %\M% %\I% %\E% %\Q%

$moduleset SCO_PIZZA C=../pizza/pizza Tcl=../pizza/pizza

SCO_PIZZA_MSG_TOGO "A pizza with %1$s to go." SCO_PIZZA_MSG_FORHERE "A pizza with %1$s for here." SCO_PIZZA_ERR_UNKNOWN_TOPPING "We don't sell %1$s topping"

$moduleset SCO_SALAD Tcl=../salad/salad.msg.tcl

SCO_SALAD_MSG_HEALTH "Salad is better for you than pizza" SCO_SALAD_MSG_ATTITUDE "More great software is written on pizza than salad"