| Age | Commit message (Collapse) | Author |
|
Unlike the other web apps in the cloud, the translation quiz was configured
to use the grammars at http://www.grammaticalframework.org/grammars.
|
|
|
|
|
|
|
|
This had been bugging me for ages!
|
|
|
|
|
|
|
|
|
|
collectPattOp :: (Patt -> [a]) -> Patt -> [a]
|
|
collection for the chart
|
|
For Patt, analogous to composOp for Term.
|
|
Also add a missing check for Predef values in apply.
|
|
Just to make them easier to spot when wading through thousands of lines of
warnings...
|
|
|
|
Also improve the documentation of the responses to the upload and make
commands.
|
|
grammars
Also remove some old commented out code.
|
|
|
|
Simplify the implementation of writeUTF8File and use it in one more place.
Remove unused imports left over after a previous change.
|
|
apps
Aarne says the Chinese resource grammar is complete, but not yet completely
correct.
|
|
There was 55 lines of rather repetitive code with calls to 6 compiler passes.
They have been replaced with 19 lines that call the 6 compiler passes
plus 26 lines of helper functions.
|
|
compiler passes
|
|
|
|
|
|
|
|
... to avoid unnecessary recompilation of other modules.
|
|
Also fixed two small problems with public grammars.
|
|
|
|
|
|
This helps avoiding problems if an inherited grammar is renamed, or if there
is more than one grammar with the same name.
|
|
The output from commands is represented as ([Expr],String), where the [Expr] is
used when data is piped between commands and the String is used for the final
output. The String can represent the same list of trees as the [Expr] and/or
contain diagnostic information.
Sometimes the data that is piped between commands is not a list of trees, but
e.g. a string or a list of strings. In those cases, functions like fromStrings
and toStrings are used to encode the data as a [Expr].
This patch introduces a newtype for CommandOutput and collects the functions
dealing with command output in one place to make it clearer what is going on.
It also makes it easier to change to a more direct representation of piped
data, and make pipes more "type safe", if desired.
|
|
|
|
GF tutorial
|
|
|
|
|
|
|
|
Avoid showing a blank page if there is an unexpected problem with the grammars
in localStorage.
|
|
This enables the use of arbitrary Unicode character in text mode in GFSE.
|
|
- Alternative variants in AScared.
- The order of adv. modifiers: first time, then place (PSeeYouPlaceDate).
- Fixed: the object valence in QWhatAge; Day.point linearization.
- PSeeYouPlaceDate is now less formal.
- Open/Closed and SeeYou functions are ok now, except that the word order in Open/Closed is a bit clumsy. TODO: "<what> <when> is open/closed" (currently not supported by the RG).
|
|
alternatives (paraphrases)
Fixed QWhatName, QWhatAge, HowMuchCost and ItCost, however, the solutions have to be reviewed.
Introduced a Lav-specific type for Language (affected also NPNationality etc.) to support a different realization of ASpeak.
Introduced alternative realizations for AHasName and ASpeak (the most typical/simple variant is the default one).
|
|
Moved similar low-level code blocks in Main and GFI for setting the console
encoding to the new module GF.System.Console.
|
|
To make the popup menus accessible, use a simple trick to activate the
simulate-hovering-by-tapping behaviour.
|
|
"Edit/Add a segment..." stopped working at some point.
(Importing text still worked.)
|
|
|
|
the row view
Functional programming is easier than imperative programming!
|
|
|
|
When adding a new function, you can enter a linearization for one language
and then copy it to the other languages with one button click.
|
|
|
|
|
|
UTF-8
...to avoid complaints from HTML validators and potential problems in browsers
with different default character encodings.
|