*** empty log message ***

[m17n/m17n-docs.git] / data-usr / dbformat.txt

diff --git a/data-usr/dbformat.txt b/data-usr/dbformat.txt
index f94397f..770202b 100644 (file)
--- a/data-usr/dbformat.txt
+++ b/data-usr/dbformat.txt
@@ -14,7 +14,7 @@ unambiguously determined by the corresponding key.  If the key is
 
 A number of expressions are possible to represent a
 plist.  For instance, we can use the form <tt>(K1:V1, K2:V2,
-... ,Kn:Vn)</tt> to represent a plist whose first property key and
+..., Kn:Vn)</tt> 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 expression here because the types of
 plists used in the m17n database are fairly restricted.
@@ -52,7 +52,7 @@ For instance, the element <tt>0xA0</tt> represents a property whose value is
 
 An element that matches the regular expression
 <tt>[^-0-9(]([^\\()]|\\.)+</tt> represents a property whose key is
-<tt> Msymbol</tt>.  In the element, <tt>\\t</tt> , <tt>\\n</tt>,
+<tt> Msymbol</tt>.  In the element, <tt>\\t</tt>, <tt>\\n</tt>,
 <tt>\\r</tt>, and <tt>\\e</tt> are replaced with tab (code 9), newline
 (code 10), carriage return (code 13), and escape (code 27)
 respectively.  Other characters following a backslash is interpreted
@@ -116,7 +116,7 @@ format of the data is as follows:
 
 @verbatim
 FONT-ENCODING ::=
-    '(' PER-FONT-INFO * ')'
+    PER-FONT-INFO *
 
 PER-FONT-INFO ::=
     '(' FONT-SPEC ENCODING ')'
@@ -153,7 +153,7 @@ resize\>.  The plist format of the data is as follows:
 
 @verbatim
 FONT-RESIZE ::=
-    '(' PER-FONT-INFO * ')'
+    PER-FONT-INFO *
 
 PER-FONT-INFO ::=
     '(' FONT-SPEC RESIZE-RATIO ')'
@@ -184,7 +184,7 @@ as follows:
 
 @verbatim
 FONTSET ::=
-    '(' PER-SCRIPT + ')'
+    PER-SCRIPT +
 
 PER-SCRIPT ::=
     '(' SCRIPT PER-LANGUAGE + ')'
@@ -228,17 +228,17 @@ three fonts.
 
 @section flt Font Layout Table
 
-Usually, the rendering engine converts character codes of a text into
-glyph codes one by one by consulting information about encoding of
-each selected font.  But, for rendering a text that requires
-complicated layouting (e.g. Thai and Indic), such an one to one
-conversion is not sufficient.  In addition, some glyphs must be
-shifted 2-dimensionally on the screen.  For such a case, a font layout
-table (FLT in short) must be used.
-
-A FLT can contain all the information in OpenType Layout Table (CMAP,
-GSUB, and GPOS) in addition to the information about how to extract a
-grapheme cluster and how to re-order characters.
+Usually, the rendering engine converts character codes of into glyph
+codes one by one by consulting information about encoding of each
+selected font.  But, for rendering a text that requires complicated
+layouting (e.g. Thai and Indic), such an one to one conversion is not
+sufficient.  In addition, some glyphs must be shifted 2-dimensionally
+on the screen.  For such a case, a font layout table (FLT in short)
+must be used.
+
+A FLT can contain the information equivarent to OpenType Layout Table
+(CMAP, GSUB, and GPOS) in addition to the information about how to
+extract a grapheme cluster and how to re-order characters.
 
 The m17n library loads a FLT from the m17n database by the tags
 \<font, layouter, FLT-NAME\>.  The plist format of the data is as