From c210f766a0d65c17ddcaff933821ccc58f470e4d Mon Sep 17 00:00:00 2001 From: Kenichi Handa Date: Thu, 8 Mar 2001 04:42:43 +0000 Subject: [PATCH] (Fdetect_coding_region): Fix comments added by the previous change. --- src/coding.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/src/coding.c b/src/coding.c index 72f773fb2e1..877d2f59ece 100644 --- a/src/coding.c +++ b/src/coding.c @@ -6229,13 +6229,16 @@ highest priority.") if (from < GPT && to >= GPT) move_gap_both (to, to_byte); + /* If we an anchor byte `\0' follows the region, we include it in + the detecting source. Then code detectors can handle the tailing + byte sequence more accurately. + + Fix me: This is not an perfect solution. It is better that we + add one more argument, say LAST_BLOCK, to all detect_coding_XXX. + */ if (to == Z || (to == GPT && GAP_SIZE > 0)) include_anchor_byte = 1; return detect_coding_system (BYTE_POS_ADDR (from_byte), - /* "+ include_anchor_byteq" is to - include the anchor byte `\0'. With - this, code detectors can check if - tailing bytes are valid. */ to_byte - from_byte + include_anchor_byte, !NILP (highest), !NILP (current_buffer @@ -6261,8 +6264,8 @@ highest priority.") return detect_coding_system (XSTRING (string)->data, /* "+ 1" is to include the anchor byte `\0'. With this, code detectors can - check if tailing bytes are - valid. */ + handle the tailing bytes more + accurately. */ STRING_BYTES (XSTRING (string)) + 1, !NILP (highest), STRING_MULTIBYTE (string)); -- 2.39.5