Add some comments as to why we don't want to use the modem's line count

From Lee:
|  commit b8062c0f76e3d3c37389aa07c950470bb41cec31
|  Author: Lee Howard <faxguy@howardsilvan.com>
|  Date:   Sat Dec 23 00:31:40 2006 +0000
|
|      Add some more comments as to why we don't want to use the modem's line count.

diff --git a/faxd/Class2Recv.c++ b/faxd/Class2Recv.c++
index ff60ac1c227991f9440d4e54de444fc392167b0a..460dca676b03fe7984ee5f0b245b8c619bd204dc 100644 (file)
--- a/faxd/Class2Recv.c++
+++ b/faxd/Class2Recv.c++
@@ -351,7 +351,12 @@ Class2Modem::parseFPTS(TIFF* tif, const char* cp, int& ppr)
 
        /*
         * In practice we cannot trust the modem line count when we're 
-        * not using ECM due to transmission errors.
+        * not using ECM due to transmission errors and also due to
+        * bugs in the modems' own decoders (like MMR).
+        *
+        * Furthermore, there exists a discrepancy between many modem's
+        * behaviors and the specification.  Some give lc in hex and 
+        * others in decimal, and so this would further complicate things.
         */
        if (!conf.class2UseLineCount) {
            lc = getRecvEOLCount();