[Added description of how to use the translator GUI and the API to the docs. bringert@cs.chalmers.se**20050509184222] { hunk ./doc/gf-java.html 120 -> pm -utf8 -printer=header | wf test.gfcm +> pm -utf8 -utf8id -printer=header | wf test.gfcm hunk ./doc/gf-java.html 122 -
-Note that you might get an error message saying that header is not -a valid value for the -printer flag. Ignore this message. This is -a bug in GF's error reporting which will be fixed. -
hunk ./doc/gf-java.html 128 -> pm -utf8 -printer=cfgm | wf test.cfgm +> pm -utf8 -utf8id -printer=cfgm | wf test.cfgm hunk ./doc/gf-java.html 130 --Note that you might get an error message saying that cfgm is not -a valid value for the -printer flag. Ignore this message. This is -a bug in GF's error reporting which will be fixed. -
hunk ./doc/gf-java.html 151 +The +build-translet +script will create a JAR-file which runs the translation GUI.
+ +To run the translation GUI on files you have +created manually, as in the description above, run:
+ ++$ java -cp gfc2java.jar:. se.chalmers.cs.gf.translategui.TranslateApp test.properties ++ +
Note that the current directory must be included in the classpath, +since properties file is loaded as a Java resource from the classpath.
+ ++Have a look at the +simple +demo program. Given the files created above, you can run the +program with:
+ ++$ java -cp gfc2java.jar:. se.chalmers.cs.gf.translategui.Test test.properties TestSwe TestEng ++ +
Note that the current directory must be included in the classpath, +since properties file is loaded as a Java resource from the classpath.
+ hunk ./doc/gf-java.html 217 -se.chalmers.cs.gf.parse.level=FINE -se.chalmers.cs.gf.linearize.level=FINE +se.chalmers.cs.gf.parse.level=FINEST +se.chalmers.cs.gf.linearize.level=FINEST hunk ./doc/gf-oaa.html 6 -hunk ./doc/gf-oaa.html 49 -