User:Xavivars/Overlapping language variants - Revision history

Gramirez: /* Multiple variants per entry */

2017-02-24T11:22:15Z

Multiple variants per entry

Gramirez: /* Multiple variants per entry */

2017-02-24T10:12:36Z

Multiple variants per entry

Gramirez: /* One entry, multiple variants */

2017-02-24T10:11:35Z

One entry, multiple variants

Gramirez: /* Id-based variants */

2017-02-24T10:10:25Z

Id-based variants

Gramirez: /* One entry, multiple variants */

2017-02-24T10:00:13Z

One entry, multiple variants

Gramirez: /* One entry, multiple variants */

2017-02-24T09:59:41Z

One entry, multiple variants

Gramirez: /* One entry, multiple variants */

2017-02-24T09:58:53Z

One entry, multiple variants

Gramirez at 15:30, 23 February 2017

2017-02-23T15:30:50Z

Gramirez: /* Id-based variants */

2017-02-23T15:25:32Z

Id-based variants

Gramirez: /* Id-based variants */

2017-02-23T15:19:53Z

Id-based variants

@@ Line 178: / Line 178: @@
 <e v="cat_uni cat_gva"><p><l>cubo<s n="n"/></l><r>poal<s n="n"/></r></p></e>
-<e v="cat><p><l>cubo<s n="n"/><s n="m"/></l><r>galleda<s n="n"/><s n="f"/></r></p></e>
+<e v="cat"><p><l>cubo<s n="n"/><s n="m"/></l><r>galleda<s n="n"/><s n="f"/></r></p></e>
@@ Line 187: / Line 187: @@
 ...
 VAR1=#deixar en blanc
-VAR2=_valencia_uni
+VAR2=_valencia-uni
-VAR3=_valencia_gva
+VAR3=_valencia-gva
 ...
 $(LANG1)$(VAR1).autogen.bin: $(BASENAME).$(LANG1).dix .deps/.d
         apertium-validate-dictionary $<
-        lt-comp -c cat rl $< $@ $(BASENAME).$(LANG1).acx
+        lt-comp -v cat rl $< $@ $(BASENAME).$(LANG1).acx
 $(LANG1)$(VAR2).autogen.bin: $(BASENAME).$(LANG1).dix .deps/.d
         apertium-validate-dictionary $<
-        lt-comp -c cat_uni rl $< $@ $(BASENAME).$(LANG1).acx
+        lt-comp -v cat_uni rl $< $@ $(BASENAME).$(LANG1).acx
 $(LANG1)$(VAR3).autogen.bin: $(BASENAME).$(LANG1).dix .deps/.d
         apertium-validate-dictionary $<
-        lt-comp -c cat_gva rl $< $@ $(BASENAME).$(LANG1).acx
+        lt-comp -v cat_gva rl $< $@ $(BASENAME).$(LANG1).acx
 </pre>
 This gets all variants as LR and set variant choices as RL.
+Moreover we propose a change to lt-comp to exclude variants from morphological analyser. That is, for example, to exclude balearic variants from val_uni or cat morphological analysers to avoid ambiguity.
 And then we create also the bilingual transducer to get from Spanish to Catalan the language variant dependent lexical choice also in the Makefile.
@@ Line 211: / Line 213: @@
 '''Benefits''': it is simple, all the info stays in the dix files, is consistent and easy to understand.
-'''Requirements''': modify v= attribute to carry more than one value and lt-comp too?
+'''Requirements''': mark explicitly all entries, no grouping can be done;  modify v= attribute to carry more than one value (NTOKEN) and lt-comp.

← Older revision		Revision as of 10:12, 24 February 2017
Line 209:		Line 209:


	'''Benefits''': it is simple, all the info stays in ~~a single~~ dix ~~file and~~ is easy to understand.		'''Benefits''': it is simple, all the info stays in the dix files, is consistent and easy to understand.

	'''Requirements''': modify v= attribute to carry more than one value and lt-comp too?		'''Requirements''': modify v= attribute to carry more than one value and lt-comp too?

@@ Line 152: / Line 152: @@
 In this file, we maintain all the info related to variants in the bilingual package.
-=== One entry, multiple variants===
+=== Multiple variants per entry===
 The idea is to extend the attribute '''v''' for entries so as it can carry more than one value:

@@ Line 95: / Line 95: @@
 The idea is to have entries that are alternative language variant forms to one "general" form marked with a unique ID as follows:
+In the monolingual dictionary we have:
 <pre>
-<e eid="la-meua"><p><l>la<b/>meva</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
+<e eid="la-meva-det"><p><l>la<b/>meva</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
+<e eid="la-meua-det"><p><l>la<b/>meua</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
  ...
-<e eid="è-n"><p><l>è</l><r>è<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
+<e eid="cafè-n"><p><l>è</l><r>è<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
  ...
 <e><i>poal</i><pardef n="abric__n"></e>
-<e><i>galleda</i><pardef n="abric__n"></e>
+<e><i>galleda</i><pardef n="abella__n"></e>
 </pre>
+In a different file, we explicit what we do to the alternatives marked with ID by variant with sections like
+<pre>
+<?xml version=“1.0”?>
+<variant name=“valencia_uni”>
+ <replace>
+   <e eid="la-meva-det">
+   <e eid="la-meua-det">
+ </replace>
+ <replace>
+    <e eid="cafè-n">
+    <e eid="café-n">
+  </replace>
+</variant>
+</pre>
+In this file, we maintain all the info related to variants in the monolingual package.
@@ Line 110: / Line 133: @@
 <pre>
 ...
-<e><p><l>cubo<s n="n"/><s n="m"/></l><r>galleda<s n="n"/><s n="f"/></r></p></e>
+<e eid="galleda-n"><p><l>cubo<s n="n"/><s n="m"/></l><r>galleda<s n="n"/><s n="f"/></r></p></e>
+<e eid="poal-n"><p><l>cubo<s n="n"/></l><r>poal<s n="n"/></r></p></e>
 ...
 </pre>
-In a different file, we explicit what we do to the alternatives marked with ID by variant with sections like
+In a different file, only for bilingual lexical choices, we explicit what we do to the alternatives marked with IDs:
 <pre>
 <?xml version=“1.0”?>
-<variant name=“valencia”>
+<variant name=“valencia_uni”>
  <replace>
+   <e eid="galleda-n">
- <e eid="la-meva"><p><l>la<b/>meua</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
+   <e eid="poal-n">
  </replace>
-  <replace>
-    <e id="café-nsg"><p><l>é</l>        <r>è<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
-    <e>                       <p><l>è</l>         <r>è<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
-  </replace>
-  <add>
-  </add>
-  <remove>
-  </remove>
 </variant>
 </pre>
-In this file, we maintain all the info related to variants.
+In this file, we maintain all the info related to variants in the bilingual package.
 === One entry, multiple variants===

@@ Line 193: / Line 193: @@
 '''Benefits''': it is simple, all the info stays in a single dix file and is easy to understand.
-'''
-Requirements''': modify v= attribute to carry more than one value and lt-comp too?
+'''Requirements''': modify v= attribute to carry more than one value and lt-comp too?

@@ Line 140: / Line 140: @@
 <pre>
+In the pardef section (orthographic changes)
  <e v="cat"><p><l>la<b/>meva</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
  <e v="cat_uni cat_gva"><p><l>la<b/>meua</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
  ...
- <e v="cat cat_uni>                          <p><l>ès</l>   <r>ès<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
- <e v="cat_gva">                             <p><l>és</l>   <r>ès<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
+ <e v="cat cat_uni><p><l>ès</l><r>ès<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
+ <e v="cat_gva"><p><l>és</l><r>ès<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
 ...
+In the main section (lexical changes).
+ I think they must be marked also, even if the choice is made in the bilingual dix, to have the info available in a monolingual view. It does not harm...
  <e v="cat_uni cat_gva"><i>poal</i><pardef n="abric__n"></e>
  <e v="cat"><i>galleda</i><pardef n="abric__n"></e>
 ...
+In the bilingual
+<e v="cat_uni cat_gva"><p><l>cubo<s n="n"/></l><r>poal<s n="n"/></r></p></e>
+<e v="cat><p><l>cubo<s n="n"/><s n="m"/></l><r>galleda<s n="n"/><s n="f"/></r></p></e>
 </pre>
-As we do now, we would create the appropriate entries for generation depending on the variant during compilation in the Makefile
+As we do now, we would create the appropriate morphological generator depending on the variant during compilation in the Makefile
 <pre>
 ...
@@ Line 172: / Line 187: @@
 </pre>
+This gets all variants as LR and only set variant choices as RL.
-Benefits: it is simple, all the info stays in a single dix file and is easy to understand.
+And then we create also the bilingual transducer to get from Spanish to Catalan the language variant dependent lexical choice also in the Makefile.
+'''Benefits''': it is simple, all the info stays in a single dix file and is easy to understand.
+'''
+Requirements''': modify v= attribute to carry more than one value and lt-comp too?

@@ Line 97: / Line 97: @@
 <pre>
- <e><p><l>la<b/>meva</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
+ <e eid="la-meua"><p><l>la<b/>meva</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
- <e id="meua-det"><p><l>la<b/>meua</l><r>el<b/>meu<s n="det"/><s n="pos"/><s n="f"/><s n="sg"/></r></p></e>
  ...
- <e><p><l>è</l><r>è<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
+<e eid="è-n"><p><l>è</l><r>è<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
- <e id="café-n"><p><l>é</l><r>è<s n="n"/><s n="m"/><s n="sg"/></r></p></e>
 </pre>
-</pre>
 In a different file, we explicit what we do to the alternatives marked with ID by variant with sections like