I would say the entire functionality that you propose could be implemented and tested in ~3 weeks, also in a cross-browser manner. Mouseover translation is trivial. Whole document translation is not trivial, but also not that hard. But that's speaking as someone who has implemented this exact DOM manipulation in multiple languages.
Still, I think this is a worthwhile project. Since I am quite sure you'll be done before time, I propose a stretch goal of inline gisting, which is like mouseover translation but with context. It's essentially a combination of full document translation, but retaining the original language text and giving the translation on hover/touch. This is not trivial, as it would require alignment of input with output - which is something last year's GSoC made possible, but nobody has used yet. -- Tino Didriksen On Fri, 9 Apr 2021 at 17:50, Omkar Prabhune <omkar.prabhune....@gmail.com> wrote: > Hello Everyone, > > I'm Omkar Prabhune, a sophomore in CompSci and I have submitted a > proposal for GSoC 2021 on the Project Idea: *Reworked Apertium Browser > Plugin* > > I have prepared a draft here and have received some great ideas on it but > I'd always appreciate more suggestions. I'm also usually active on the IRC > chat with the username <op> > > Link to the Document: > https://docs.google.com/document/d/1HtvZH7Vg08n0XmedMEVzXceKbu0QPhvv92xSzqDI25E/edit?usp=sharing > > Thanks, > Omkar Prabhune >
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
