| Age | Commit message (Collapse) | Author |
|---|
|
|
|
but much faster
|
|
|
|
the app!
|
|
|
|
The minibar lets the user choose any category as the start category, but this
can lead to run-time errors for grammars compiled with -optimize-pgf.
The problem can also be observed in the GF shell. For example,
"linearize Fish" (which means that the start category is Kind) fails for
some languages when Foods.pgf is compiled with -optimize-pgf.
|
|
|
|
|
|
|
|
|
|
compiles now. But Japanese has no support for chunks, because ChunkFunctor does not typecheck for it due to its richer Utt type.
|
|
|
|
|
|
|
|
|
|
|
|
Quant are missing in each language"
|
|
|
|
|
|
|
|
investigate here.
|
|
|
|
completions.
|
|
|
|
|
|
|
|
|
|
loss of speed than VPSlash-valued original rules.
|
|
increase translation quality. This comes with 30% longer translation time with my benchmark but should still be OK.
|
|
PhrasebookChi
|
|
yet)
This makefile just calls GF once and lets GF figure out in which order to
compile things. It uses the -j flag to enable parallel compilation and
specifies an explicit -path, overriding the -path flags in the source files.
This allows all needed modules to be found automatically and ensures that
that alltenses is consistently used everywhere. But for some reason, this
doesn't work...
|
|
to the top level; the resulting rule is the same. This kind of inefficiencies are best found if you compile with the -v option and check for constructors creating unexpectedly many PGF rules.
|
|
low-quality version and is hence the first Chinese phrasebook version that can claim high quality.
|
|
indirect questions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
changes that were not reflected
|
|
|
|
|
|
|
|
clash with Construction.Language in App
|
|
known
|
|
|
|
|
|
|
