Popcorndude: Created page with "This project is very open-ended and whoever does it will have a great deal of say about which direction to take the project. Possible directions include: * Generating written..."

2021-04-10T01:50:45Z

Created page with "This project is very open-ended and whoever does it will have a great deal of say about which direction to take the project. Possible directions include: * Generating written..."

New page

This project is very open-ended and whoever does it will have a great deal of say about which direction to take the project. Possible directions include:

* Generating written explanations of what rules are doing
* Drawing pictorial representations of rules
* Tracing the execution of a set of rules
* ... or any combination of the above

You could also reasonably expand this project to include working on specialized editor modes (emacs, vim, atom, etc) or linters.

=== Coding Challenge ===

Create a tool like https://github.com/Jakespringer/dapertium that works for monodix files (that is, it takes a dictionary and generates a graph of paradigms, optionally tracing which paradigms are involved in generating a particular form)

=== Further Links ===

https://github.com/apertium/tree-sitter-apertium has parsers for most of the file formats in Apertium and it has been determined that their bindings are definitely usable in [https://github.com/apertium/apertium-stats-service Rust] and [https://github.com/mr-martian/apertium-lint Python] and other languages probably work too.

https://github.com/mr-martian/apertium-lint a linter

[[Emacs]] for the current state of specialized editor modes

Ideas for Google Summer of Code/Visualization tools - Revision history

Popcorndude: Created page with "This project is very open-ended and whoever does it will have a great deal of say about which direction to take the project. Possible directions include: * Generating written..."