Ideas for Google Summer of Code - Revision history

Unhammer at 09:15, 4 March 2024

2024-03-04T09:15:42Z

Popcorndude: length → size

2024-02-09T22:33:23Z

length → size

Show changes

Unhammer at 09:31, 6 February 2024

2024-02-06T09:31:19Z

Unhammer at 09:11, 6 February 2024

2024-02-06T09:11:50Z

Unhammer at 09:10, 6 February 2024

2024-02-06T09:10:12Z

Unhammer: Robust Recursive Transfer

2024-02-06T09:08:48Z

Robust Recursive Transfer

Tino Didriksen: Snip completed l10n/i18n

2023-10-26T11:09:23Z

Snip completed l10n/i18n

Popcorndude at 14:30, 31 March 2023

2023-03-31T14:30:27Z

Popcorndude: make description make sense

2023-03-21T20:07:33Z

make description make sense

Popcorndude: link

2023-03-07T15:45:08Z

link

@@ Line 88: / Line 88: @@
 | rationale = Currently, preferences are implemented via language variant, which relies on multiple dictionaries, increasing compilation time exponentially every time a new preference gets introduced.
 | mentors = [[User:Xavivars|Xavi Ivars]] [[User:Unhammer]]
-| more = /Use preferences in SPA-CAT
+| more = /Use preferences in pair
 }}

@@ Line 208: / Line 208: @@
 | more = /More_robust_recursive_transfer
 }}
+{{IdeaSummary
+| name = CG-based Transfer
+| difficulty = Hard
+| length = long
+| skills = C++
+| description = Linguists already write dependency trees in [[Constraint Grammar]]. A following step could use these to reorder into target language trees.
+| mentors =
+| more =
+}}
 {{IdeaSummary
 | name = Language Server Protocol

@@ Line 206: / Line 206: @@
 | rationale = Currently, one has to be very careful in writing recursive transfer rules to ensure they don't get too deep or ambiguous, and that they cover full sentences. See in particular issues [https://github.com/apertium/apertium-recursive/issues/97 97] and [https://github.com/apertium/apertium-recursive/issues/80 80]. We would like linguists to be able to fearlessly write recursive (rtx) rules based on what makes linguistic sense, and have rtx-proc/rtx-comp deal with the computational/performance side.
 | mentors =
-| more = /Robust_recursive_transfer
+| more = /More_robust_recursive_transfer
 }}
 {{IdeaSummary

@@ Line 199: / Line 199: @@
 {{IdeaSummary
-| name = Robust Recursive Transfer
+| name = More Robust Recursive Transfer
 | difficulty = Hard
 | length = long
@@ Line 206: / Line 206: @@
 | rationale = Currently, one has to be very careful in writing recursive transfer rules to ensure they don't get too deep or ambiguous, and that they cover full sentences. See in particular issues [https://github.com/apertium/apertium-recursive/issues/97 97] and [https://github.com/apertium/apertium-recursive/issues/80 80]. We would like linguists to be able to fearlessly write recursive (rtx) rules based on what makes linguistic sense, and have rtx-proc/rtx-comp deal with the computational/performance side.
 | mentors =
-| more =
+| more = /Robust_recursive_transfer
 }}
 {{IdeaSummary

@@ Line 198: / Line 198: @@
 }}
+{{IdeaSummary
+| name = Robust Recursive Transfer
+| difficulty = Hard
+| length = long
+| skills = C++
+| description = Ensure [[Apertium-recursive#Further_Documentation|Recursive Transfer]] survives ambiguous or incomplete parse trees
+| rationale = Currently, one has to be very careful in writing recursive transfer rules to ensure they don't get too deep or ambiguous, and that they cover full sentences. See in particular issues [https://github.com/apertium/apertium-recursive/issues/97 97] and [https://github.com/apertium/apertium-recursive/issues/80 80]. We would like linguists to be able to fearlessly write recursive (rtx) rules based on what makes linguistic sense, and have rtx-proc/rtx-comp deal with the computational/performance side.
+| mentors =
+| more =
+}}
 {{IdeaSummary
 | name = Language Server Protocol

@@ Line 196: / Line 196: @@
 | mentors = [[User:Popcorndude]]
 | more = /Backpropagation
-}}
-{{IdeaSummary
-| name = Localization (l10n/i18n) of Apertium tools
-| difficulty = Medium
-| length = short
-| skills = C++
-| description = All our command line tools are currently hardcoded as English-only and it would be good if this were otherwise. [https://github.com/apertium/organisation/issues/28#issuecomment-803474833 Coding Challenge]
-| rationale = ...
-| mentors = [[User:Tino_Didriksen|Tino Didriksen]]
-| more = https://github.com/apertium/organisation/issues/28 Github
 }}

@@ Line 263: / Line 263: @@
 | skills = html, css, js, python
 | description = Finish implementing dictionary lookup mode in Apertium's web infrastructure
-| rationale = Apertium's website infrastructure [[Apertium-html-tools]] and its supporting API [[APy|Apertium APy]] have numerous open issues, including half-completed features like dictionary lookup.  This project would entail completing the dictionary lookup feature.  Some additional features which would be good to work would include automatic reverse lookups (so that a user has a better understanding of the results), grammatical information (such as the gender of nouns or the conjugation paradigms of verbs), and information about MWEs.  See [https://github.com/apertium/apertium-html-tools/issues/105 the open issue on GitHub].
+| rationale = Apertium's website infrastructure [[Apertium-html-tools]] and its supporting API [[APy|Apertium APy]] have numerous open issues, including half-completed features like dictionary lookup.  This project would entail completing the dictionary lookup feature.  Some additional features which would be good to work would include automatic reverse lookups (so that a user has a better understanding of the results), grammatical information (such as the gender of nouns or the conjugation paradigms of verbs), and information about MWEs.
 | mentors = [[User:Firespeaker|Jonathan Washington]], [[User:Xavivars|Xavi Ivars]], [[User:Popcorndude]]
+| more = https://github.com/apertium/apertium-html-tools/issues/105 the open issue on GitHub
-| more = /Website improvements
 }}

@@ Line 321: / Line 321: @@
 | length = either
 | skills = JS, Python
-| description = OmniLingo is a language learning system for practicing listening comprehension using Apertium data. There is a lot of text processing involved (for example tokenisation) that could be aided by Apertium tools.
+| description = OmniLingo is a language learning system for practicing listening comprehension using Common Voice data. There is a lot of text processing involved (for example tokenisation) that could be aided by Apertium tools.
 | rationale =
 | mentors = [[User:Francis Tyers|Francis Tyers]]
@@ Line 332: / Line 332: @@
 | length = either
 | skills = NodeJS
-| description = UD Annotatrix is an annotation interface for Universal Dependencies, but does not yet support all functionality
+| description = UD Annotatrix is an annotation interface for Universal Dependencies, but does not yet support all functionality.
 | rationale =
 | mentors = [[User:Francis Tyers|Francis Tyers]]

@@ Line 335: / Line 335: @@
 | rationale =
 | mentors = [[User:Francis Tyers|Francis Tyers]]
-| more = /Morphological analyser
+| more = /Annotatrix enhanced dependencies
 }}