Unification of metadix and parametrized dictionaries - Revision history

Unhammer: /* Fran's summary */

2016-04-25T08:24:43Z

Fran's summary

Bech: Link to French page

2014-10-08T08:36:44Z

Link to French page

Bech: Category:Documentation in English (for this page, can be discuted)

2012-03-24T11:24:57Z

Category:Documentation in English (for this page, can be discuted)

Francis Tyers: no :'(

2008-07-04T10:23:57Z

no :'(

Francis Tyers: /* Header */

2008-07-04T10:23:34Z

Header

Francis Tyers at 08:18, 4 December 2007

2007-12-04T08:18:12Z

Francis Tyers: /* Fran's summary */

2007-11-05T10:07:19Z

Fran's summary

85.56.129.103 at 06:47, 1 November 2007

2007-11-01T06:47:14Z

85.56.129.103 at 06:44, 1 November 2007

2007-11-01T06:44:11Z

85.56.129.103 at 06:36, 1 November 2007

2007-11-01T06:36:25Z

@@ Line 310: / Line 310: @@
   <e lm="datoteka"><i>datoteka</i><par n="luka__n"/></e>
 </pre>
+==See also==
+* Proposal for multiple prm's at http://wiki.apertium.org/wiki/Talk:Metadix
 [[Category:Discussions]]

@@ Line 1: / Line 1: @@
+[[Unification des metadix et dictionnaires paramétrés|En français]]
 {{TOCD}}
 Different language-pair packages use different strategies to generate .dix dictionaries ([[monodix]]) and ([[bidix]]) from XML files using features not supported by the .dix format. The objectives of these new dix-like formats are:
@@ Line 89: / Line 91: @@
 Probably it is a good idea for all possible values of <code>alt</code> to be previously declared in the header (see above).
-A generalization of this would be a <code>wrap</code> element having three attributes: <code>element</code> (the name of the element affected), <code>attribute</code> (the name of the attribute) and <code>value</code> (the value of the attribute), so that <code><wrap element="e" attribute="alt" value="xx"></code> would be equivalent to <code><e-group alt="xx"></code> and <code><wrap element="rule" attribute="alt" value="xx"></code> would be equivalent to <code><rule-group alt="xx"></code>, but perhaps this is too general.
+A generalisation of this would be a <code>wrap</code> element having three attributes: <code>element</code> (the name of the element affected), <code>attribute</code> (the name of the attribute) and <code>value</code> (the value of the attribute), so that <code><wrap element="e" attribute="alt" value="xx"></code> would be equivalent to <code><e-group alt="xx"></code> and <code><wrap element="rule" attribute="alt" value="xx"></code> would be equivalent to <code><rule-group alt="xx"></code>, but perhaps this is too general.
 ==Parametrized paradigms==

← Older revision		Revision as of 11:24, 24 March 2012
Line 310:		Line 310:

	[[Category:Discussions]]		[[Category:Discussions]]
			[[Category:Documentation in English]]

@@ Line 17: / Line 17: @@
 <pre>
-<dictionary type="monodix">
+<dictionary>
   <header>
+    <type>monolingual</type>
     <language code="ca" full="Català"/>
-    <def-alt>
+    <alternatives>
-      <alt-item code="ca@valencian" full="Valencià"/>
+      <alternative code="ca@valencian" full="Valencià"/>
-      <alt-item code="ca" full="Català"/>
+      <alternative code="ca" full="Català"/>
-    </def-alt>
+    </alternatives>
-    <def-app n="eco">
-      <include>
-        <alt-item code="ca@valencian" r="LR"/>
-        <alt-item code="ca"/>
-        <alt-item code="ca@eco"/>
-      </include>
-    </def-app>
-    <def-app n="ca">
-      <include>
-        <alt-item code="ca@valencian" r="LR"/>
-        <alt-item code="ca"/>
-      </include>
-      <exclude>
-        <alt-item code="ca@eco"/>
-      </exclude>
-    </def-app>
-    <def-app n="ca@valencian">
-      <include>
-        <alt-item code="ca@valencian"/>
-        <alt-item code="ca" r="LR"/>
-      </include>
-      <exclude>
-        <alt-item code="ca@eco"/>
-      </exclude>
-    </def-app>
   </header>
   ...
-<dictionary type="monodix">
-  <header>
-    <language code="oc" full="Occitano"/>
-    <def-alt>
-      <alt-item mode="exc" code="oc@aran" full="Aranés"/>
-      <alt-item mode="exc" code="oc" full="Occitano"/>
-    </def-alt>
-  </header>
 </pre>

@@ Line 17: / Line 17: @@
 <pre>
-<dictionary>
+<dictionary type="monodix">
   <header>
-    <type>monolingual</type>
     <language code="ca" full="Català"/>
-    <alternatives>
+    <def-alt>
-      <alternative code="ca@valencian" full="Valencià"/>
+      <alt-item code="ca@valencian" full="Valencià"/>
-      <alternative code="ca" full="Català"/>
+      <alt-item code="ca" full="Català"/>
-    </alternatives>
+    </def-alt>
+    <def-app n="eco">
+      <include>
+        <alt-item code="ca@valencian" r="LR"/>
+        <alt-item code="ca"/>
+        <alt-item code="ca@eco"/>
+      </include>
+    </def-app>
+    <def-app n="ca">
+      <include>
+        <alt-item code="ca@valencian" r="LR"/>
+        <alt-item code="ca"/>
+      </include>
+      <exclude>
+        <alt-item code="ca@eco"/>
+      </exclude>
+    </def-app>
+    <def-app n="ca@valencian">
+      <include>
+        <alt-item code="ca@valencian"/>
+        <alt-item code="ca" r="LR"/>
+      </include>
+      <exclude>
+        <alt-item code="ca@eco"/>
+      </exclude>
+    </def-app>
   </header>
   ...
+<dictionary type="monodix">
+  <header>
+    <language code="oc" full="Occitano"/>
+    <def-alt>
+      <alt-item mode="exc" code="oc@aran" full="Aranés"/>
+      <alt-item mode="exc" code="oc" full="Occitano"/>
+    </def-alt>
+  </header>
 </pre>

@@ Line 264: / Line 264: @@
 <pre>
-<pardef n="ab/i[T]ar__vblex" prm-list="cons">
+<pardef n="ab/i[T]ar__vblex" prm-list="cons cons2">
   <e alt="oc@aran">
     <p>
@@ Line 270: / Line 270: @@
       <r>i</r>
     </p>
-    <i><txt-prm n="cons"/></i>
+    <i><txt-prm n="cons"/><txt-prm n="cons2"/></i>
     <par n="cànt/iga__vblex"/>
   </e>
@@ Line 298: / Line 298: @@
   <e lm="house"><i>house</i><par n="house__n"/></e>
   <e lm="time"><i>time</i><par n="house__n" prms="count='unc'"/></e>
-  <e lm="brilhar"><i>br</i><par n="ab/i[T]ar__vblex" prms="cons='lh'"/></e>
+  <e lm="brilhar"><i>br</i><par n="ab/i[T]ar__vblex" prms="cons='lh' cons2='tx'"/></e>
   <e lm="aerodrom"><i>aerodrom</i><par n="aerodrom__n"/></e>
   <e lm="avion"><i>avion<b/>luka</i><par n="aerodrom__n"/></e>

@@ Line 256: / Line 256: @@
 ==Fran's summary==
+[with attribute names slightly changed to conform with the above]
 This is a brief summary detailing the various ways that the new format could be used. These are all in different languages, but it could be that any pair of languages might use all these features.
@@ Line 266: / Line 268: @@
       <r>i</r>
     </p>
-    <i><prm-txt n="cons"/></i>
+    <i><txt-prm n="cons"/></i>
     <par n="cànt/iga__vblex"/>
   </e>
   <e>
-    <i>i<prm-txt n="cons"/></i>
+    <i>i<txt-prm n="cons"/></i>
     <par n="cant/as__vblex"/>
   </e>
@@ Line 279: / Line 281: @@
     <p>
       <l/>
-      <r><s n="n"/><prm-sym n="count"/><s n="sg"/></r>
+      <r><s n="n"/><symbol-prm n="count"/><s n="sg"/></r>
     </p>
   </e>
@@ Line 285: / Line 287: @@
     <p>
       <l>s</l>
-      <r><s n="n"/><prm-sym n="count"/><s n="pl"/></r>
+      <r><s n="n"/><symbol-prm n="count"/><s n="pl"/></r>
     </p>
   </e>

← Older revision		Revision as of 06:36, 1 November 2007
Line 252:		Line 252:
	</pre>		</pre>

	in a completely analogous way to word-form parameters. The only difference is that <code><symbol-prm n="x"></code> generates <code><s n="y"></code> if the value of <code>x</code> is <code>y</code>, whereas <code><txt-prm n="x"></code> generates just <code>y</code>.		in a completely analogous way to word-form parameters. The only difference is that <code><symbol-prm n="x"></code> generates <code><s n="y"></code> if the value of <code>x</code> is <code>y</code>, whereas <code><txt-prm n="x"></code> generates just <code>y</code>.