summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authoraarne <unknown>2005-04-10 15:57:33 +0000
committeraarne <unknown>2005-04-10 15:57:33 +0000
commitdc0ec11e282c094c9b98aad5c8fc98c8dc492508 (patch)
tree9dfdf421fccb7c6f126507947f7d23a91c56f08a /doc
parent792fea08bd18c4757930f55f7067e2ec9b5d4a57 (diff)
just module rules missing
Diffstat (limited to 'doc')
-rw-r--r--doc/gf-modules.html14
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/gf-modules.html b/doc/gf-modules.html
index 0a085ac49..ce6a5b41f 100644
--- a/doc/gf-modules.html
+++ b/doc/gf-modules.html
@@ -749,11 +749,23 @@ times. Here is a summary of how they are compiled:
</ul>
This means that some generated code is duplicated, because those operations that
do have complete definitions in an <tt>interface</tt> are copied to each of
-the <tt>instances</tt>
+the <tt>instances</tt>.
<h3>Transfer modules</h3>
+<b>Translation by transfer</b> means that syntax trees are manipulated
+by non-compositional functions (<b>transfer rules</b>) between the
+source and target languages. They are being introduce to GF as a module
+type of its own, but their development is still in progress. What
+will be available are <i>at least</i> <tt>fun</tt> and <tt>def</tt>
+judgements, but more is needed. It has not yet been defined how
+transfer modules are integrated in multilingual grammars, i.e.\
+where in the grammar it is specified what transfer to use.
+(Both GF and GFC have a syntax for transfer modules and
+multilingual headers, but their compilation further than parsing
+has not been implemented.)
+
<h2>Summary of module syntax and semantics</h2>