Difference between revisions of "Ideas for Google Summer of Code/UD and Apertium integration"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | |||
+ | ==Tasks== |
||
+ | |||
+ | This project would involve working on a number of tasks from the following list: |
||
* [[UD annotatrix]] |
* [[UD annotatrix]] |
||
+ | ** An HTML/JS interface for treebank annotation |
||
* lttoolbox relabelling (tagset conversion) |
* lttoolbox relabelling (tagset conversion) |
||
+ | ** Seamless conversion between Apertium and UD tagsets |
||
* [[UDpipe]] --- lttoolbox integration |
* [[UDpipe]] --- lttoolbox integration |
||
+ | ** Use Apertium morphological analysers to be soft constraints on lemmatisation and POS/MSD tagging. |
||
+ | * ''Your idea(s) here'' |
||
==Coding challenge== |
==Coding challenge== |
Revision as of 14:34, 28 February 2017
Tasks
This project would involve working on a number of tasks from the following list:
- UD annotatrix
- An HTML/JS interface for treebank annotation
- lttoolbox relabelling (tagset conversion)
- Seamless conversion between Apertium and UD tagsets
- UDpipe --- lttoolbox integration
- Use Apertium morphological analysers to be soft constraints on lemmatisation and POS/MSD tagging.
- Your idea(s) here
Coding challenge
- Fix one issue in UD annotatrix and send a pull request
- Train UDpipe for a language that is also in Apertium
- Write a tagset equivalence file for a language that is in both Apertium and UD.