User:Mono/GSoC 2017

Webpage Translation mode

An interface that lets the user to input a URL, choose a source and a destination language and translate the webpage.

Code

Backend

• https://github.com/goavki/apertium-apy/commit/1f0642858ad82c6666c1b92bea1f5f65bf150c41

Documentation

Backend

URL	Function	Parameters	Output
/translatePage	Translates a webpage	langpair: language pair to use for translation url: url of webpage that has to be translated	Returns the translated webpage curl -Ss 'http://localhost:2737/translatePage?langpair=eng|spa&url=http://facebook.com' output

Frontend

ENABLED_MODES: an array of the enabled interfaces, a non-empty subset of ['translation', 'analyzation', 'generation', 'sandbox', 'lookup']

• translation lookup turns on webpage translation mode.

Future Work

1. The backend for this mode is merged in this commit. The screenshot of the current state of interface can be found here.
2. The interface is pretty much functional. However, a future task is to make use of a form handler while submitting the URL links for translation. The related issues are in this comment.

SpellChecker mode

Checks for the spelling of input text for a given language and suggests alternatives if the spelling is wrong.

Documentation

Backend

URL	Function	Parameters	Output
/speller	Performs spellchecking on a given text for a given language	lang: language to perform spellchecking for q: text to perform spellchecking on	Returns the spellchecking results curl -Ss 'curl -Ss 'http://localhost:3025/speller?lang=hin&q=माय' | ascii2uni -a U -q [{"sugg": [["काय", "1.000000"], ["चाय", "1.000000"], ["राय", "1.000000"], ["हाय", "1.000000"], ["साय", "1.000000"], ["मा", "1.000000"], ["वाय", "1.000000"], ["दाय", "1.000000"], ["गाय", "1.000000"], ["जाय", "1.000000"]], "known": false, "token": "माय"}]

Frontend

ENABLED_MODES: an array of the enabled interfaces, a non-empty subset of ['translation', 'analyzation', 'generation', 'sandbox', 'lookup', 'speller']

• speller turns on spell checking mode.

Future Work

1. The screenshot of the current state of interface can be found here.
2. Improving the logic of mapping the suggestions returned from the backend for the tokens appropriately to the corresponding text on the frontend.