cg3
cg3 copied to clipboard
GrammarSoft
Tools for the 3rd edition of the Constraint Grammar formalism.
There's no reason VAR can't support `
Enhance `MOVE` to take multiple contextual targets and move them into place based on a pattern.
Could be `T` and would resolve to `+` or `-` depending on where target is.
Should not parse: - `SELECT SUB:1:haberde Vblex ...` - `LIST (@SPRED) = @ ...`
Disallow unescaped set operators ever being tags, which would enable grouping with () to distinguish from inline sets.
Since commit a9c767573edaefb0d59c2c9d93fbf1048d5c92a3, tags are not printed unless tracing is enabled. However, since CG is now used in many Apertium pairs during generation to handle preferences, tags may be necessary...
CG-3's memory use when parsing huge corpora tends to increase infinitely, but haven't ever been able to detect any leaks. Pretty sure it's because the corpus has a lot of...
A way to tell sections how many that particular one should be run.
A way to designate which relation prefixes are unique, so that AddRelation won't add more than 1 of each kind from cohorts.
Metadata
Owner
Metadata
Tools for the 3rd edition of the Constraint Grammar formalism.