User:Dtr5 - Revision history

Dtr5 at 13:52, 22 December 2015

2015-12-22T13:52:25Z

Dtr5: /* Making your own configuration file */ New scripts for making configuration files

2012-08-07T11:14:34Z

Making your own configuration file: New scripts for making configuration files

Dtr5: /* Configuration file definition */

2012-07-06T19:32:30Z

Configuration file definition

Dtr5 at 09:49, 29 May 2012

2012-05-29T09:49:05Z

Dtr5 at 09:47, 29 May 2012

2012-05-29T09:47:45Z

Dtr5 at 09:11, 29 May 2012

2012-05-29T09:11:33Z

Dtr5 at 08:56, 29 May 2012

2012-05-29T08:56:34Z

Dtr5 at 08:55, 29 May 2012

2012-05-29T08:55:16Z

Dtr5 at 08:55, 29 May 2012

2012-05-29T08:55:02Z

Dtr5: /* Configuration file definition */

2012-05-29T08:53:34Z

Configuration file definition

@@ Line 17: / Line 17: @@
 The application runs over php, and uses [http://www.basex.org BaseX] as XML database. It also uses a bit of XSLT.
-===== Initialization =====
+===== Init =====
 [[File:Upload.png]]
@@ Line 159: / Line 159: @@
 Please, report all the bugs you find.
+== Contact ==
+username ''at'' alu ''dot'' ua ''dot'' es

@@ Line 113: / Line 113: @@
 ==== Making your own configuration file ====
-Now, you can make your own configuration file with this [http://apertium.vm.bytemark.co.uk/simpledix/simpledix/configHelp/configGenerator.tgz]
+Now, you can make your own configuration file with the scripts included in simpledix/simpledix/configHelp
-* We get the dictionaries we are going to work with.
+# First, we need the .dix files of the dictionaries we are going to work with
+# We have 4 options for generating the configuration files:
-* We execute one of the scripts getConfigFile.sh or getConfigFileInteractive.sh
+* Writing them by hand. Is a big job, but you will only have to do it one time.
 * The non-interactive script generates the configuration file of all the paradigms (including the auxiliary paradigms)
-  getConfigFile.sh apertium-lang1-lang2.lang.dix > config.lang.xml
+    getConfigFile.sh apertium-xx-yy.xx.dix
 * The interactive script asks us witch paradigms to include, one by one.
-  getConfigFile.sh apertium-lang1-lang2.lang.dix config.lang.xml
+    getConfigFileInteractive.sh apertium-xx-yy.xx.dix out.xml
-* The script extracts the idForm and the kind if the paradigm is in the '''acci/ó__n''' form.
+* The configurable script. We have to write a file that describes what kind of paradigms should go into the simpledix configuration file.
+    getConfigFile_2.sh apertium-xx-yy.xx.dix paradigms.xx-yy.txt
-* User may manually clear unwanted paradigms or flexions, and fill empty idForm, desc and kind fields.
+A possible description file:
+  vblex
+  .inf
+  .fts p2 sg
+  .ger
+  .imp p2 pl
+  .pis p2 sg
+  n
+  .m sg
+  .f sg
+  .m pl
+  .f pl
+  .mf sg
+  .mf pl
+  .m sp
+  .f sp
+  .mf sp
+This means that, for example, if we find a noun (''n'') paradigm, the configuration file will contain all of ''n, m, sg'', ''n, f, sg''... but not ''n, m, t''. The canonical form (''idform'') of the paradigm in the simpledix configuration file is decided by the order of this description file.
+The non-interactive and interactive versions of the script extract the idForm and the kind if the paradigm is in the '''acci/ó__n''' form. User has to manually clear unwanted paradigms or flexions, and fill empty idForm, desc and kind fields.
 ==== TODO ====

@@ Line 75: / Line 75: @@
   <splitter>
     <paradigms>
-        <paradigm n = "abric__n" idForm="" desc="Nom, Masculí (Abric)" kind="noun">
+        <paradigm n = "abric__n" idForm="" desc="Nom, Masculí (Abric)" kind="n">
             <flex form = "s"/>
         </paradigm>
-        <paradigm n = "ahir__adv" idForm = "" desc = "Adverbi (Ahir)" kind="adverb"/>
+        <paradigm n = "ahir__adv" idForm = "" desc = "Adverbi (Ahir)" kind="adv"/>
-        <paradigm n = "abell/a__n" idForm = "a" desc = "Nom, Femení (Abella)" kind="noun">
+        <paradigm n = "abell/a__n" idForm = "a" desc = "Nom, Femení (Abella)" kind="n">
             <flex form = "es"/>
         </paradigm>
-        <paradigm n = "abander/ar__lex" idForm = "ar" desc = "Verb regular, 1ª conjugació (Abanderar)" kind="verb">
+        <paradigm n = "abander/ar__lex" idForm = "ar" desc = "Verb regular, 1ª conjugació (Abanderar)" kind="vb">
             <flex form = "àssiu"/>
             <flex form = "àveu"/>
         </paradigm>
-        <paradigm n = "abdominal__adj" idForm = "" desc = "Adjectiu, masculí/femení (Abdominal)" kind="adjective">
+        <paradigm n = "abdominal__adj" idForm = "" desc = "Adjectiu, masculí/femení (Abdominal)" kind="adj">
             <flex form = "s"/>
         </paradigm>
-        <paradigm n = "acci/ó__n" idForm = "ó" desc = "Nom, Femení (Acció)" kind="noun">
+        <paradigm n = "acci/ó__n" idForm = "ó" desc = "Nom, Femení (Acció)" kind="n">
             <flex form = "ons"/>
         </paradigm>
-        <paradigm n = "acadèmi/c__adj" idForm = "c" desc = "Adjectiu, masculí (Acadèmic)" kind="adjective">
+        <paradigm n = "acadèmi/c__adj" idForm = "c" desc = "Adjectiu, masculí (Acadèmic)" kind="adj">
             <flex form = "cs"/>
             <flex form = "ca"/>

@@ Line 106: / Line 106: @@
 * '''kind''' : lexical type of the paradigm.
-'''All the attributes need value'''
+'''All the attributes, but idForm, need a non empty-string value'''
 The '''<flex>''' node represents a significative form of a paradigm. They should be as representative as possible, so the user can change the paradigm if he sees a bad flexion. Also, they should be as few as possible, because a long list will lead to user skipping this list. It has only 1 attribute:

@@ Line 105: / Line 105: @@
 * '''desc''' : short, simple description showed in the paradigm list. Useful for pairs with obscure paradigm names (like LAT_35 in eu)
 * '''kind''' : lexical type of the paradigm.
+'''All the attributes need value'''
 The '''<flex>''' node represents a significative form of a paradigm. They should be as representative as possible, so the user can change the paradigm if he sees a bad flexion. Also, they should be as few as possible, because a long list will lead to user skipping this list. It has only 1 attribute: