From: ntakahas Date: Wed, 25 Jun 2003 12:02:40 +0000 (+0000) Subject: *** empty log message *** X-Git-Tag: XML-base~150 X-Git-Url: http://git.chise.org/gitweb/?a=commitdiff_plain;h=7d96e6d3446f65dd6e486cc348558459a7fe5386;p=m17n%2Fm17n-docs.git *** empty log message *** --- diff --git a/configure.ac b/configure.ac index 462d7d0..8a2a129 100644 --- a/configure.ac +++ b/configure.ac @@ -27,7 +27,7 @@ AC_SUBST(M17NLIB) AC_CHECK_PROG(HAVEDOXYGEN, doxygen, yes, no) AC_CHECK_PROG(RUBY, ruby, yes, no) -AC_CHECK_PROG(LATEX, platex, yes, no) +AC_CHECK_PROG(LATEX, latex, yes, no) AC_CHECK_PROG(PLATEX, platex, yes, no) OK=yes diff --git a/data-usr/dbformat.txt b/data-usr/dbformat.txt index 3a8ecc1..9ceee46 100644 --- a/data-usr/dbformat.txt +++ b/data-usr/dbformat.txt @@ -1,61 +1,74 @@ /***@page m17nDatabaseFormat DatabaseFormat -This section describes the formats of predefined @e plist @e type data -in the m17n database. +This section describes the data formats used in the m17n database. @section dbformat General format -The m17n library expects that the function mdatabase_load () returns a -plist of a specific format on loading data identified by a specific -set of tags. As the plist format used for the database data is -strongly limited, we can use the equivalent text of simple syntax -(S-expression) to represent the plist as below. - -The text consists of one or more @e elements . Each element -represents a property, i.e. a single element of a plist, and the -sequence of the elements constitute a plist. - -Elements are separated by one or more @e whitespaces, i.e. a space +The mdatabase_load () function receives a set of tags and returns the +contents of database in the form of plist. The keys of the returned +plist are limited to Minteger, Msymbol, +Mtext, and Mplist. The type of the value is +unambiguously determined by the corresponding key. If the key is +Minteger, the value is an integer. If the key is +Msymbol, the value is a symbol. And so on. + +A number of character representations are possible to represent a +plist. For instance, we can use the form (K1:V1, K2:V2, +... ,Kn:Vn) to represent a plist whose first property key and +value are K1 and V1, second key and value are K2 and V2, and so on. +However, we can use a simpler notation here because the types of +plists used in the m17n database are fairly restricted. + +Hereafter, we use a character representation, which is similar to +S-expression, to represent a plist. (Actually, the default database +loader of the m17n library is designed to read data files written in +this format.) + +The representation consists of one or more elements. Each +element represents a property, i.e. a single element of a plist. + +Elements are separated by one or more whitespaces, i.e. a space (code 32), a tab (code 9), or a newline (code 10). Comments begin with a semicolon (;) and extend to the end of the line. The key and the value of each property are determined based on the -form of element as below: +type of the element as explained below. EXAMPLE -Suppose (K1:V1, K2:V2, ... ,Kn:Vn) represents a plist whose first -property key and value are K1 and V1, second key and value are K2 and -V2, and so on. Then the line: +Here is an example of plist that is written in our S-expression like +representation. + @verbatim abc 123 (pqr 0xff) "m\"text" (_\\_ ("string" xyz) -456) @endverbatim -is interpreted as follows. + +It represents the following plist: + @verbatim (Msymbol:abc, Minteger:123, @@ -94,11 +108,6 @@ is interpreted as follows. Minteger:-456)) @endverbatim -The default database loader of the m17n library actually read a text -of this syntax from the database file. - -Here after we describes the plist format of each data by this syntax. - @section fontenc Font Encoding The m17n library loads information about the encoding of each font