| Age | Commit message (Collapse) | Author |
|
Translation Demo'
Just as a quick way to test different documents in the Wide Coverage
Translation Demo.
|
|
|
|
variants and are now obsolete with the new partial evaluator
|
|
If the enumaration of table parameter values fails during the static
traversal phase, try again in the dynamic computation phase, when the values
of bound variables are known.
This is necessary to properly deal with generic table construction in opers,
like the ones found in prelude/Coordination.gf, e.g.
consTable : (P : PType) -> ... = \P ... -> {s1 = table P {...} ; ... }
|
|
|
|
GF.Compile.Optimize.mkLinReference can fail and cause this error because
the helper function inside it applies msum to a list that might be empty
(if there is a record type that does not contain a field of type Str).
This means that it can return mzero::Err, i.e.
Bad "error (no reason given)"
which can slip through the top level test that only catches Bad "no string".
|
|
Because the prompt included the name of the abstract syntax, the loading
of the PGF was forced even if -retain was used. Even worse,
if an error occured while loading the PGF, it was repeated and caught
every time the prompt was printed, creating an infite loop. The solution
is to not print the name of the abstract syntax when the grammar is
imported with -retain, which is the way things were before anyway.
|
|
The commands available in the shell after import -retain are now a superset
of the commands available after import without -retain.
The PGF is created lazily, so there should be no performance penalty if
the PGF isn't needed. If there are errors, they won't be reported until a
command that uses the PGF is entered.
|
|
Restrict the entire request handler instead of just the call to the C parser.
|
|
|
|
|
|
if their probability differ with less that 0.5
|
|
pasting text
|
|
word of a sentence
Keep the first letter in upper case if it is followed by more upper case
letters.
(Also remove some left over debugging output.)
|
|
|
|
with string literals
|
|
|
|
Currently Bul, Chi, Eng and Swe are marked as "fast" in the documentation.
|
|
|
|
|
|
Android app. Compiles and works on iPad retina but may crash and has known issues.
|
|
variables
|
|
|
|
This limit might still be to high to avoid excessive time/space use in the
parser for certain languages in the wide coverage translation grammar.
|
|
function to 4 by default
The limit can be changed with the -j flag
|
|
|
|
would gladly remove some code.
|
|
alignment API. This was causing problems on 64-bit machines
|
|
|
|
|
|
|
|
and Tha output
|
|
(and of course follow the target lang conventions)
|
|
|
|
With ghc-7.4 'import M hiding (x)' causes an error if M does not export x...
|
|
2 modules: Name clashes caused by Applicative-Monad change in Prelude
2 modules: Ambiguities caused by Foldable/Traversable in Prelude
2 modules: Backwards incompatible changes in time-1.5 for defaultTimeLocale
9 modules: {-# LANGUAGE FlexibleContexts #-} (because GHC checks inferred types
now, in addition to explicitly given type signatures)
Also silenced warnings about tab characters in source files.
|
|
|
|
+ Some additional simplifying rewrites.
+ Use an intermediate representation for Haskell types, for separation of
concerns and cleaner code.
+ Pretty printer layout tuning
+ Code cleanup.
|
|
Haskell code
Introduced an intermediate representation for the generated Haskell expressions.
This allows pretty printing concerns to be separated from conversion concerns,
and makes it easy to apply some simplifying rewrites to the generated
expressions, e.g.
[x] ++ [y] ==> [x,y]
pure f <*> x ==> f <$> x
f <$> pure x ==> pure (f x)
join (pure x) ==> x
|
|
|
|
By adding the flag -haskell=variants to the command line, GF will now generate
linearization functions in Haskell that support variants. Variants are
represented as lists in Haskell.
Variants inside pre { ... } expressions are still ignored.
TODO: apply some monad laws to generate more compact code (using an
intermediate representation of the generated Haskell code, instead of
pretty printing directly from the GF code).
|
|
|
|
|
|
Japanese uses the same lexer as Chinese, i.e. every character is a separate
token.
|
|
|
|
c-parse & c-translate web requests
|
|
|
|
|
|
|
|
|