Task ideas for Google Code-in/Apy pipedebug - Revision history

Unhammer at 12:52, 26 March 2015

2015-03-26T12:52:49Z

2015-03-26T12:52:38Z

2015-03-26T12:48:54Z

2015-03-26T12:40:43Z

2015-03-10T08:04:01Z

apertium-viewer.html

2014-11-19T08:40:23Z

apertium-viewer.html

2014-11-19T08:39:47Z

APY endpoint

2014-11-18T09:21:17Z

2014-11-18T09:18:53Z

apertium-viewer.html

2014-11-18T09:18:21Z

← Older revision		Revision as of 12:52, 26 March 2015
Line 1:		Line 1:
	This task is ~~now~~ done, see -r59428 and -r57945 in apy SVN.		This task is almost done, see -r59428 and -r57945 in apy SVN.

	==Still TODO==		==Still TODO==

@@ Line 1: / Line 1: @@
 This task is now done, see -r59428 and -r57945 in apy SVN.
-Still TODO:
+==Still TODO==
-* It should translate as you type (no caching, just do one request per keypress)
+* It should translate as you type
+** No caching, just do one request per keypress, with a [http://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/apertium-html-tools/assets/js/translator.js#l51 timeout]
-* It should send a NUL on each \0, not escape it
+* It should send a NUL on each \0, not escape it. This is still just one request, so we can send a \0 either with curl or from the HTML UI.
 ** We might just want to skip apertium-deshtml and assume the user can escape things on their own? Or we could let the user turn on/off deshtml.
 * It should look slightly prettier
+** tags, lemmas and symbols should have different colours (see [[apertium-viewer]])
-* _e in mode names turns into underlines in the dropdown
+* _e in mode names turns into underlined e in the dropdown, should just be _e
+* it'd be cool to be able to edit each step, like with [[apertium-viewer]], but maybe not that important.
 ==APY endpoint==
+(This task mostly done, see -r59428.)
 To start on this work, first look at what [[Apertium-viewer]] does.

@@ Line 1: / Line 1: @@
 This task is now done, see -r59428 and -r57945 in apy SVN.
+Still TODO:
+* It should translate as you type (no caching, just do one request per keypress)
+* It should send a NUL on each \0, not escape it
+** We might just want to skip apertium-deshtml and assume the user can escape things on their own? Or we could let the user turn on/off deshtml.
+* It should look slightly prettier
+* _e in mode names turns into underlines in the dropdown

@@ Line 1: / Line 1: @@
+This task is now done, see -r59428 and -r57945 in apy SVN.
 ==APY endpoint==
 To start on this work, first look at what [[Apertium-viewer]] does.

@@ Line 36: / Line 36: @@
 ==apertium-viewer.html==
+(This task mostly done, see tools/apertium-viewer.html in the apy source.)
 This html+js page should have an input box where you can type things like "te\0ost", another input box where you can type "isl|eng", and a button, and on clicking the button it should make a request to <code>http://localhost:2737/pipedebug?pair=isl|eng&q=te\0ost</code> and present the output like

@@ Line 53: / Line 53: @@
     Tea.[][\n]\0^Cheese.[][\n]\0\0\0\0\0
 with some colours to make it more readable.
+Since /pipedebug is not implemented yet, your request function can make a call to /translate with the same parameters, and then simply disregard the output, and return a hardcoded string containing the JSON in [[#Example pipedebug output]] above.
 You can also attach an event listener to the input box so it makes requests on typing (but [http://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/apertium-html-tools/assets/js/translator.js#l51 with a timeout]).

@@ Line 10: / Line 10: @@
     curl 'http://localhost:2737/translate?langpair=isl|eng&q=te\0ost'
-Example output:
+===Example pipedebug output===
     {

@@ Line 56: / Line 56: @@
 You can also attach an event listener to the input box so it makes requests on typing (but [http://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/apertium-html-tools/assets/js/translator.js#l51 with a timeout]).
+This should be done in plain javascript+html, no external libs. It has to work offline, with only a checkout of APY and the language pair in question.
 [[Category:Tasks for Google Code-in|Apy pipedebug]]

@@ Line 36: / Line 36: @@
 ==apertium-viewer.html==
+This html+js page should have an input box where you can type things like "te\0ost", another input box where you can type "isl|eng", and a button, and on clicking the button it should make a request to <code>http://localhost:2737/pipedebug?pair=isl|eng&q=te\0ost</code> and present the output like
+    lt-proc -z isl-eng.automorf.bin
+    ^te/te<n><m>/te<vblex><inf>$^./.<sent><clb>$[][\n]\0^ost/ose<vblex><pp>/ost<n><m>$^./.<sent><clb>$[][\n]\0
+    apertium-tagger -z -g isl-eng.prob
+    ^te<n><m>$^./.<sent><clb>$[][\n]\0^ost<n><m>$^./.<sent><clb>$[][\n]\0\0
+    lt-proc -z isl-eng.autobil.bin
+    ^tea<n>$^./.<sent><clb>$[][\n]\0^cheese<n>$^./.<sent><clb>$[][\n]\0\0\0
+    apertium-transfer -z apertium-isl-eng.t1x isl-eng.t1x.bin
+    ^Tea<n>$^./.<sent><clb>$[][\n]\0^Cheese<n>$^./.<sent><clb>$[][\n]\0\0\0\0
+    lt-proc -z -g isl-eng.autogen.bin
+    Tea.[][\n]\0^Cheese.[][\n]\0\0\0\0\0
+You can also attach an event listener to the input box so it makes requests on typing (but [http://sourceforge.net/p/apertium/svn/HEAD/tree/trunk/apertium-tools/apertium-html-tools/assets/js/translator.js#l51 with a timeout]).
 [[Category:Tasks for Google Code-in|Apy pipedebug]]