Ideas for Google Summer of Code/Apertium website improvements
The Apertium translation website is pretty cool, but we can make it even cooler. This project consists of various website (and API) improvement tasks.
The website consists of two pieces: the front-end, html-tools, (https://github.com/apertium/apertium-html-tools) and the back-end API (https://github.com/apertium/apertium-apy) called APy. Some tasks follow and a full listing can be found on the project pages: https://github.com/apertium/apertium-html-tools/projects/1 and https://github.com/apertium/apertium-apy/projects/2.
- Add "dictionary lookup" mode for single-word translations.
- Should give synonyms and alternative translations.
- It should rank the translations by likelihood.
- Add a mode that colours the resulting translation depending on how reliable it is.
- One possibility would be for language pairs to have different colours depending on WER or something.
- Make language detection work properly and do "did you mean" style if people choose an unlikely source language.
Work in progress
Past GCI/GSoC have generated some work that just needs some polishing (e.g. last [GSoC](http://wiki.apertium.org/wiki/GSOC'16_Kira's_results._Apertium_website_improvements)). These are summarized on the project page and a few are included below.
- An "improve this translation" option https://github.com/apertium/apertium-html-tools/pull/35
- "website translation" option https://github.com/apertium/apertium-html-tools/pull/41
- Needs improvements to APY to be able to split long pages into several requests without breaking html
- Install the Apertium website with some language pairs on a server under your control, test that it works correctly. This means installing both APy and Html-tools.
- Check out the list of coding challenges found within https://github.com/apertium/apertium-html-tools/projects/1 and https://github.com/apertium/apertium-apy/projects/2.
- Send us a pull request with your code.
- Work with us to get your code merged!