Idiom: idiomatic phrases such as existentials
-
Infrastructure modules
Expressions of each phrase category are constructed in the corresponding
@@ -142,7 +93,6 @@ can skip the lincat definition of a category and use the default
{s : Str} until you need to change it to something else. In
English, for instance, many categories do have this linearization type.
Lexical modules
What is lexical and what is syntactic is not as clearcut in GF as in @@ -179,7 +129,6 @@ different languages on the level of a resource grammar. In other words, application grammars are likely to use the resource in different ways for different languages.
-The core of the syntax
Among all categories and functions, a handful are @@ -204,7 +153,6 @@ rules relate the categories to each other. It is intended to be a first approximation when designing the parameter system of a new language.
-Another reduced API
If you want to experiment with a small subset of the resource API first, @@ -213,7 +161,6 @@ try out the module explained in the GF Tutorial.
-The present-tense fragment
Some lines in the resource library are suffixed with the comment @@ -229,9 +176,7 @@ implementation. To compile a grammar with present-tense-only, use i -preproc=GF/lib/resource-1.0/mkPresent LangGer.gf
-Phases of the work
-Putting up a directory
Unless you are writing an instance of a parametrized implementation
@@ -317,7 +262,6 @@ as e.g. VerbGer.
Direction of work
The real work starts now. There are many ways to proceed, the main ones being @@ -416,7 +360,6 @@ and dependences there are in your language, and you can now produce very much in the order you please. -
The develop-test cycle
The following develop-test cycle will @@ -473,7 +416,6 @@ follow soon. (You will found out that these explanations involve a rational reconstruction of the live process! Among other things, the API was changed during the actual process to make it more intuitive.)
-Resource modules used
These modules will be written by you. @@ -492,8 +434,9 @@ package.
ParamX: parameter types used in many languages -CommonX: implementation of the categories $Text$ and $Phr$, as well as of - the logical tense, anteriority, and polarity parameters +CommonX: implementation of language-uniform categories + such as $Text$ and $Phr$, as well as of + the logical tense, anteriority, and polarity parametersCoordination: operations to deal with lists and coordinationPrelude: general-purpose operations on strings, records, truth values, etc. @@ -529,7 +472,6 @@ almost everything. This led in practice to the duplication of almost all code on thelinandoperlevels, and made the code hard to understand and maintain. -Morphology and lexicon
The paradigms needed to implement @@ -600,7 +542,6 @@ These constants are defined in terms of parameter types and constructors in
-ResGerandMorphoGer, which modules are not visible to the application grammarian.Lock fields
An important difference between
MorphoGerand @@ -611,8 +552,8 @@ record types in a resource modules, such asParadigmsGer, a lock field is added to the record, so that categories with the same implementation are not confused with each other. (This is inspired by thenewtypediscipline in Haskell.) -For instance, the lincats of adverbs and conjunctions may be the same -inCatGer: +For instance, the lincats of adverbs and conjunctions are the same +inCommonX(and therefore inCatGer, which inherits it):lincat Adv = {s : Str} ; @@ -647,7 +588,6 @@ in her hidden definitions of constants in-Paradigms. For instance, -- mkAdv s = {s = s ; lock_Adv = <>} ;Lexicon construction
The lexicon belonging to
-LangGerconsists of two modules: @@ -667,20 +607,17 @@ the coverage of the paradigms gets thereby tested and that the use of the paradigms inLexiconGergives a good set of examples for those who want to build new lexica.Inside grammar modules
Detailed implementation tricks are found in the comments of each module.
-The category system
-Phrase category modules
-Resource modules
- ResGer @@ -706,16 +642,13 @@ are found in the comments of each module.
- ParadigmsGer, ParadigmsGer.gf
Lexicon
-Lexicon extension
-The irregularity lexicon
It may be handy to provide a separate module of irregular @@ -725,7 +658,6 @@ few hundred perhaps. Building such a lexicon separately also makes it less important to cover everything by the worst-case paradigms (
-mkVetc).Lexicon extraction from a word list
You can often find resources such as lists of @@ -760,7 +692,6 @@ When using ready-made word lists, you should think about coyright issues. Ideally, all resource grammar material should be provided under GNU General Public License.
-Lexicon extraction from raw text data
This is a cheap technique to build a lexicon of thousands @@ -768,7 +699,6 @@ of words, if text data is available in digital format. See the Functional Morphology homepage for details.
-Extending the resource grammar API
Sooner or later it will happen that the resource grammar API @@ -777,7 +707,6 @@ that it does not include idiomatic expressions in a given language. The solution then is in the first place to build language-specific extension modules. This chapter will deal with this issue (to be completed).
-Writing an instance of parametrized resource grammar implementation
Above we have looked at how a resource implementation is built by @@ -797,7 +726,6 @@ the Romance family (to be completed). Here is a set of slides on the topic.
-Parametrizing a resource grammar implementation
This is the most demanding form of resource grammar writing. @@ -813,6 +741,6 @@ This chapter will work out an example of how an Estonian grammar is constructed from the Finnish grammar through parametrization.
- - + +