+The GF interpreter needs two representations of the grammar to do +linearization and parsing. These two representations can be generated +from a GF source grammar by using the +GF system. +This example assumes that we have the concrete syntax modules +TestEng and TestSwe. +
+ ++Load all the source modules into GF: +
++> i TestEng.gf +> i TestSwe.gf ++
+Create a GFCM file: +
++> pm -utf8 -printer=header | wf test.gfcm ++
+Create a CFGM file: +
++> pm -utf8 -printer=cfgm | wf test.cfgm ++
+Create a properties file (here test.properties) so that the interpreter can find +these files: +
++$ cat > test.properties <<PROP +name: test +gfcm: test.gfcm +cfgm: test.cfgm +PROP ++
See the +build-gramlet +script for an example of how to do this automatically.
+ hunk ./doc/gf-java.html 125 -is a demo applet which uses the Java GF -interpreter and the GF numerals +is a demo applet which uses the Java GF interpreter and the GF numerals hunk ./doc/gf-java.html 148 -Struct names are case-insensitive in OAA. This means that we cannot handle functions whose names differ only in case.
++Struct names are case-insensitive in OAA. This means that we cannot +handle functions whose names differ only in case. +
hunk ./test.html 16 ++The source code for the applet is included with the +Java +GF interpreter source code. +
+ }