Status: Closed (View Workflow)
Affects Version/s: None
Fix Version/s: None
Windows 7 (64-bit)
In Windows, many of the Sword utilities (for 1.6.2) often generate these lines:
Error reading ulBuffNum
These are sent to stdout, rather than stderr, so they get included in any piped output from the former. The message usually occurs in triplicate!
This is an issue of considerable standing - it's been around for ages, but no-one seems to have come up with a fix yet.
It occurs when using tools like
Usually triggered by missing books, chapters or verses (in relation to the defined v11n).
A search through the mailing list archive indicates that several users have encountered the problem.
(not just me!).
Is anyone actually doing something about this?
(a) to ensure that these error messages are propelrly sent to stderr
(b) to fix the utils so that this particular error message is rarely sent