| Age | Commit message (Collapse) | Author |
|---|
|
one fix in DictionaryChi
|
|
|
|
|
|
|
|
|
|
still not optimal
|
|
|
|
|
|
|
|
|
|
|
|
|
|
generate definitions and examples for words in the App.
|
|
|
|
|
|
something. this requires one more step in the App compilation which is described in the README
|
|
|
|
|
|
there but the menu item for activating it is not there yet since the functionality is not complete
|
|
in the translation to disappear
|
|
|
|
it still produces the right TTS
|
|
|
|
database
|
|
|
|
|
|
|
|
|
|
version
|
|
|
|
|
|
|
|
|
|
|
|
|
|
but much faster
|
|
|
|
compile
|
|
|
|
|
|
|
|
(and of course follow the target lang conventions)
|
|
|
|
|
|
The API in the C runtime as well as in the Haskell, Python and Java binding
is changed. Now instead of adding the literal callbacks to the concrete syntax
you need to supply them every time when you need to parse. The main reason is:
- referentially transparent API for Haskell
- when we start using memory mapped files we will not be allowed to change
anything in the grammar data structures. At that point the old API would
be impossible to use.
|
|
|
|
|
|
|
|
|
|
|
