Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Ideas for Google Summer of Code/Visual interface to write structural transfer rules

From Apertium
Jump to: navigation, search

Contents

Apertium structural transfer rules are currently encoded in XML-based formats. These are very overt and clear, but clumsy and may be hard to write. The idea is to design a visual programming language of the style of like Scratch, where jigsaw-puzzle-style pieces corresponding to statements and control structures fit only if the syntax is right.

[edit] Tasks

  • Write a graphical user interface to write structural transfer rules (one that reads in (a subset of) the current XML-based language, allows for a graphical, intuitive editing of the rules, and writes compilable .t1x, .t2x or .t3x files)

[edit] Coding challenge

[edit] Frequently asked questions

  • none yet, ask us something! :)

[edit] See also

Check Appinventor.

Check Blockly.

Check Snap

Personal tools