http://wikis.swarthmore.edu/ling073/api.php?action=feedcontributions&feedformat=atom&user=Cdalton2LING073 - User contributions [en]2026-10-25T00:00:10ZUser contributionsMediaWiki 1.27.7http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7737Cdalton2/Final project2018-05-12T19:21:08Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
See the poster for a visual representation of the layout, as well as references and other information:<br />
<br />
[[File:RohingyaHanifiPoster.jpg|thumb]]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla could be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi characters are most common in Rohingya texts)'''<br />
<br />
== Further issues ==<br />
<br />
* Since Rohingya characters will not be added to the Unicode Standard until June 5, 2018 and the fonts are not yet implemented, everything will just show up as boxes until then<br />
<br />
* We should have better ways of evaluating the efficiency and suitability of keyboard layouts<br />
<br />
* The Windows keyboard layout is listed under Romanian (Moldova) due to system limitations (i.e., there is no Rohingya option in the language field of Microsoft Keyboard Layout Creator, so I just went with a completely unrelated language whose name also happens to begin with "Ro," with apologies to both language communities)<br />
<br />
* You have to change a random obscure setting to get the layout to show up in Windows 10 (this is detailed in the INSTALL file)<br />
<br />
* Should retired/variant glyphs be included in the keyboard? Pandey's proposed Unicode block includes several characters that are stylistic variants or no longer used<br />
<br />
* Danger of appearing to promote one script over the other<br />
<br />
* Should vowel signs be more accessible? Although they are not considered full letters, they are obligatory, unlike in Arabic<br />
<br />
== References ==<br />
<br />
Mahmood, Syed S., Emily Wroe, Arlan Fuller, & Jennifer Leaning. 2017. The Rohingya people of Myanmar: Health, human rights, and identity. ''Lancet'' 389: 1841-1850. Amsterdam: Elsevier.<br />
<br />
Pandey, Anshuman. 2016. Revised proposal to include Hanifi Rohingya in Unicode. Unicode Technical Committee Document Registry. https://www.unicode.org/L2/L2016/16311r-hanifi-rohingya.pdf.<br />
<br />
Translators without Borders. 2017. Rohingya Zuban: A Translators without Borders rapid assessment of language barriers in the Cox's Bazar refugee response. https://translatorswithoutborders.org/rohingya-zuban/ (6 Feb., 2018.)<br />
<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7736Cdalton2/Final project2018-05-12T19:18:35Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
See the poster for a visual representation of the layout, as well as references and other information:<br />
<br />
[[File:RohingyaHanifiPoster.jpg|thumb]]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla could be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi characters are most common in Rohingya texts)'''<br />
<br />
== Further issues ==<br />
<br />
* Since Rohingya characters will not be added to the Unicode Standard until June 5, 2018 and the fonts are not yet implemented, everything will just show up as boxes until then<br />
<br />
* We should have better ways of evaluating the efficiency and suitability of keyboard layouts<br />
<br />
* The Windows keyboard layout is listed under Romanian (Moldova) due to system limitations (i.e., there is no Rohingya option in the language field of Microsoft Keyboard Layout Creator, so I just went with a completely unrelated language whose name also happens to begin with "Ro," with apologies to both language communities)<br />
<br />
* You have to change a random obscure setting to get the layout to show up in Windows 10 (this is detailed in the INSTALL file)<br />
<br />
* Should retired/variant glyphs be included in the keyboard? Pandey's proposed Unicode block includes several characters that are stylistic variants or no longer used<br />
<br />
* Danger of appearing to promote one script over the other<br />
<br />
* Should vowel signs be more accessible? Although they are not considered full letters, they are obligatory, unlike in Arabic<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7735Cdalton2/Final project2018-05-12T19:18:08Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
See the poster for a visual representation of the layout, as well as references and other information:<br />
<br />
[[File:RohingyaHanifiPoster.jp]]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla could be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi characters are most common in Rohingya texts)'''<br />
<br />
== Further issues ==<br />
<br />
* Since Rohingya characters will not be added to the Unicode Standard until June 5, 2018 and the fonts are not yet implemented, everything will just show up as boxes until then<br />
<br />
* We should have better ways of evaluating the efficiency and suitability of keyboard layouts<br />
<br />
* The Windows keyboard layout is listed under Romanian (Moldova) due to system limitations (i.e., there is no Rohingya option in the language field of Microsoft Keyboard Layout Creator, so I just went with a completely unrelated language whose name also happens to begin with "Ro," with apologies to both language communities)<br />
<br />
* You have to change a random obscure setting to get the layout to show up in Windows 10 (this is detailed in the INSTALL file)<br />
<br />
* Should retired/variant glyphs be included in the keyboard? Pandey's proposed Unicode block includes several characters that are stylistic variants or no longer used<br />
<br />
* Danger of appearing to promote one script over the other<br />
<br />
* Should vowel signs be more accessible? Although they are not considered full letters, they are obligatory, unlike in Arabic<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7734Cdalton2/Final project2018-05-12T19:17:43Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
See the poster for a visual representation of the layout, as well as references and other information:<br />
<br />
[[File:RohingyaHanifiPoster.jpg]]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla could be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi characters are most common in Rohingya texts)'''<br />
<br />
== Further issues ==<br />
<br />
* Since Rohingya characters will not be added to the Unicode Standard until June 5, 2018 and the fonts are not yet implemented, everything will just show up as boxes until then<br />
<br />
* We should have better ways of evaluating the efficiency and suitability of keyboard layouts<br />
<br />
* The Windows keyboard layout is listed under Romanian (Moldova) due to system limitations (i.e., there is no Rohingya option in the language field of Microsoft Keyboard Layout Creator, so I just went with a completely unrelated language whose name also happens to begin with "Ro," with apologies to both language communities)<br />
<br />
* You have to change a random obscure setting to get the layout to show up in Windows 10 (this is detailed in the INSTALL file)<br />
<br />
* Should retired/variant glyphs be included in the keyboard? Pandey's proposed Unicode block includes several characters that are stylistic variants or no longer used<br />
<br />
* Danger of appearing to promote one script over the other<br />
<br />
* Should vowel signs be more accessible? Although they are not considered full letters, they are obligatory, unlike in Arabic<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=File:RohingyaHanifiPoster.jpg&diff=7733File:RohingyaHanifiPoster.jpg2018-05-12T19:17:16Z<p>Cdalton2: </p>
<hr />
<div></div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7732Cdalton2/Final project2018-05-12T19:15:36Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
See the poster for a visual representation of the layout, as well as references and other information:<br />
<br />
[[File:https://i.imgur.com/mVLTq0W.jpg]]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla could be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi characters are most common in Rohingya texts)'''<br />
<br />
== Further issues ==<br />
<br />
* Since Rohingya characters will not be added to the Unicode Standard until June 5, 2018 and the fonts are not yet implemented, everything will just show up as boxes until then<br />
<br />
* We should have better ways of evaluating the efficiency and suitability of keyboard layouts<br />
<br />
* The Windows keyboard layout is listed under Romanian (Moldova) due to system limitations (i.e., there is no Rohingya option in the language field of Microsoft Keyboard Layout Creator, so I just went with a completely unrelated language whose name also happens to begin with "Ro," with apologies to both language communities)<br />
<br />
* You have to change a random obscure setting to get the layout to show up in Windows 10 (this is detailed in the INSTALL file)<br />
<br />
* Should retired/variant glyphs be included in the keyboard? Pandey's proposed Unicode block includes several characters that are stylistic variants or no longer used<br />
<br />
* Danger of appearing to promote one script over the other<br />
<br />
* Should vowel signs be more accessible? Although they are not considered full letters, they are obligatory, unlike in Arabic<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7726Cdalton2/Final project2018-05-12T18:27:37Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla could be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi characters are most common in Rohingya texts)'''<br />
<br />
== Further issues ==<br />
<br />
* Since Rohingya characters will not be added to the Unicode Standard until June 5, 2018 and the fonts are not yet implemented, everything will just show up as boxes until then<br />
<br />
* We should have better ways of evaluating the efficiency and suitability of keyboard layouts<br />
<br />
* The Windows keyboard layout is listed under Romanian (Moldova) due to system limitations (i.e., there is no Rohingya option in the language field of Microsoft Keyboard Layout Creator, so I just went with a completely unrelated language whose name also happens to begin with "Ro," with apologies to both language communities)<br />
<br />
* You have to change a random obscure setting to get the layout to show up in Windows 10 (this is detailed in the INSTALL file)<br />
<br />
* Should retired/variant glyphs be included in the keyboard? Pandey's proposed Unicode block includes several characters that are stylistic variants or no longer used<br />
<br />
* Danger of appearing to promote one script over the other<br />
<br />
* Should vowel signs be more accessible? Although they are not considered full letters, they are obligatory, unlike in Arabic<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7725Cdalton2/Final project2018-05-12T18:27:04Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla could be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi characters are most common in Rohingya texts)'''<br />
<br />
== Further issues ==<br />
<br />
* Since Rohingya characters will not be added to the Unicode Standard until June 5, 2018 and the fonts are not yet implemented, everything will just show up as boxes until then<br />
<br />
* We should have better ways of evaluating the efficiency and suitability of keyboard layouts<br />
<br />
* The Windows keyboard layout is listed under Romanian (Moldova) due to system limitations (i.e., there is no Rohingya option in the language field of Microsoft Keyboard Layout Creator, so I just went with a completely unrelated language whose name also happens to begin with "Ro")<br />
<br />
* You have to change a random obscure setting to get the layout to show up in Windows 10 (this is detailed in the INSTALL file)<br />
<br />
* Should retired/variant glyphs be included in the keyboard? Pandey's proposed Unicode block includes several characters that are stylistic variants or no longer used<br />
<br />
* Danger of appearing to promote one script over the other<br />
<br />
* Should vowel signs be more accessible? Although they are not considered full letters, they are obligatory, unlike in Arabic<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7724Cdalton2/Final project2018-05-12T18:12:24Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Measuring the efficiency of a layout directly appears to be quite difficult, especially in the absence of a collaborator who can read and type the language and script for which the layout was designed. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
* Does the layout contain the necessary characters for writing in the language? '''Yes'''<br />
<br />
* Is the layout sensibly organized (i.e., all numbers on the same row)? '''Yes'''<br />
<br />
* Does the layout resemble layouts the population might already be familiar with? '''Judging from low literacy rates, most Rohingya are likely not familiar with any keyboard layouts'''<br />
<br />
* Does the layout avoid sensitive political implications? '''At least moreso than basing it on Bangla or Burmese (implying that Rohingya is just a variety of Bangla would be bad because that's one of the arguments the Myanmar government and others have used to assert that the Rohingya are illegal interlopers from Bangladesh)'''<br />
<br />
* Does the layout offer easy access to frequently-used characters? '''Yes, comma and period are accessible with one keystroke (that said, I don't have data about which Hanifi letters are most common in Rohingya texts)'''<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7723Cdalton2/Final project2018-05-12T18:02:56Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7722Cdalton2/Final project2018-05-12T18:02:45Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[[https://github.com/cmdalton/rhg-keyboard The keyboard layouts are currently available on Github.]]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7721Cdalton2/Final project2018-05-12T18:02:18Z<p>Cdalton2: </p>
<hr />
<div>== Outline ==<br />
<br />
For my final project, I created a suite of Windows, Mac, and Linux keyboard layouts for the Rohingya Hanifi script. I felt this project could be useful to the community because the Rohingya are currently a displaced refugee population with very low literacy rates. A keyboard layout could make literacy (and computer literacy) education easier, as well as lightening the load on Rohingya interpreters, who, according to Translators without Borders, are in high demand right now and often work in stressful and even traumatizing conditions.<br />
<br />
[[The keyboard layouts are currently available on Github. https://github.com/cmdalton/rhg-keyboard]]<br />
<br />
== Evaluation ==<br />
<br />
Evaluating my project was not straightforward because I could not locate a standard set of criteria as to what constitutes a successful keyboard layout. Instead, I decided to propose some criteria of my own and then consider how well my layout fulfills them. These are just preliminary guidelines, and I hope others will expand upon them in the future.<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7720Cdalton2/Final project2018-05-12T17:53:29Z<p>Cdalton2: </p>
<hr />
<div>https://github.com/cmdalton/rhg-keyboard<br />
<br />
[[Category:Sp18_FinalProjects]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7719Cdalton2/Final project2018-05-12T17:53:17Z<p>Cdalton2: </p>
<hr />
<div>https://github.com/cmdalton/rhg-keyboard<br />
<br />
[Category:Sp18_FinalProjects]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7718Cdalton2/Final project2018-05-12T17:53:09Z<p>Cdalton2: </p>
<hr />
<div>https://github.com/cmdalton/rhg-keyboard<br />
<br />
[Category: Sp18_FinalProjects]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Cdalton2/Final_project&diff=7715Cdalton2/Final project2018-05-12T01:25:05Z<p>Cdalton2: Created page with "https://github.com/cmdalton/rhg-keyboard"</p>
<hr />
<div>https://github.com/cmdalton/rhg-keyboard</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek&diff=7687Uzbek2018-05-03T13:57:02Z<p>Cdalton2: </p>
<hr />
<div>[https://wikis.swarthmore.edu/ling073/Uzbek/Universal_Dependencies Universal Dependencies]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek&diff=7686Uzbek2018-05-03T13:56:38Z<p>Cdalton2: </p>
<hr />
<div>[https://wikis.swarthmore.edu/ling073/Uzbek/Universal_Dependencies/ Universal Dependencies]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek&diff=7685Uzbek2018-05-03T13:56:19Z<p>Cdalton2: Created page with "https://wikis.swarthmore.edu/ling073/Uzbek/Universal Dependencies/ Universal Dependencies"</p>
<hr />
<div>[[https://wikis.swarthmore.edu/ling073/Uzbek/Universal Dependencies/ Universal Dependencies]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7684Uzbek/Universal Dependencies2018-05-03T13:54:49Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || UAS: 42.98%, LAS: 35.09%<br />
|-<br />
! uzb.nomorph.udpipe<br />
| UAS: 72.11%, LAS: 69.72%<br />
| UAS: 43.86%, LAS: 35.09%<br />
|}<br />
<br />
=== uzb.annotated.ud.connlu ===<br />
<br />
forms: 251<br />
<br />
sentences: 30<br />
<br />
=== uzb.annotated2.ud.connlu ===<br />
<br />
forms: 114<br />
<br />
sentences: 9<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
=== @obj ===<br />
<br />
@obj is usually applied to a patient-like constituent. In Uzbek, the constituent designated @obj will often be a noun in the accusative case. This is seen in the sentence below from our corpus.<br />
<br />
<code><br />
"<Ushbu>"<br />
<br />
"ushbu" prn dem nom @det #1->2<br />
<br />
"<gumbazni>"<br />
<br />
"gumbaz" n acc @obj #2->7<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @advmod #3->7<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #4->7<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @xcomp #5->7<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #6->7<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @root #7->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #8->7<br />
</code><br />
<br />
''Ushbu gumbazni esa Xudo osmon deb atadi.''<br />
<br />
This dome whereas God heaven that called.<br />
<br />
"God called the expanse heaven."<br />
<br />
However, sometimes the @obj can be in other cases. In the sentence below, the obj ''suvlarning'' "waters" is in the genitive case.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->5<br />
<br />
"<quruqlikni>"<br />
<br />
"quruqlik" n acc @obj #2->5<br />
<br />
"<yer>"<br />
<br />
"yer" n nom @xcomp #3->5<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #4->5<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @root #5->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #6->12<br />
<br />
"<suvlarning>"<br />
<br />
"suv" n pl gen @obj #7->12<br />
<br />
"<jamini>"<br />
<br />
"jami" adj subst acc @nmod #8->7<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @advmod #9->12<br />
<br />
"<dengizlar>"<br />
<br />
"dengiz" n pl nom @xcomp #10->12<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #11->12<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @conj #12->5<br />
<br />
"<.>"<br />
<br />
"." sent @punct #13->5<br />
</code><br />
<br />
''Xudo quruqlikni yer deb atadi, suvlarning jamini esa dengizlar deb atadi.''<br />
<br />
God land earth that called, waters gathering whereas sea that called.<br />
<br />
"God called the dry land earth, and the gathering of the waters He called seas."<br />
<br />
=== @parataxis ===<br />
<br />
@parataxis is the relationship between the main predicate of a sentence and other elements "placed side by side without any explicit coordination, subordination, or argument relation with the head word." Parataxis is used in a variety of situations where the relationship between main sentence and clause is not explicit, especially in direct or reported speech (and so can often be identified w/ punctuation like ";" or ":"). @parataxis can be contrasted against @ccomp, which is used when the reported speech is clearly in a subordinate clause of the main verb. We used @parataxis to identify reported speech in our corpus.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->8<br />
<br />
"<:>"<br />
<br />
":" sent @punct #2->8<br />
<br />
"<«>"<br />
<br />
"«" lquot @punct #3->5<br />
<br />
"<Yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #4->5<br />
<br />
"<bo‘lsin>"<br />
<br />
"bo'l" v tv perm @parataxis #5->8<br />
<br />
"<»>"<br />
<br />
"»" rquot @punct #6->5<br />
<br />
"<,>"<br />
<br />
"," cm @punct #7->8<br />
<br />
"<dedi>"<br />
<br />
"de" v tv past p3 sg @root #8->0<br />
<br />
"<va>"<br />
<br />
"va" cnjcoo @cc #9->12<br />
<br />
"<yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #10->12<br />
<br />
"<paydo>"<br />
<br />
"paydo" adj @nmod #11->10<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #12->8<br />
<br />
"<.>"<br />
<br />
"." sent @punct #13->8<br />
<br />
</code><br />
<br />
@Parataxis is especially helpful in these examples because the syntax of reported speech in Uzbek is even less coordinated than in English: the sentence begins with the speaker, launches into the reported speech, and we only get the speaking verb at the end of the sentence. <br />
<br />
<code><br />
<br />
"<Yana>"<br />
<br />
"yana" adv @advmod #1->17<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->17<br />
<br />
"<:>"<br />
<br />
":" sent @punct #3->17<br />
<br />
"<«>"<br />
<br />
"«" lquot @punct #4->13<br />
<br />
"<Suvliklar>"<br />
<br />
"suv" n loc @nmod #5->11<br />
<br />
"<o‘rtasida>"<br />
<br />
"o'rta" n px3sp loc @case #6->5<br />
<br />
"<ularni>"<br />
<br />
"ular" prn pers p3 pl acc @obj #7->9<br />
<br />
"<bir-biridan>"<br />
<br />
"bir-bir" prn ind px3sp abl @nmod #8->7<br />
<br />
"<ajratib>"<br />
<br />
"ajra" v iv past p3 sg @acl #9->11<br />
<br />
"<turadigan>"<br />
<br />
"tur" v iv past p3 sg @conj #10->9<br />
<br />
"<gumbaz>"<br />
<br />
"gumbaz" n nom @nsubj #11->13<br />
<br />
"<paydo>"<br />
<br />
"paydo" adj @nmod #12->11<br />
<br />
"<bo‘lsin>"<br />
<br />
"bo'l" v tv perm @parataxis #13->17<br />
<br />
<br />
"<»>"<br />
<br />
"»" rquot @punct #14->13<br />
<br />
"<,>"<br />
<br />
"," cm @punct #15->17<br />
<br />
"<–>"<br />
<br />
"-" guio @punct #16->17<br />
<br />
"<dedi>"<br />
<br />
"de" v tv past p3 sg @root #17->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #18->17<br />
<br />
</code><br />
<br />
We also have examples where @acl (clausal modifiers of nouns) are embedded within @parataxis. Which brings us to our next point...<br />
<br />
=== @acl ===<br />
<br />
We used @acl <br />
<br />
=== @cc ===<br />
<br />
@cc links a coordinating conjunction to the conjunct that comes after it. In Uzbek, one common coordinating conjunction is ''va'', which appears in the sentence below.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->8<br />
<br />
"<:>"<br />
<br />
":" sent @punct #2->8<br />
<br />
"<«>"<br />
<br />
"«" lquot @punct #3->5<br />
<br />
"<Yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #4->5<br />
<br />
"<bo‘lsin>"<br />
<br />
"bo'l" v tv perm @parataxis #5->8<br />
<br />
"<»>"<br />
<br />
"»" rquot @punct #6->5<br />
<br />
"<,>"<br />
<br />
"," cm @punct #7->8<br />
<br />
"<dedi>"<br />
<br />
"de" v tv past p3 sg @root #8->0<br />
<br />
"<va>"<br />
<br />
"va" cnjcoo @cc #9->12<br />
<br />
"<yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #10->12<br />
<br />
"<paydo>"<br />
<br />
"paydo" adj @nmod #11->10<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #12->8<br />
<br />
"<.>"<br />
<br />
"." sent @punct #13->8<br />
<br />
</code><br />
<br />
''Xudo: "Yorug'lik bo'lsin", dedi va yorug'lik paydo bo'ldi.''<br />
<br />
God: "Light be", said and light appear did.<br />
<br />
"God said, 'Let there be light,' and there was light."<br />
<br />
This ''va'' isn't in the CTILD dictionary, but based on this sentence, it seems to mean something like "and." Another common @cc is ''esa'' "whereas":<br />
<br />
<code><br />
"<Xudoning>"<br />
<br />
"xudo" n gen @nmod #1->2<br />
<br />
"<Ruhi>"<br />
<br />
"ruh" n px3sp nom @root #2->0<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @cc #3->2<br />
<br />
"<suv>"<br />
<br />
"suv" n nom @nmod #4->6<br />
<br />
"<yuzida>"<br />
<br />
"yuz" num subst px3sp loc @case #5->4<br />
<br />
"<parvoz>"<br />
<br />
"parvoz" n nom @nsubj #6->2<br />
<br />
"<etar>"<br />
<br />
"etar" v tv past p3 sg @aux #7->8<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #8->2<br />
<br />
"<.>"<br />
<br />
"." sent @punct #9->2<br />
</code><br />
<br />
''Xudoning Ruhi esa suv yuzida parvoz etar edi.''<br />
<br />
God's Spirit whereas water face flight did was.<br />
<br />
"And the spirit of God was hovering over the surface of the waters."<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7683Uzbek/Universal Dependencies2018-05-02T23:36:50Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || UAS: 42.98%, LAS: 35.09%<br />
|-<br />
! uzb.nomorph.udpipe<br />
| UAS: 72.11%, LAS: 69.72%<br />
| UAS: 43.86%, LAS: 35.09%<br />
|}<br />
<br />
=== uzb.annotated.ud.connlu ===<br />
<br />
forms: 251<br />
<br />
sentences: 30<br />
<br />
=== uzb.annotated2.ud.connlu ===<br />
<br />
forms: 114<br />
<br />
sentences: 9<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
=== @obj ===<br />
<br />
@obj is usually applied to a patient-like constituent. In Uzbek, the constituent designated @obj will often be a noun in the accusative case. This is seen in the sentence below from our corpus.<br />
<br />
<code><br />
"<Ushbu>"<br />
<br />
"ushbu" prn dem nom @det #1->2<br />
<br />
"<gumbazni>"<br />
<br />
"gumbaz" n acc @obj #2->7<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @advmod #3->7<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #4->7<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @xcomp #5->7<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #6->7<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @root #7->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #8->7<br />
</code><br />
<br />
''Ushbu gumbazni esa Xudo osmon deb atadi.''<br />
<br />
This dome whereas God heaven that called.<br />
<br />
"God called the expanse heaven."<br />
<br />
However, sometimes the @obj can be in other cases. In the sentence below, the obj ''suvlarning'' "waters" is in the genitive case.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->5<br />
<br />
"<quruqlikni>"<br />
<br />
"quruqlik" n acc @obj #2->5<br />
<br />
"<yer>"<br />
<br />
"yer" n nom @xcomp #3->5<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #4->5<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @root #5->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #6->12<br />
<br />
"<suvlarning>"<br />
<br />
"suv" n pl gen @obj #7->12<br />
<br />
"<jamini>"<br />
<br />
"jami" adj subst acc @nmod #8->7<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @advmod #9->12<br />
<br />
"<dengizlar>"<br />
<br />
"dengiz" n pl nom @xcomp #10->12<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #11->12<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @conj #12->5<br />
<br />
"<.>"<br />
<br />
"." sent @punct #13->5<br />
</code><br />
<br />
''Xudo quruqlikni yer deb atadi, suvlarning jamini esa dengizlar deb atadi.''<br />
<br />
God land earth that called, waters gathering whereas sea that called.<br />
<br />
"God called the dry land earth, and the gathering of the waters He called seas."<br />
<br />
=== @parataxis ===<br />
<br />
@parataxis is the relationship between the main predicate of a sentence and other elements "placed side by side without any explicit coordination, subordination, or argument relation with the head word." Parataxis is used in a variety of situations where the relationship between main sentence and clause is not explicit, especially in direct or reported speech (and so can often be identified w/ punctuation like ";" or ":"). @parataxis can be contrasted against @ccomp, which is used when the reported speech is clearly in a subordinate clause of the main verb. We used @parataxis to identify reported speech in our corpus.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->8<br />
<br />
"<:>"<br />
<br />
":" sent @punct #2->8<br />
<br />
"<«>"<br />
<br />
"«" lquot @punct #3->5<br />
<br />
"<Yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #4->5<br />
<br />
"<bo‘lsin>"<br />
<br />
"bo'l" v tv perm @parataxis #5->8<br />
<br />
"<»>"<br />
<br />
"»" rquot @punct #6->5<br />
<br />
"<,>"<br />
<br />
"," cm @punct #7->8<br />
"<dedi>"<br />
"de" v tv past p3 sg @root #8->0<br />
"<va>"<br />
"va" cnjcoo @cc #9->12<br />
"<yorug‘lik>"<br />
"yorug'lik" n nom @nsubj #10->12<br />
"<paydo>"<br />
"paydo" adj @nmod #11->10<br />
"<bo‘ldi>"<br />
"bo'l" v tv past p3 sg @conj #12->8<br />
"<.>"<br />
"." sent @punct #13->8<br />
</code><br />
<br />
@Parataxis is especially helpful in these examples because the syntax of reported speech in Uzbek is even less coordinated than in English: the sentence begins with the speaker, launches into the reported speech, and we only get the speaking verb at the end of the sentence. <br />
<br />
<code><br />
"<Yana>"<br />
"yana" adv @advmod #1->17<br />
"<Xudo>"<br />
"xudo" n nom @nsubj #2->17<br />
"<:>"<br />
":" sent @punct #3->17<br />
"<«>"<br />
"«" lquot @punct #4->13<br />
"<Suvliklar>"<br />
"suv" n loc @nmod #5->11<br />
"<o‘rtasida>"<br />
"o'rta" n px3sp loc @case #6->5<br />
"<ularni>"<br />
"ular" prn pers p3 pl acc @obj #7->9<br />
"<bir-biridan>"<br />
"bir-bir" prn ind px3sp abl @nmod #8->7<br />
"<ajratib>"<br />
"ajra" v iv past p3 sg @acl #9->11<br />
"<turadigan>"<br />
"tur" v iv past p3 sg @conj #10->9<br />
"<gumbaz>"<br />
"gumbaz" n nom @nsubj #11->13<br />
"<paydo>"<br />
"paydo" adj @nmod #12->11<br />
"<bo‘lsin>"<br />
"bo'l" v tv perm @parataxis #13->17<br />
"<»>"<br />
"»" rquot @punct #14->13<br />
"<,>"<br />
"," cm @punct #15->17<br />
"<–>"<br />
"-" guio @punct #16->17<br />
"<dedi>"<br />
"de" v tv past p3 sg @root #17->0<br />
"<.>"<br />
"." sent @punct #18->17<br />
</code><br />
<br />
We also have examples where @acl (clausal modifiers of nouns) are embedded within @parataxis. Which brings us to our next point...<br />
<br />
=== @acl ===<br />
<br />
We used @acl <br />
<br />
=== @cc ===<br />
<br />
@cc links a coordinating conjunction to the conjunct that comes after it. In Uzbek, one common coordinating conjunction is ''va'', which appears in the sentence below.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->8<br />
<br />
"<:>"<br />
<br />
":" sent @punct #2->8<br />
<br />
"<«>"<br />
<br />
"«" lquot @punct #3->5<br />
<br />
"<Yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #4->5<br />
<br />
"<bo‘lsin>"<br />
<br />
"bo'l" v tv perm @parataxis #5->8<br />
<br />
"<»>"<br />
<br />
"»" rquot @punct #6->5<br />
<br />
"<,>"<br />
<br />
"," cm @punct #7->8<br />
<br />
"<dedi>"<br />
<br />
"de" v tv past p3 sg @root #8->0<br />
<br />
"<va>"<br />
<br />
"va" cnjcoo @cc #9->12<br />
<br />
"<yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #10->12<br />
<br />
"<paydo>"<br />
<br />
"paydo" adj @nmod #11->10<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #12->8<br />
<br />
"<.>"<br />
<br />
"." sent @punct #13->8<br />
<br />
</code><br />
<br />
''Xudo: "Yorug'lik bo'lsin", dedi va yorug'lik paydo bo'ldi.''<br />
<br />
God: "Light be", said and light appear did.<br />
<br />
"God said, 'Let there be light,' and there was light."<br />
<br />
This ''va'' isn't in the CTILD dictionary, but based on this sentence, it seems to mean something like "and." Another common @cc is ''esa'' "whereas":<br />
<br />
<code><br />
"<Xudoning>"<br />
<br />
"xudo" n gen @nmod #1->2<br />
<br />
"<Ruhi>"<br />
<br />
"ruh" n px3sp nom @root #2->0<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @cc #3->2<br />
<br />
"<suv>"<br />
<br />
"suv" n nom @nmod #4->6<br />
<br />
"<yuzida>"<br />
<br />
"yuz" num subst px3sp loc @case #5->4<br />
<br />
"<parvoz>"<br />
<br />
"parvoz" n nom @nsubj #6->2<br />
<br />
"<etar>"<br />
<br />
"etar" v tv past p3 sg @aux #7->8<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #8->2<br />
<br />
"<.>"<br />
<br />
"." sent @punct #9->2<br />
</code><br />
<br />
''Xudoning Ruhi esa suv yuzida parvoz etar edi.''<br />
<br />
God's Spirit whereas water face flight did was.<br />
<br />
"And the spirit of God was hovering over the surface of the waters."<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=User:Cdalton2&diff=7664User:Cdalton22018-05-01T15:28:50Z<p>Cdalton2: </p>
<hr />
<div>Hello! My name is Courtney Dalton. I'm a junior linguistics major at Bryn Mawr. I've taken Intro to Computing and I work with the Digital Scholarship department at BMC, but I don't have a lot of experience with computer science otherwise. Here are some languages that I would be interested in working on:<br />
<br />
* Uyghur<br />
* Tibetan<br />
* Bangla<br />
* Maltese<br />
<br />
'S-suffixes: Long Form':<br />
ܦܵܬܚ<vblex><pres><p1><f><sg>:<br />
- ܦܵܬܚܵܢܵܐ<br />
ܦܵܬܚ<vblex><pres><p1><m><sg>:<br />
- ܦܵܬܚܝܼܢܵܐ<br />
ܦܵܬܚ<vblex><pres><p1><pl>:<br />
- ܦܵܬܚܵܚܹܢ<br />
ܦܵܬܚ<vblex><pres><p2><f><sg>:<br />
- ܦܵܬܚܵܬܹܢ<br />
ܦܵܬܚ<vblex><pres><p2><m><sg>:<br />
- ܦܵܬܚܝܼܬܹܢ<br />
ܦܵܬܚ<vblex><pres><p2><pl>:<br />
- ܦܵܬܚܝܼܬܘܼܢ<br />
ܦܵܬܚ<vblex><pres><p3><f><sg>:<br />
- ܦܵܬܚܵܢܝܼ<br />
ܦܵܬܚ<vblex><pres><p3><m><sg>:<br />
- ܦܵܬܚܢܝܼ<br />
ܦܵܬܚ<vblex><pres><p3><pl>:<br />
- ܦܵܬܚܝܼܢܝܼ<br />
<br />
<br />
=== @cc ===<br />
<br />
@cc links a coordinating conjunction to the conjunct that comes after it. In Uzbek, one common coordinating conjunction is ''va'', which appears in the sentence below.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->8<br />
<br />
"<:>"<br />
<br />
":" sent @punct #2->8<br />
<br />
"<«>"<br />
<br />
"«" lquot @punct #3->5<br />
<br />
"<Yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #4->5<br />
<br />
"<bo‘lsin>"<br />
<br />
"bo'l" v tv perm @parataxis #5->8<br />
<br />
"<»>"<br />
<br />
"»" rquot @punct #6->5<br />
<br />
"<,>"<br />
<br />
"," cm @punct #7->8<br />
<br />
"<dedi>"<br />
<br />
"de" v tv past p3 sg @root #8->0<br />
<br />
"<va>"<br />
<br />
"va" cnjcoo @cc #9->12<br />
<br />
"<yorug‘lik>"<br />
<br />
"yorug'lik" n nom @nsubj #10->12<br />
<br />
"<paydo>"<br />
<br />
"paydo" adj @nmod #11->10<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #12->8<br />
<br />
"<.>"<br />
<br />
"." sent @punct #13->8<br />
<br />
</code><br />
<br />
''Xudo: "Yorug'lik bo'lsin", dedi va yorug'lik paydo bo'ldi.''<br />
<br />
God: "Light be", said and light appear did.<br />
<br />
"God said, 'Let there be light,' and there was light."<br />
<br />
This ''va'' isn't in the CTILD dictionary, but based on this sentence, it seems to mean something like "and." Another common @cc is ''esa'' "whereas":<br />
<br />
<code><br />
"<Xudoning>"<br />
<br />
"xudo" n gen @nmod #1->2<br />
<br />
"<Ruhi>"<br />
<br />
"ruh" n px3sp nom @root #2->0<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @cc #3->2<br />
<br />
"<suv>"<br />
<br />
"suv" n nom @nmod #4->6<br />
<br />
"<yuzida>"<br />
<br />
"yuz" num subst px3sp loc @case #5->4<br />
<br />
"<parvoz>"<br />
<br />
"parvoz" n nom @nsubj #6->2<br />
<br />
"<etar>"<br />
<br />
"etar" v tv past p3 sg @aux #7->8<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #8->2<br />
<br />
"<.>"<br />
<br />
"." sent @punct #9->2<br />
</code><br />
<br />
''Xudoning Ruhi esa suv yuzida parvoz etar edi.''<br />
<br />
God's Spirit whereas water face<br />
<br />
[[Category:sp18_students]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=User:Cdalton2&diff=7662User:Cdalton22018-05-01T15:15:46Z<p>Cdalton2: </p>
<hr />
<div>Hello! My name is Courtney Dalton. I'm a junior linguistics major at Bryn Mawr. I've taken Intro to Computing and I work with the Digital Scholarship department at BMC, but I don't have a lot of experience with computer science otherwise. Here are some languages that I would be interested in working on:<br />
<br />
* Uyghur<br />
* Tibetan<br />
* Bangla<br />
* Maltese<br />
<br />
'S-suffixes: Long Form':<br />
ܦܵܬܚ<vblex><pres><p1><f><sg>:<br />
- ܦܵܬܚܵܢܵܐ<br />
ܦܵܬܚ<vblex><pres><p1><m><sg>:<br />
- ܦܵܬܚܝܼܢܵܐ<br />
ܦܵܬܚ<vblex><pres><p1><pl>:<br />
- ܦܵܬܚܵܚܹܢ<br />
ܦܵܬܚ<vblex><pres><p2><f><sg>:<br />
- ܦܵܬܚܵܬܹܢ<br />
ܦܵܬܚ<vblex><pres><p2><m><sg>:<br />
- ܦܵܬܚܝܼܬܹܢ<br />
ܦܵܬܚ<vblex><pres><p2><pl>:<br />
- ܦܵܬܚܝܼܬܘܼܢ<br />
ܦܵܬܚ<vblex><pres><p3><f><sg>:<br />
- ܦܵܬܚܵܢܝܼ<br />
ܦܵܬܚ<vblex><pres><p3><m><sg>:<br />
- ܦܵܬܚܢܝܼ<br />
ܦܵܬܚ<vblex><pres><p3><pl>:<br />
- ܦܵܬܚܝܼܢܝܼ<br />
<br />
<br />
=== @cc ===<br />
<br />
@cc links a coordinating conjunction to the conjunct that comes after it. In Uzbek, one common coordinating conjunction is ''bilan'', which basically means "and, with." ''Bilan'' appears in the sentence below.<br />
<br />
<br />
[[Category:sp18_students]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7661Uzbek/Universal Dependencies2018-05-01T04:38:37Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || UAS: 42.98%, LAS: 35.09%<br />
|-<br />
! uzb.nomorph.udpipe<br />
| UAS: 72.11%, LAS: 69.72%<br />
| UAS: 43.86%, LAS: 35.09%<br />
|}<br />
<br />
=== uzb.annotated.ud.connlu ===<br />
<br />
forms: 251<br />
<br />
sentences: 30<br />
<br />
=== uzb.annotated2.ud.connlu ===<br />
<br />
forms: 114<br />
<br />
sentences: 9<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
=== @obj ===<br />
<br />
@obj is usually applied to a patient-like constituent. In Uzbek, the constituent designated @obj will often be a noun in the accusative case. This is seen in the sentence below from our corpus.<br />
<br />
<code><br />
"<Ushbu>"<br />
<br />
"ushbu" prn dem nom @det #1->2<br />
<br />
"<gumbazni>"<br />
<br />
"gumbaz" n acc @obj #2->7<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @advmod #3->7<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #4->7<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @xcomp #5->7<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #6->7<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @root #7->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #8->7<br />
</code><br />
<br />
''Ushbu gumbazni esa Xudo osmon deb atadi.''<br />
<br />
This dome whereas God heaven that called.<br />
<br />
"God called the expanse heaven."<br />
<br />
However, sometimes the @obj can be in other cases. In the sentence below, the obj ''suvlarning'' "waters" is in the genitive case.<br />
<br />
<code><br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #1->5<br />
<br />
"<quruqlikni>"<br />
<br />
"quruqlik" n acc @obj #2->5<br />
<br />
"<yer>"<br />
<br />
"yer" n nom @xcomp #3->5<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #4->5<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @root #5->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #6->12<br />
<br />
"<suvlarning>"<br />
<br />
"suv" n pl gen @obj #7->12<br />
<br />
"<jamini>"<br />
<br />
"jami" adj subst acc @nmod #8->7<br />
<br />
"<esa>"<br />
<br />
"esa" cnjcoo @advmod #9->12<br />
<br />
"<dengizlar>"<br />
<br />
"dengiz" n pl nom @xcomp #10->12<br />
<br />
"<deb>"<br />
<br />
"deb" cnjsub @advmod #11->12<br />
<br />
"<atadi>"<br />
<br />
"ata" v tv past p3 sg @conj #12->5<br />
<br />
"<.>"<br />
<br />
"." sent @punct #13->5<br />
</code><br />
<br />
''Xudo quruqlikni yer deb atadi, suvlarning jamini esa dengizlar deb atadi.''<br />
<br />
God land earth that called, waters gathering whereas sea that called.<br />
<br />
"God called the dry land earth, and the gathering of the waters He called seas."<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7660Uzbek/Universal Dependencies2018-05-01T04:37:16Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || UAS: 42.98%, LAS: 35.09%<br />
|-<br />
! uzb.nomorph.udpipe<br />
| UAS: 72.11%, LAS: 69.72%<br />
| UAS: 43.86%, LAS: 35.09%<br />
|}<br />
<br />
=== uzb.annotated.ud.connlu ===<br />
<br />
forms: 251<br />
<br />
sentences: 30<br />
<br />
=== uzb.annotated2.ud.connlu ===<br />
<br />
forms: 114<br />
<br />
sentences: 9<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
=== @obj ===<br />
<br />
@obj is usually applied to a patient-like constituent. In Uzbek, the constituent designated @obj will often be a noun in the accusative case. This is seen in the sentence below from our corpus.<br />
<br />
"<Ushbu>"<br />
"ushbu" prn dem nom @det #1->2<br />
"<gumbazni>"<br />
"gumbaz" n acc @obj #2->7<br />
"<esa>"<br />
"esa" cnjcoo @advmod #3->7<br />
"<Xudo>"<br />
"xudo" n nom @nsubj #4->7<br />
"<osmon>"<br />
"osmon" n nom @xcomp #5->7<br />
"<deb>"<br />
"deb" cnjsub @advmod #6->7<br />
"<atadi>"<br />
"ata" v tv past p3 sg @root #7->0<br />
"<.>"<br />
"." sent @punct #8->7<br />
<br />
''Ushbu gumbazni esa Xudo osmon deb atadi.''<br />
<br />
This dome whereas God heaven that called.<br />
<br />
"God called the expanse heaven."<br />
<br />
However, sometimes the @obj can be in other cases. In the sentence below, the obj ''suvlarning'' "waters" is in the genitive case.<br />
<br />
"<Xudo>"<br />
"xudo" n nom @nsubj #1->5<br />
"<quruqlikni>"<br />
"quruqlik" n acc @obj #2->5<br />
"<yer>"<br />
"yer" n nom @xcomp #3->5<br />
"<deb>"<br />
"deb" cnjsub @advmod #4->5<br />
"<atadi>"<br />
"ata" v tv past p3 sg @root #5->0<br />
"<,>"<br />
"," cm @cc #6->12<br />
"<suvlarning>"<br />
"suv" n pl gen @obj #7->12<br />
"<jamini>"<br />
"jami" adj subst acc @nmod #8->7<br />
"<esa>"<br />
"esa" cnjcoo @advmod #9->12<br />
"<dengizlar>"<br />
"dengiz" n pl nom @xcomp #10->12<br />
"<deb>"<br />
"deb" cnjsub @advmod #11->12<br />
"<atadi>"<br />
"ata" v tv past p3 sg @conj #12->5<br />
"<.>"<br />
"." sent @punct #13->5<br />
<br />
''Xudo quruqlikni yer deb atadi, suvlarning jamini esa dengizlar deb atadi.''<br />
<br />
God land earth that called, waters gathering whereas sea that called.<br />
<br />
"God called the dry land earth, and the gathering of the waters He called seas."<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7659Uzbek/Universal Dependencies2018-05-01T04:14:38Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || UAS: 42.98%, LAS: 35.09%<br />
|-<br />
! uzb.nomorph.udpipe<br />
| UAS: 72.11%, LAS: 69.72%<br />
| UAS: 43.86%, LAS: 35.09%<br />
|}<br />
<br />
=== uzb.annotated.ud.connlu ===<br />
<br />
forms: 251<br />
<br />
sentences: 30<br />
<br />
=== uzb.annotated2.ud.connlu ===<br />
<br />
forms: 114<br />
<br />
sentences: 9<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7658Uzbek/Universal Dependencies2018-05-01T04:10:10Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || UAS: 42.98%, LAS: 35.09%<br />
|-<br />
! uzb.nomorph.udpipe<br />
| UAS: 72.11%, LAS: 69.72%<br />
| UAS: 43.86%, LAS: 35.09%<br />
|}<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7657Uzbek/Universal Dependencies2018-05-01T03:58:51Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || Cell 3<br />
|-<br />
! uzb.nomorph.udpipe<br />
| UAS: 72.11%, LAS: 69.72%<br />
| Cell C<br />
|}<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7656Uzbek/Universal Dependencies2018-05-01T03:49:12Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.conllu<br />
! uzb.annotated2.ud.conllu<br />
|-<br />
! uzb.withmorph.udpipe<br />
| UAS: 82.07%, LAS: 79.68% || Cell 3<br />
|-<br />
! uzb.nomorph.udpipe<br />
| Cell B<br />
| Cell C<br />
|}<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7655Uzbek/Universal Dependencies2018-05-01T03:48:30Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! <br />
! uzb.annotated.ud.txt<br />
! uzb.annotated2.ud.txt<br />
|-<br />
! uzb.withmorph.udpipe<br />
| Cell 2 || Cell 3<br />
|-<br />
! uzb.nomorph.udpipe<br />
| Cell B<br />
| Cell C<br />
|}<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7654Uzbek/Universal Dependencies2018-05-01T03:46:30Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
! Column header 1<br />
! Column header 2<br />
! Column header 3<br />
|-<br />
! Row header 1<br />
| Cell 2 || Cell 3<br />
|-<br />
! Row header A<br />
| Cell B<br />
| Cell C<br />
|}<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7653Uzbek/Universal Dependencies2018-05-01T03:46:21Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
{| class="wikitable"<br />
|+ The table's caption<br />
! Column header 1<br />
! Column header 2<br />
! Column header 3<br />
|-<br />
! Row header 1<br />
| Cell 2 || Cell 3<br />
|-<br />
! Row header A<br />
| Cell B<br />
| Cell C<br />
|}<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7652Uzbek/Universal Dependencies2018-05-01T03:21:04Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
According to both the transducer and the CTILD dictionary, ''kech'' "evening" and ''erta'' "morning" are actually adverbs, but in this sentence, they fill the role of nominal subject.<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7651Uzbek/Universal Dependencies2018-05-01T03:18:02Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
<br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech bo'ldi, erta bo'ldi - bu birinchi kun edi.''<br />
<br />
Evening was, morning was - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7650Uzbek/Universal Dependencies2018-05-01T03:16:53Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action. An example of @nsubj can be seen in the following sentence from our corpus.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
Note that not all nouns in the nominative case are @nsubj. For some reason, ''osmon'' "heaven" in this sentence is in the nominative case even though it is an object and a patient. Perhaps the accusative ending on ''yerni'' "earth" is able to cover both conjuncts.<br />
<br />
Sometimes @nsubj can be assigned to things that are not prototypically nouns. This occurs in the following sentence.<br />
<br />
<code><br />
<br />
"<Kech>"<br />
<br />
"kech" adv subst nom @nsubj #1->2<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @root #2->0<br />
<br />
"<,>"<br />
<br />
"," cm @cc #3->5<br />
<br />
"<erta>"<br />
<br />
"erta" adv subst nom @nsubj #4->5<br />
<br />
"<bo‘ldi>"<br />
<br />
"bo'l" v tv past p3 sg @conj #5->2<br />
<br />
"<–>"<br />
<br />
"-" guio @cc #6->7<br />
<br />
"<bu>"<br />
<br />
"bu" prn dem nom @conj #7->2<br />
<br />
"<birinchi>"<br />
<br />
"bir" num ord @nmod #8->9<br />
<br />
"<kun>"<br />
<br />
"kun" n nom @nsubj #9->7<br />
<br />
"<edi>"<br />
<br />
"e" cop past p3 sg @cop #10->7<br />
<br />
"<.>"<br />
<br />
"." sent @punct #11->2<br />
<br />
</code><br />
<br />
''Kech boldi, erta boldi - bu birinchi kun edi.''<br />
<br />
Evening was.with(?), morning was.with - this first day was.<br />
<br />
"And the evening and the morning were the first day."<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7649Uzbek/Universal Dependencies2018-05-01T03:06:35Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
''Azalda Xudo osmon bilan yerni yaratdi.''<br />
<br />
In.the.beginning God heaven and earth created.<br />
<br />
"In the beginning, God created the heavens and the earth."<br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7648Uzbek/Universal Dependencies2018-05-01T03:04:08Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
[[Category: sp18_UD]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7647Uzbek/Universal Dependencies2018-05-01T03:03:49Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action.<br />
<br />
<code><br />
"<Azalda>"<br />
<br />
"azal" n loc @obl #1->6<br />
<br />
"<Xudo>"<br />
<br />
"xudo" n nom @nsubj #2->6<br />
<br />
"<osmon>"<br />
<br />
"osmon" n nom @obj #3->6<br />
<br />
"<bilan>"<br />
<br />
"bilan" cnjcoo @cc #4->5<br />
<br />
"<yerni>"<br />
<br />
"yer" n acc @conj #5->3<br />
<br />
"<yaratdi>"<br />
<br />
"yarat" v tv past p3 sg @root #6->0<br />
<br />
"<.>"<br />
<br />
"." sent @punct #7->6<br />
<br />
</code><br />
<br />
[Category: sp18_UD]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7646Uzbek/Universal Dependencies2018-05-01T03:03:25Z<p>Cdalton2: </p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==<br />
<br />
=== @nsubj ===<br />
<br />
@nsubj (nominal subject) denotes a semantically agent-like and syntactically subject-like nominal. Note that it cannot be used for pleonastic subjects.<br />
<br />
In Uzbek, @nsubj will usually be assigned to a noun in the nominative case. Generally speaking, a noun in the nominative case is the subject of the sentence and the doer of the action.<br />
<br />
<code><br />
"<Azalda>"<br />
"azal" n loc @obl #1->6<br />
"<Xudo>"<br />
"xudo" n nom @nsubj #2->6<br />
"<osmon>"<br />
"osmon" n nom @obj #3->6<br />
"<bilan>"<br />
"bilan" cnjcoo @cc #4->5<br />
"<yerni>"<br />
"yer" n acc @conj #5->3<br />
"<yaratdi>"<br />
"yarat" v tv past p3 sg @root #6->0<br />
"<.>"<br />
"." sent @punct #7->6<br />
</code><br />
<br />
[Category: sp18_UD]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Uzbek/Universal_Dependencies&diff=7645Uzbek/Universal Dependencies2018-05-01T02:39:24Z<p>Cdalton2: Created page with "== Evaluation == == Dependency relations =="</p>
<hr />
<div>== Evaluation ==<br />
<br />
== Dependency relations ==</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7633Latin and Mandarin Chinese2018-04-25T02:49:48Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
=== zho ===<br />
<br />
'''Precision and recall'''<br />
<br />
Totals: 135 forms, 356 tp, 0 fp, 0 tn, 0 fn<br />
<br />
Precision: 100.00000%<br />
<br />
Recall: 100.00000%<br />
<br />
'''Coverage over large corpus:''' 100.00%<br />
<br />
'''# of words in large corpus:''' 232,490<br />
<br />
'''# of stems in transducer:''' ~8574<br />
<br />
=== lat-zho ===<br />
<br />
'''longer corpus'''<br />
<br />
WER: 103.17%<br />
<br />
PER: 87.53%<br />
<br />
Number of words in reference: 441<br />
<br />
Number of words in test: 516<br />
<br />
Number of unknown words (marked with a star) in test: 139<br />
<br />
Percentage of unknown words: 26.94 %<br />
<br />
Trimmed coverage: 100.00%<br />
<br />
'''large corpus'''<br />
<br />
Number of tokenised words in the corpus: 4997<br />
<br />
Coverage: 40.70%<br />
<br />
Top unknown words in the corpus:<br />
<br />
95 e<br />
<br />
65 f<br />
<br />
64 The<br />
<br />
58 c<br />
<br />
50 A<br />
<br />
45 d<br />
<br />
42 C<br />
<br />
41 h<br />
<br />
37 of<br />
<br />
36 a<br />
<br />
36 b<br />
<br />
31 g<br />
<br />
29 M<br />
<br />
22 B<br />
<br />
21 AMC<br />
<br />
21 ISBN<br />
<br />
21 T<br />
<br />
20 the<br />
<br />
19 Dead<br />
<br />
18 s<br />
<br />
=== lat ===<br />
<br />
=== zho-lat ===<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7632Latin and Mandarin Chinese2018-04-25T02:49:05Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
=== zho ===<br />
<br />
'''Precision and recall'''<br />
<br />
Totals: 135 forms, 356 tp, 0 fp, 0 tn, 0 fn<br />
<br />
Precision: 100.00000%<br />
<br />
Recall: 100.00000%<br />
<br />
'''Coverage over large corpus:''' 100.00%<br />
<br />
'''# of words in large corpus:''' 232,490<br />
<br />
'''# of stems in transducer:''' ~8574<br />
<br />
=== lat-zho ===<br />
<br />
'''longer corpus'''<br />
<br />
WER: 103.17%<br />
<br />
PER: 87.53%<br />
<br />
Number of words in reference: 441<br />
<br />
Number of words in test: 516<br />
<br />
Number of unknown words (marked with a star) in test: 139<br />
<br />
Percentage of unknown words: 26.94 %<br />
<br />
Trimmed coverage: 100.00%<br />
<br />
'''large corpus'''<br />
<br />
Number of tokenised words in the corpus: 4997<br />
<br />
Coverage: 40.70%<br />
<br />
Top unknown words in the corpus:<br />
<br />
95 e<br />
<br />
65 f<br />
<br />
64 The<br />
<br />
58 c<br />
<br />
50 A<br />
<br />
45 d<br />
<br />
42 C<br />
<br />
41 h<br />
<br />
37 of<br />
<br />
36 a<br />
<br />
36 b<br />
<br />
31 g<br />
<br />
29 M<br />
<br />
22 B<br />
<br />
21 AMC<br />
<br />
21 ISBN<br />
<br />
21 T<br />
<br />
20 the<br />
<br />
19 Dead<br />
<br />
18 s<br />
<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7631Latin and Mandarin Chinese2018-04-25T02:30:18Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
=== zho ===<br />
<br />
'''Precision and recall'''<br />
<br />
Totals: 135 forms, 356 tp, 0 fp, 0 tn, 0 fn<br />
<br />
Precision: 100.00000%<br />
<br />
Recall: 100.00000%<br />
<br />
'''Coverage over large corpus:''' 100.00%<br />
<br />
'''# of words in large corpus:''' 232,490<br />
<br />
'''# of stems in transducer:''' ~8574<br />
<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7630Latin and Mandarin Chinese2018-04-25T02:09:38Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
=== zho ===<br />
<br />
'''Precision and recall'''<br />
<br />
Totals: 135 forms, 356 tp, 0 fp, 0 tn, 0 fn<br />
<br />
Precision: 100.00000%<br />
<br />
Recall: 100.00000%<br />
<br />
'''# of stems in transducer:''' ~8574<br />
<br />
'''Coverage over large corpus:''' 100.00%<br />
<br />
'''# of words in large corpus:''' 232,490<br />
<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7629Latin and Mandarin Chinese2018-04-25T02:09:13Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
=== zho ===<br />
<br />
'''Precision and recall'''<br />
<br />
Totals: 135 forms, 356 tp, 0 fp, 0 tn, 0 fn<br />
<br />
Precision: 100.00000%<br />
<br />
Recall: 100.00000%<br />
<br />
'''# of stems in transducer:''' ~8574<br />
<br />
'''Coverage over large corpus:''' 100.00%<br />
<br />
'''# of stems in large corpus:''' 232,490<br />
<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7624Latin and Mandarin Chinese2018-04-24T16:32:53Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
=== zho ===<br />
<br />
'''Precision and recall'''<br />
<br />
Totals: 135 forms, 356 tp, 0 fp, 0 tn, 0 fn<br />
<br />
Precision: 100.00000%<br />
<br />
Recall: 100.00000%<br />
<br />
'''# of stems in transducer:''' ~8574<br />
<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7623Latin and Mandarin Chinese2018-04-24T16:24:40Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
=== zho ===<br />
<br />
'''Precision and recall'''<br />
<br />
Totals: 135 forms, 356 tp, 0 fp, 0 tn, 0 fn<br />
<br />
Precision: 100.00000%<br />
<br />
Recall: 100.00000%<br />
<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7620Latin and Mandarin Chinese2018-04-24T14:50:18Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
== Final Evaluation ==<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese&diff=7611Latin and Mandarin Chinese2018-04-21T16:17:34Z<p>Cdalton2: </p>
<hr />
<div>==Resources for machine translation between [https://wikis.swarthmore.edu/ling073/Latin Latin] and [https://wikis.swarthmore.edu/ling073/Mandarin_Chinese Mandarin Chinese]==<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Lexical_selection Lexical Selection Documentation]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Structural_transfer Structural transfer]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho Machine Translator]<br />
<br />
[https://github.swarthmore.edu/cdalton2/ling073-lat-zho-corpus Parallel Corpus]<br />
<br />
[https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese/Contrastive_Grammar Contrastive Grammar]<br />
<br />
== lat → zho evaluation ==<br />
<br />
Sentences WER: 586.79%<br />
<br />
Sentences PER: 586.79%<br />
<br />
Tests WER: 609.9%<br />
<br />
Tests PER: 609.9%<br />
<br />
== zho → lat evaluation ==<br />
<br />
Sentences WER: 97.42%<br />
<br />
Sentences PER: 93.55%<br />
<br />
Tests WER: 95.45%<br />
<br />
Tests PER: 89.39%<br />
<br />
==Proportion of stems translated correctly==<br />
<br />
lat.sentences.txt: 314:173<br />
<br />
lat.tests.txt: 66:17<br />
<br />
zho.sentences.txt: 53:0<br />
<br />
zho.tests.txt: 10:0<br />
<br />
== Lexical Selection ==<br />
<br />
One case of one-to-many mapping from Chinese to Latin has to do with the preposition 在. This is a general locative preposition in Chinese, and it can be used to mean anything from 'in' to 'above' to 'outside' to 'to in front of' to 'west of.' Usually, the object of 在 is either a place word (such as 'China' or 'the library') or a word that means 'in', 'above', etc. which is then modified by a noun, resulting in a phrase sort of equivalent to "在 the inside of the box" or "在 the top of the table." In contrast, Latin has many different prepositions which specify different locational relationships to the object of the preposition, much like English.<br />
<br />
Another case has to do with pronouns; each Latin pronoun has many different forms for different cases. In contrast, in Chinese each pronoun has at most two different forms: one singular and one plural.<br />
<br />
It's a bit more difficult to find one-to-many mappings from Latin to Chinese due to the nature of the beast. However, note that Chinese is a classifier language, meaning that you need a classifier or measure word in order to couple a noun with a numeral or determiner. Different nouns can have different measure words depending on the shape of the object they represent, among other factors. This is different from Latin, in which you don't have to worry about all of these different measure words when pairing a noun with a numeral; you just have to make sure the numeral agrees with the noun in terms of gender, number, and case. In that sense, this might be considered a one-to-many mapping (and sometimes literally a "one" to many mapping).<br />
<br />
Also note that Chinese has a number of sentence-ending particles that can be used to "soften" or otherwise modulate a sentence. For example, the particle 呢 often marks a rhetorical question. In Latin, a rhetorical question would, I think, have the same form as a genuine question, making this another possible one-to-many mapping from Latin to Chinese.<br />
<br />
== Additions ==<br />
<br />
=== zho ===<br />
<br />
Added 2 new lexical selection rules<br />
<br />
Added 2 new structural transfer rules<br />
<br />
[[Category:Sp18_TranslationPairs]]</div>Cdalton2http://wikis.swarthmore.edu/ling073/index.php?title=Latin_and_Mandarin_Chinese/Structural_transfer&diff=7608Latin and Mandarin Chinese/Structural transfer2018-04-19T16:06:06Z<p>Cdalton2: </p>
<hr />
<div>This is the page for the structural transfer of Latin and Mandarin Chinese. The main page for this language pair can be found [https://wikis.swarthmore.edu/ling073/Latin_and_Mandarin_Chinese here].<br />
<br />
==Pre-evaluation==<br />
<br />
=== Latin corpus coverage ===<br />
<br />
Number of tokenised words in the corpus: 380<br />
<br />
Coverage: 88.68%<br />
<br />
Top unknown words in the corpus:<br />
<br />
2 potest<br />
<br />
2 facet<br />
<br />
2 possit<br />
<br />
2 quo<br />
<br />
1 tibi<br />
<br />
1 Mariaene<br />
<br />
1 quid<br />
<br />
1 audit<br />
<br />
1 possum<br />
<br />
1 matrae<br />
<br />
1 James<br />
<br />
1 loquent<br />
<br />
1 audire<br />
<br />
1 not<br />
<br />
1 Videbasne<br />
<br />
1 duo<br />
<br />
1 poterunt<br />
<br />
1 eae<br />
<br />
1 aliquid<br />
<br />
1 posset<br />
<br />
=== Chinese corpus coverage ===<br />
<br />
Number of tokenised words in the corpus: 447<br />
<br />
Coverage: 100.00%<br />
<br />
=== lat → zho ===<br />
<br />
WER: 586.79%<br />
<br />
PER: 586.79%<br />
<br />
=== zho → lat ===<br />
<br />
WER: 97.42%<br />
<br />
PER: 93.55%<br />
<br />
== Implementation ==<br />
<br />
=== lat → zho ===<br />
<br />
For translating into Chinese, we implemented macros that take case off of nouns and add the associative particle 的 to nouns that, in Latin, had the genitive case.<br />
<br />
''Maria caput pueri videt.''<br />
<br />
"Maria saw the boy's head."<br />
<br />
'''tagger:''' <br />
<br />
^Maria<np><ant><f><sg><nom>$ ^caput<n><nt><sg><nom>$ ^puer<n><m><sg><gen>$ ^videre<vblex><pri><act><p3><sg>$^.<sent>$<br />
<br />
'''biltrans:''' <br />
<br />
^Maria<np><ant><f><sg><nom>/小红<np><ant><f><sg><nom>$ ^caput<n><nt><sg><nom>/头<n><nt><sg><nom>$ ^puer<n><m><sg><gen>/男孩<n><m><sg><gen>$ ^videre<vblex><pri><act><p3><sg>/看到<vblex><pri><act><p3><sg>$^.<sent>/。<sent>$<br />
<br />
'''chunker:'''<br />
<br />
apertium-transfer: Rule 2 caput<n><nt><sg><nom>/头<n><nt><sg><nom><br />
<br />
apertium-transfer: Rule 2 puer<n><m><sg><gen>/男孩<n><m><sg><gen><br />
<br />
apertium-transfer: Rule 1 .<sent>/。<sent><br />
^default<default>{^小红<np><ant><f><sg><nom>$}$ ^noun<SN>{^头<n>$ }$ ^noun<SN>{^男孩<n>$ ^的<pr>$}$ ^default<default>{^看到<vblex><pri><act><p3><sg>$}$^sent<SENT>{^。<sent>$}$<br />
<br />
'''interchunk:''' <br />
<br />
Rule 1 noun<SN>{^男孩<n>$ ^的<pr>$}<br />
^default<default>{^小红<np><ant><f><sg><nom>$}$ ^noun<SN>{^头<n>$ }$ ^noun<SN>{^男孩<n>$ ^的<pr>$}$ ^default<default>{^看到<vblex><pri><act><p3><sg>$}$^sent<SENT>{^。<sent>$}$<br />
<br />
'''postchunk:''' <br />
<br />
^小红<np><ant><f><sg><nom>$ ^头<n>$ ^男孩<n>$ ^的<pr>$ ^看到<vblex><pri><act><p3><sg>$^。<sent>$<br />
<br />
'''lat-zho:''' <br />
<br />
#小红 头 男孩 的 #看到。<br />
<br />
=== zho → lat ===<br />
<br />
For translating into Latin, we implemented rules to take away the preposition 给 and change the following noun into dative case.<br />
<br />
我给狗听。<br />
<br />
"I listen for the dog (i.e., for the dog's sake/at the dog's behest)."<br />
<br />
'''tagger：''' <br />
<br />
^我<prn>$ ^给<pr>$ ^狗<n>$ ^听<vblex>$<br />
<br />
'''biltrans:''' <br />
<br />
^我<prn>/ego<prn>$ ^给<pr>/$ ^狗<n>/canis<n><m>$ ^听<vblex>/auscultare$<br />
<br />
'''chunker:''' <br />
<br />
apertium-transfer: Rule 2 给<pr>/<br />
<br />
apertium-transfer: Rule 3 狗<n>/canis<n><m><br />
^default<default>{^ego<prn>$}$ ^pr<SPR><dat>{}$ ^nom<SN><ND><CD>{^canis<n><m><2><3>$}$ ^default<default>{^auscultare$}$<br />
<br />
'''interchunk:'''<br />
<br />
apertium-interchunk: Rule 2 pr<SPR><dat>{} nom<SN><ND><CD>{^canis<n><m><2><3>$}<br />
^default<default>{^ego<prn>$}$ ^nom<SN><sg><dat>{^canis<n><m><2><3>$}$ ^default<default>{^auscultare$}$<br />
<br />
'''postchunk:'''<br />
<br />
^ego<prn>$ ^canis<n><m><sg><dat>$ ^auscultare$<br />
<br />
'''zho-lat'''<br />
<br />
#ego cani #auscultare<br />
<br />
== Post-evaluation ==<br />
<br />
=== Latin corpus coverage ===<br />
<br />
Number of tokenised words in the corpus: 380<br />
<br />
Coverage: 88.68%<br />
<br />
Top unknown words in the corpus:<br />
<br />
2 possit<br />
<br />
2 potest<br />
<br />
2 quo<br />
<br />
2 facet<br />
<br />
1 abest<br />
<br />
1 duo<br />
<br />
1 Id<br />
<br />
1 Te<br />
<br />
1 quid<br />
<br />
1 vult<br />
<br />
1 Utrique<br />
<br />
1 poterunt<br />
<br />
1 accipiunt<br />
<br />
1 se<br />
<br />
1 veta<br />
<br />
1 Scisne<br />
<br />
1 tibi<br />
<br />
1 not<br />
<br />
1 possum<br />
<br />
1 posset<br />
<br />
=== Chinese corpus coverage ===<br />
<br />
Number of tokenised words in the corpus: 447<br />
<br />
Coverage: 100.00%<br />
<br />
=== lat → zho === <br />
<br />
WER: 97.84%<br />
<br />
PER: 97.04%<br />
<br />
(after adding spaces to zho.sentences.txt)<br />
<br />
=== zho → lat ===<br />
<br />
WER: 95.45%<br />
<br />
PER: 89.39%<br />
<br />
[[Category:Sp17_StructuralTransfer]]</div>Cdalton2