stypox / dicio-sentences-compiler

Sentences-compiler for Dicio assistant

Ciao! I am Stypox:

• Passionate contributor to free software, enjoys writing code to replace apps and services that do not respect the user
• Member of MindsHub, a no-profit association focused on education and team work in the fields of informatics, electronics and 3d printing
• Participates to competitive programming and cybersecurity competitions and is a tutor for younger students
• Studies information engineering at University of Trento
• User of Manjaro Linux with KDE and owner of a Fairphone 3+ with /e/OS

I'm currently working on:

• Dicio: an Android voice assistant (available on F-Droid and Play Store)
• NewPipe: an Android YouTube frontend with many cool features the official YouTube app doesn't have (available on F-Droid)
• dicio-numbers: a Java library for multilanguage number parsing and formatting
• Tridenta: an app to view public transport information in Trentino (available on F-Droid and Play Store)
• Curriculust: a Rust program that allows writing a CV in YAML and turning that into LaTeX and PDF

Other projects I'm proud of are:

• Crop detection: an AI model to detect crops in images, a building block of MindsHub's Cyberorto, an autonomous farmer
• Plotter: some scripts and algorithms to print G-code, text or images with a custom-made 2D plotter
• Quadermas: an Android app to access "Quaderno Elettronico Mastercom" (available on F-Droid)
• Olympiad exercises: the competitive programming code I've produced to train for the Italian Olympiad in Informatics
• Insigno: an app by MindsHub that gameifies reporting and collecting trash (available on F-Droid, Play Store and Apple Store)

dicio-sentences-compiler's Issues

Output files always have to be UTF-8

Android Studio can't normally compile UTF-16 files, so the UTF-16 encoding for output can't be used. So when the output is UTF-8 unicode characters in sentences should be written as "\uXXXX" in Java strings.

The directory containing the output file is not automatically created

This could be the expected behaviour.

Allow concatenating words to e.g. combine different declensions

For example cherche-(r|z)? should be unfolded into cherche|chercher|cherchez

Consider to continue development on Rust

I would like to suggest to switch this library to Rust and continue development on Rust.
Reasons:

1. It can be shared with other projects on C++ or Rust
2. It will be safe as well as on Java (but even safer in case of multi threading)
3. It is not limit us on performance (and even in case of heavy NLP onnx models)
4. We can create a skill repository and write skills on WASM and link them as plugins - community driven skills
5. Rust is a best language for such kind of things(parsers, matchers etc.)
6. I has very loose coupling with Main Java application (interface should be quite simple)

Some links:
https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-21-rust-on-android.html
https://medium.com/visly/rust-on-android-19f34a2fb43
https://freemasen.com/blog/wasmer-plugin-pt-1/

Unable to mark word as optional without parenthesis

e.g. a| b is not interpreted as "a optional, b" but as "a or b". There is no way to mark a as optional without putting parenthesis around a| (or around b).

Match words without considering diacritics by default

For example, in French météo should also match meteo for convenience, since removing the diacritics does not create a new word with a different meaning. So by default words should be matched without considering diacritics. A different syntax can be added to enforce diacritic matching, like sorrounding words with ".