Difference between revisions of "User:Mono/GSoC 2017"
Line 167: | Line 167: | ||
== POST v/s GET == |
== POST v/s GET == |
||
1. Initially, the AJAX requests made use of GET method to retrieve |
1. Initially, the AJAX requests made use of GET method to retrieve data from the backend. <br/> |
||
2. The GET method was used |
2. The GET method was used along with ''jsonp'' to allow cross domain requests. However, this gave a ''414-request URI too large'' error when the input size was large and thus, resulted in failed requests. <br/> |
||
3. This was resolved by making use of POST method |
3. This issue was resolved by making use of a POST method if the request size was beyond a threshold size and GET method otherwise. |
||
=== Code === |
=== Code === |
||
* https://github.com/goavki/apertium-html-tools/commit/d40162f4c134c2b168d7f28627606d3ac7c58630 |
* https://github.com/goavki/apertium-html-tools/commit/d40162f4c134c2b168d7f28627606d3ac7c58630 |
||
== Language Dropdown going offscreen Issue == |
|||
1. The language dropdown used to go offscreen when the browser window size was adjusted. This would obstruct the user from choosing the language of his choice. <br/> |
|||
2. This issue was fixed by dynamically determining the available space on the browser window (triggered on resize) and changing the number of columns to fit the languages inside the viewport. |
|||
=== Code === |
|||
* https://github.com/goavki/apertium-html-tools/commit/b2dc0caeecd6de9dcbf855d32aa1386b5d75d233 |
|||
== LTR/RTL alignment of languages in dropdown == |
|||
1. Inspite of setting the left-to-right or right-to-left orientation for the language display names, the browser did not render it in the expected manner. <br/> |
|||
2. A patch was created which applied the necessary styling to the display names along with the styling of other associated UI elements to achieve the right behaviour. |
|||
=== Code === |
|||
* https://github.com/goavki/apertium-html-tools/pull/159 |
Revision as of 15:39, 27 August 2017
Contents
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
Frontend
- https://github.com/goavki/apertium-html-tools/pull/154
- https://github.com/goavki/apertium-html-tools/pull/202
- https://github.com/goavki/apertium-html-tools/pull/205
Documentation
Backend
URL | Function | Parameters | Output |
---|---|---|---|
/translatePage | Translates a webpage |
|
Returns the translated webpage
curl -Ss 'http://localhost:2737/translatePage?langpair=eng|spa&url=http://facebook.com' |
Frontend
ENABLED_MODES: an array of the enabled interfaces, a non-empty subset of ['translation', 'analyzation', 'generation', 'sandbox']
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.
Code
Backend
Frontend
Documentation
Backend
URL | Function | Parameters | Output |
---|---|---|---|
/speller | Performs spellchecking on a given text for a given language |
|
Returns the spellchecking results
curl -Ss 'http://localhost:2737/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', '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.
Dictionary Lookup mode
An interface that generates all forms of a given word. It renders the definitions of a given word for a given language pair after translating them.
Code
Backend
Frontend
Documentation
Backend
URL | Function | Parameters | Output |
---|---|---|---|
/dictionaryLookup | Generate dictionary forms of a given word |
|
Returns the possible forms of after translation
curl -Ss 'http://localhost:2737/dictionaryLookup?langpair=eng|spa&q=light' {"vblex": ["encender", "iluminar"], "n": ["luz"], "adj": ["ligero", "claro"]} |
Frontend
ENABLED_MODES: an array of the enabled interfaces, a non-empty subset of ['translation', 'analyzation', 'generation', 'sandbox']
translation lookup
turns on dictionary lookup mode.
Future Work
1. The screenshot of the current state of interface can be found here.
2. The pending tasks with respect to dictionary lookup mode are discussed in this comment.
Installation Notification
1. A notification that appears when the requests made to the APy take more than a threshold time.
2. This notification also appears when a cumulative average of the requests duration exceeds a certain threshold indicating that the servers may be overloaded and thus, one could set the APy locally too.
Code
POST v/s GET
1. Initially, the AJAX requests made use of GET method to retrieve data from the backend.
2. The GET method was used along with jsonp to allow cross domain requests. However, this gave a 414-request URI too large error when the input size was large and thus, resulted in failed requests.
3. This issue was resolved by making use of a POST method if the request size was beyond a threshold size and GET method otherwise.
Code
Language Dropdown going offscreen Issue
1. The language dropdown used to go offscreen when the browser window size was adjusted. This would obstruct the user from choosing the language of his choice.
2. This issue was fixed by dynamically determining the available space on the browser window (triggered on resize) and changing the number of columns to fit the languages inside the viewport.
Code
LTR/RTL alignment of languages in dropdown
1. Inspite of setting the left-to-right or right-to-left orientation for the language display names, the browser did not render it in the expected manner.
2. A patch was created which applied the necessary styling to the display names along with the styling of other associated UI elements to achieve the right behaviour.