content.txt

Emdros is a text database middleware-layer aimed at storage and retrieval of "text plus information

<page_anchor ID="2000">configuration file</page_anchor> <index
term="configuration file"></P>

<p>equivalent <page_anchor id="1130">toolbar</page_anchor> button:
<img src="connect.png" alt="Connect">.</p>


<h2>Commit</h2>

<P>The "Commit" menu item saves the chunking-changes made in the program,
by committing them to the database.</P>

<p>equivalent <page_anchor id="1130">toolbar</page_anchor> button:
<img src="commit.png" alt="Commit">.</p>


<h2>Exit</h2>

<P>The "Exit" menu item quits the program.</P>

<P>Equivalent <page_anchor ID="1130">toolbar</page_anchor> button:
None.</P>

</page>



<page ID="1150">

<h2>Split</h2>

<P>The "Split" menu item splits the current chunk right before the
currently selected box.</P>

<P>Equivalent <page_anchor ID="1130">toolbar</page_anchor> button:
<IMG SRC="flash.png" ALT="Split">.</P>

<h2>Combine</h2>

<P>The "Combine" menu item combines the chunk containing the currently
selected box with the previous chunk.</P>

<P>Equivalent <page_anchor ID="1130">toolbar</page_anchor> button:
<IMG SRC="together.png" ALT="Combine">.</P>

<h2>Move left</h2>

<P>The "Move left" menu item moves the chunk containing the currently
selected box one tab-stop to the left.</P>

<P>Equivalent <page_anchor ID="1130">toolbar</page_anchor> button:
<IMG SRC="leftarrow.png" ALT="Move left">.</P>


<h2>Move right</h2>

<P>The "Move right" menu item moves the chunk containing the currently
selected box one tab-stop to the right.</P>

<P>Equivalent <page_anchor ID="1130">toolbar</page_anchor> button:
<IMG SRC="rightarrow.png" ALT="Move right">.</P>



</page>



<page ID="1155">

<h2>Configure...</h2>

<P>This menu-item has not been implemented yet.  Sorry.</P>



</page>



<page ID="1160">

<h2>Help Contents...</h2>

<P>This brings up this help document.</P>


<h2>About Emdros Chunking Tool...</h2>

<P>This brings up the "About box".  Press "OK" to dismiss it
again.</P>

<P>Equivalent <page_anchor ID="1130">toolbar</page_anchor> button:
None.</P>



</page>



<page ID="1300">

<P>The chunking area is middle of the program window.  It is this area
that is the place for interacting with the program.</P>

<P>Once a database connection has been loaded, you will see some text
in this window.  The text is divided into clickable (and thus
selectable) boxes.</P>

<P>You can use the "split" <IMG SRC="flash.png" ALT="Split"> and
"combine" <IMG SRC="together.png" ALT="Combine"> buttons to split or
combine the text into "chunks", each on its own line.</P>

<P>These chunks can then be indented with respect to each other with
the "Move left" <IMG SRC="leftarrow.png" ALT="Move left"> and "Move
right" <IMG SRC="rightarrow.png" ALT="Move right"> buttons.</P>

<h2>Example</h2>

<P>In the image below, you can see an example database that has been
chunked and indented.</P>

<P><IMG SRC="MainScreenGreekExample.png" ALT="Example with Greek"></P>

</page>


<page ID="2000">

<h2></h2>

<h2>Format of the configuration file</h2>

<P>The configuration file follows many other Unix and Windows
configuration files in that:</P>

<UL> 

<LI>Comments are prefixed by #, and anything from the # to the end of
  the line is ignored.  

<LI>Blank lines are ignored. 

<LI>The rest is a number of "key = value" pairs.  

<LI>The keys are pre-defined (see below).  

<LI>The values are either "quote-enclosed strings" (e.g.,
  "C:\Emdros\mymap.map") or consist of letters, numbers, underscores,
  and/or dots, optionally followed by a "quote-enclosed string" (e.g.,
  'word.surface', or 'word.surface."C:\Documents and
  Settings\Administrator\teckitmap.map"').

</UL>

<P>When a value has dots that are not enclosed in "quotes", then the
strings on either side of the dots are interpreted as subkeys.  For
example, the value "word.surface" represents the subkey "word" with
the value "surface", and the value
"word.surface."/home/myname/Blah.map" represents the subkey "word"
with the subsubkey "surface", followed by the value
"/home/myname/Blah.map".</P>



<P>Here is a sample configuration file, explained bit by bit:</P>

<h3>Database selection</h3>
<PRE class="code">
{PREHASH} database
database = mydb
</PRE><!-- widthincm : 12 -->

<P>You can specify a database that is always to be used with this
configuration file.</P>

<P>If using SQLite, you may wish to specify a path.  Do so in
quotes:</P>

<PRE class="code">
{PREHASH} database
{PREHASH} Put the database name in quotes.
{PREHASH} For SQLite 2 and SQLite 3, you should probably give
{PREHASH} the full path to the file as well.

database = "C:{PREBACKSLASH}Program Files{PREBACKSLASH}Emdros{PREBACKSLASH}Emdros-1.2.0.pre228{PREBACKSLASH}db{PREBACKSLASH}mydb"
</PRE><!-- widthincm : 12 -->

<h3>Data unit</h3>

<PRE class="code">
{PREHASH} data unit
{PREHASH} There can only be one data unit
{PREHASH} but it can have as many data{PREUNDERSCORE}features as you like.
{PREHASH} Each data{PREUNDERSCORE}feature will go on its own interlinear line.
{PREHASH} 

data{PREUNDERSCORE}unit            = word
data{PREUNDERSCORE}feature         = graphical{PREUNDERSCORE}word
data{PREUNDERSCORE}feature         = graphical{PREUNDERSCORE}lexeme
</PRE><!-- widthincm : 14 -->

<P>The data unit is the basic unit that will result in one box in the
chunking area.  They can be any object type, and need not be words.
However, probably you want them to be words or word-like objects.  It
depends on how large segments you want to be able to chunk at a
time.</P>

<P>You must specify which feature(s) to display for the data unit.</P>

<P>There can only be one data unit.</P>


<h3>TECkit mappings</h3>

<PRE class="code">
{PREHASH} TECKit
{PREHASH}
{PREHASH} data{PREUNDERSCORE}feature{PREUNDERSCORE}teckit{PREUNDERSCORE}mapping defines what TECkit map to use
{PREHASH} for a given data{PREUNDERSCORE}feature.
{PREHASH}
{PREHASH} data{PREUNDERSCORE}feature{PREUNDERSCORE}teckit{PREUNDERSCORE}in{PREUNDERSCORE}encoding specifies the in{PREUNDERSCORE}encoding ("bytes" 
{PREHASH} or "unicode") for the given data{PREUNDERSCORE}feature.
{PREHASH}
{PREHASH} data{PREUNDERSCORE}feature{PREUNDERSCORE}teckit{PREUNDERSCORE}out{PREUNDERSCORE}encoding specifies the out{PREUNDERSCORE}encoding ("bytes"
{PREHASH} or "unicode") for the given data{PREUNDERSCORE}feature.
{PREHASH} 
data{PREUNDERSCORE}feature{PREUNDERSCORE}teckit{PREUNDERSCORE}mapping      = graphical{PREUNDERSCORE}word."Amsterdam.map"
data{PREUNDERSCORE}feature{PREUNDERSCORE}teckit{PREUNDERSCORE}in{PREUNDERSCORE}encoding  = graphical{PREUNDERSCORE}word.bytes
data{PREUNDERSCORE}feature{PREUNDERSCORE}teckit{PREUNDERSCORE}out{PREUNDERSCORE}encoding = graphical{PREUNDERSCORE}word.unicode
</PRE><!-- widthincm : 14 -->

<P><strong>TECkit</strong> is a tool made by SIL International.  It
converts between encodings, in particular to and from Unicode.  The
Emdros Chunking Tool incorporates TECkit, and you can apply it to any
textual feature of any object type.</P>

<P>TECkit works with a so-called "map file" -- a text file which you
or someone else writes.  More information about writing TECkit
mappings can be found on SIL's website:</P>

<center><P><strong>http://scripts.sil.org/TECkit/</strong></P></center>

<P>The Emdros Chunking Tool needs three pieces of information in
order for TECkit to work on a particular feature:</P>

<OL> 

  <LI>The name of the file which holds the maping.  This is given
      with the key "data_feature_teckit_mapping".

  <LI>The input encoding (encoding of the feature-string): This is
      given with the key "data_feature_teckit_in_encoding".  The value
      can be either "bytes" or "unicode" (without the quotes).
      "bytes" means that TECkit does not convert to UTF-8.  "unicode"
      means it is converted to UTF-8 for display.  You should use
      whatever is used in the map file for input encoding here.

  <LI>The output encoding (encoding to transform into): This is given
      with the key "data_feature_teckit_out_encoding".  The same
      meanings and restrictions apply as for the input encoding.

</OL>

<P>TECkit can not only convert between encodings, but also remove
stuff from a string.  This can come in handy when you have characters
in your feature-strings which you do not wish to display.  Again, see
the TECkit site on SIL's website for information on how to write a
TECkit mapping.</P>

<P>You should give first the object type, then a dot, then the
feature-name, then a dot, then the full path to the map file.  You
probably need to enclose the path in "double quotes".</P>

<P>You can only have one TECkit per feature.</P>


<h3>Options</h3>

<PRE class="code">
{PREHASH} Options
{PREHASH}
{PREHASH} The only option available is 'right{PREUNDERSCORE}to{PREUNDERSCORE}left', which, if set,
{PREHASH} will cause the chunking area to run right to left rather than
{PREHASH} left to right.
option = right{PREUNDERSCORE}to{PREUNDERSCORE}left
</PRE><!-- widthincm : 14 -->


<h3>Display options</h3>

<PRE class="code">
{PREHASH} Fonts -- chunking area font names.
{PREHASH} If you give more than one chunking{PREUNDERSCORE}area{PREUNDERSCORE}font{PREUNDERSCORE}name,
{PREHASH} they will be assigned to individual data{PREUNDERSCORE}feature interlinear
{PREHASH} lines, in the same order as the data{PREUNDERSCORE}feature keys appear.
{PREHASH}
{PREHASH} If you give less keys here than you have data{PREUNDERSCORE}feature keys,
{PREHASH} then the last one will be used for the ones that aren't assigned
{PREHASH} an explicit value.
{PREHASH}
{PREHASH} If you give no values for this key, then some sensible default
{PREHASH} font will be used.
{PREHASH}
chunking{PREUNDERSCORE}area{PREUNDERSCORE}font{PREUNDERSCORE}name = "Ezra SIL"
chunking{PREUNDERSCORE}area{PREUNDERSCORE}font{PREUNDERSCORE}name = "Courier"
chunking{PREUNDERSCORE}area{PREUNDERSCORE}font{PREUNDERSCORE}name = "Ezra SIL"

{PREHASH}
{PREHASH} The magnification (in percent) of the chunking area.
{PREHASH} 100 corresponds approximately to a font size of 12 points.
{PREHASH}
chunking{PREUNDERSCORE}area{PREUNDERSCORE}magnification  = 120
</PRE><!-- widthincm : 14 -->

</page>