You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: