mrob95 on texmaker
Add basic TeXMaker support (compare)
mrob95 on master
Create requirements.txt (compare)
mrob95 on master
Create install.bat (compare)
mrob95 on master
change to \(\) for inline math,… add equation* and align* update docs and 2 more (compare)
mrob95 on master
mrob95 on breathe
Transition sublime and template Update dependencies Add install script and 2 more (compare)
mrob95 on master
Create LICENSE (compare)
mrob95 on master
Add core context (compare)
mrob95 on master
Add install script (compare)
mrob95 on master
Update dependencies (compare)
mrob95 on languages
Improve formatting (compare)
mrob95 on languages
Initial multilanguage support load to edit Further improvement and 1 more (compare)
mrob95 on master
Transition sublime and template (compare)
language
setting is equal to nld
. English will always be used as a fallback
Major architectural change. Before updating you will need to run
pip install dfly-breathe
I have entirely replaced the old caster-based CCR backend with Breathe, a library I've been working on. Should make it much easier to add support for new apps etc, and I have fully fleshed out the NestedRule
concept which was originally prototyped here. Please let me know if there are any issues.
Well basically I wanted rules that were like:
Integral from <stuff1> to <stuff2>
Where stuff was a sequence of any other ccr commands. Nested rules were the first implementation based on Caster, breathe allows this by allowing the user to add custom top-level rules. The mathfly examples are in e.g. lyx.py
at the bottom but may be slightly difficult to understand at a glance, there are clearer examples on the breathe readme which show greedy dictation and optional repeat values using the same feature.
CommandsRef
extra which references a sequence of commands and then include an Exec
action to execute the sequence
say <text>
command, which should allow you to input text without using Dragon dictation
@mrob95 Not urgent as it only happens a few times an hour, but I wanted to report an error I'm getting with some of the longer strings of math dictation. In particular, I have latex-maths enabled and I'm getting some warnings in the Python output window. The relevant utterances also are simply not entered into my document. Here are a few examples:
WARNING:engine:Grammar MergeRule(Merged42Ma): failed to decode recognition (u'equals', u'uniform', u'sub', u'one', u'right', u'equals', u'uniform', u'sub', u'two', u'right', u'equals', u'uniform', u'sub', u'three', u'right', u'ampersand', u'equals').
and
WARNING:engine:Grammar MergeRule(Merged15Ma): failed to decode recognition (u'alpha', u'plus', u'x-ray', u'minus', u'one', u'right', u'prekris', u'one', u'minus', u'papa', u'right', u'super', u'script', u'eight', u'up', u'plus', u'november', u'minus', u'x-ray', u'minus', u'one', u'right').
Note that in the first example all of the component words are recognized correctly, while in the second example the word 'bravo' was misrecognized as 'eight up'. I believe even the misrecognition should have yielded a valid sequence of commands, however (if a somewhat silly one).
Like I said, not urgent, but probably a bug worth looking at some point. Let me know if I can provide any more information. Thanks.
Hi Anna, firstly I'm impressed that you can hold such a long string of commands in your head at once ^^. I have always needed a pause for thought after a few commands.
I am not 100% sure that this is the issue, but one thing you could try is bumping up the value of max_ccr_repetitions
in settings.toml a bit. I don't think there is any science behind the current maximum of 16. Someone chose it a long time ago as a number that was big enough to rarely cause issues while also not triggering grammar complexity errors, and it stuck.