search

nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.1k stars 634 forks source link

Send liblouis log output to the NVDA log #4554

Closed nvaccessAuto closed 5 years ago

nvaccessAuto commented 10 years ago

Reported by jteh on 2014-10-16 23:18 liblouis logs information which could be useful in debugging problems. We should send liblouis log output to the NVDA log at level debugWarning (or perhaps debug if it's too much). This is now possible with the logging callback introduced in liblouis 2.6.0.

LeonarddeR commented 7 years ago

cc @JCSTeh @DKager

dkager commented 7 years ago

I have been meaning to add the necessary functions to the Python wrapper, but haven't done so yet. One potential problem is that liblouis has its own log levels, which don't map to NVDA log levels. For example, I think most of what liblouis logs shouldn't be included in NVDA's default (info) level.

jcsteh commented 7 years ago

I'd say just push all liblouis log output as debug in NVDA's log. Even if it's reporting an error, that should cause an error higher in the code (e.g. translate failing). The dev can then poke at the log to get more details.

LeonarddeR commented 7 years ago

May be even add a separate option to the configuration system similar to HwIo debugging?