User:Ilnar.salimzyan/Wishlist - Revision history

Ilnar.salimzyan: /* A new DTD for .dix files */

2015-03-08T15:20:40Z

A new DTD for .dix files

Ilnar.salimzyan: /* Pan-turkic-english-russian dictionary */

2015-03-08T14:57:11Z

Pan-turkic-english-russian dictionary

Ilnar.salimzyan at 14:55, 8 March 2015

2015-03-08T14:55:36Z

Ilnar.salimzyan at 14:55, 8 March 2015

2015-03-08T14:55:17Z

Ilnar.salimzyan: /* A new DTD for .dix files */

2015-03-08T14:53:11Z

A new DTD for .dix files

Ilnar.salimzyan: /* Pan-turkic-english-russian dictionary */

2015-03-08T14:51:11Z

Pan-turkic-english-russian dictionary

Ilnar.salimzyan: /* Pan-turkic-english-russian dictionary */

2015-03-08T14:50:37Z

Pan-turkic-english-russian dictionary

Ilnar.salimzyan at 14:13, 8 March 2015

2015-03-08T14:13:27Z

Ilnar.salimzyan at 14:08, 8 March 2015

2015-03-08T14:08:24Z

Ilnar.salimzyan at 14:06, 8 March 2015

2015-03-08T14:06:38Z

← Older revision		Revision as of 15:20, 8 March 2015
Line 26:		Line 26:

	When creating a DTD for the multilingual dictionary described above, would be great to allow a <subsection> element which can have a "name" attribute and appears inside of <nowiki><section></nowiki> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <nowiki><!-- SECTION: some-noun-category-we-want-to-distinguish --></nowiki>		When creating a DTD for the multilingual dictionary described above, would be great to allow a <subsection> element which can have a "name" attribute and appears inside of <nowiki><section></nowiki> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <nowiki><!-- SECTION: some-noun-category-we-want-to-distinguish --></nowiki>

			"Use/MT attribute should probably also be codified in DTD in case we ever want to export entries from the multilingual dictionary into a monolinguagual dictionary (lexc or dix, doesn't matter).

@@ Line 21: / Line 21: @@
 There are some little tricks in pardefs (which you can't have when using some spreadsheet or similar) useful when translating into/from Russian or English, they would work for any Turkic language.
-The main motivation for such a dictionary is that we keep everything in one place so that we can control things like "мүмкін емес". The reason it appeared in kaz.lexc was that eng-kaz.dix contained it. If there is a better way to handle it, we could agree upon one and store it in our pan-turkic dictionary. You know, one single point of leverage for harnessing the influence of non-turkic languages :)
+The main motivation for such a dictionary is that we keep everything in one place so that we can control things like "мүмкін емес". The reason it appeared in kaz.lexc was that eng-kaz.dix required it. If there is a better way to handle it, we could agree upon one and store it in our pan-turkic dictionary. You know, one single point of leverage for harnessing the influence of non-turkic languages :)
 === A new DTD for .dix files ===

← Older revision		Revision as of 14:55, 8 March 2015
Line 25:		Line 25:
	=== A new DTD for .dix files ===		=== A new DTD for .dix files ===

	When creating a DTD for the multilingual dictionary described above, would be great to allow a <subsection> element which can have a "name" attribute and appears inside of <nowiki><section></nowiki> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <!-- SECTION: some-noun-category-we-want-to-distinguish -->		When creating a DTD for the multilingual dictionary described above, would be great to allow a <subsection> element which can have a "name" attribute and appears inside of <nowiki><section></nowiki> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <nowiki><!-- SECTION: some-noun-category-we-want-to-distinguish --></nowiki>

← Older revision		Revision as of 14:55, 8 March 2015
Line 25:		Line 25:
	=== A new DTD for .dix files ===		=== A new DTD for .dix files ===

	When creating a DTD for the multilingual dictionary described above, would be great to allow a <subsection> element which can have a "name" attribute and appears inside of <section> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <!-- SECTION: some-noun-category-we-want-to-distinguish -->		When creating a DTD for the multilingual dictionary described above, would be great to allow a <subsection> element which can have a "name" attribute and appears inside of <nowiki><section></nowiki> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <!-- SECTION: some-noun-category-we-want-to-distinguish -->

← Older revision		Revision as of 14:53, 8 March 2015
Line 25:		Line 25:
	=== A new DTD for .dix files ===		=== A new DTD for .dix files ===

	A ~~new~~ DTD for ~~.dix~~ ~~files~~ ~~which~~ would ~~have~~ a <subsection> element which can have a "name" attribute and appears inside of <section> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <!-- SECTION: some-noun-category-we-want-to-distinguish -->		When creating a DTD for the multilingual dictionary described above, would be great to allow a <subsection> element which can have a "name" attribute and appears inside of <section> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <!-- SECTION: some-noun-category-we-want-to-distinguish -->

@@ Line 23: / Line 23: @@
 The main motivation for such a dictionary is that we keep everything in one place so that we can control things like "мүмкін емес". The reason it appeared in kaz.lexc was that eng-kaz.dix contained it. If there is a better way to handle it, we could agree upon one and store it in our pan-turkic dictionary. You know, one single point of leverage for harnessing the influence of non-turkic languages :)
-=== A new DTD for.dix files ===
+=== A new DTD for .dix files ===
 A new DTD for .dix files which would have a <subsection> element which can have a "name" attribute and appears inside of <section> element. The idea is to be able to sort a .dix file automatically without breaking the internal order (which currently happens when the section names are just comments of the form <!-- SECTION: some-noun-category-we-want-to-distinguish -->

@@ Line 5: / Line 5: @@
 == Pan-turkic-english-russian dictionary ==
-Pan-turkic+english+russian dictionary which we maintain (which is a superset of any Turkic-to-Turkic, Turkic-to-English, Turkic-to-Russian bidix and is aldo used for testing translators). Would help with classification of stems (i.e. with being consistent across Turkic pairs). Exporting that into OmegaWiki would be cool as well (although we need much less than what Omegawiki does).
+Pan-turkic+english+russian dictionary which we maintain (which is a superset of any Turkic-to-Turkic, Turkic-to-English, Turkic-to-Russian bidix and is also used for testing translators). Would help with classification of stems (i.e. with being consistent across Turkic pairs). Exporting that into OmegaWiki would be cool as well (although we need much less than what Omegawiki does).
 I would store it in a format as close to the current bidix format as possible, e.g.:

@@ Line 1: / Line 1: @@
+== Annotatrix ==
-* for [[Annotatrix]]: comparing my annotation with annotation done by another user, calculating the inter-annotator agreement and easy merging of the two versions by highlighting sentences which differ.
-* pan-turkic+english+russian dictionary which we maintain (which is a superset of any Turkic-to-Turkic, Turkic-to-English, Turkic-to-Russian bidix and also is used for testing translators). Would help with classification of stems as well (i.e. with being consistent across Turkic pairs). Exporting that into OmegaWiki would be cool as well (although we need much less than what Omegawiki does).
+For [[Annotatrix]]: Comparing my annotation with annotation done by another user, calculating the inter-annotator agreement and easy merging of the two versions by highlighting sentences which differ.
+== Pan-turkic-english-russian dictionary ==
+Pan-turkic+english+russian dictionary which we maintain (which is a superset of any Turkic-to-Turkic, Turkic-to-English, Turkic-to-Russian bidix and also is used for testing translators). Would help with classification of stems as well (i.e. with being consistent across Turkic pairs). Exporting that into OmegaWiki would be cool as well (although we need much less than what Omegawiki does).
+I would store it in a format as close to the current bidix format as possible, e.g.:
+<pre>
+<e>
+  <p>
+    <tat>китап<sdef n="n"/></tat>
+    <kaz>кітап<sdef n="n"/></kaz>
+    <eng>book<sdef n="n"/></eng>
+    <rus>книга<sdef n="n"/><sdef n="nn"/><sdef n="f"/></rus>
+  </p>
+<e>
+</pre>
+There are some tricks in pardefs (which you can't have when using some spreadsheet or similar) useful when translating into/from Russian or English, they would work for any Turkic language.
+The main motivation for such a dictionary is that we keep everything in one place so that we can control things like "мүмкін емес". The reason it appeared in kaz.lexc was that eng-kaz.dix contained it. If there is a better way to handle it, we could agree upon one and store it in our pan-turkic dictionary. You know, one single point of leverage for harnessing the influence of non-turkic languages :)