diff options
| author | Eli Zaretskii <eliz@gnu.org> | 2002-04-26 12:03:20 +0000 |
|---|---|---|
| committer | Eli Zaretskii <eliz@gnu.org> | 2002-04-26 12:03:20 +0000 |
| commit | d37478d0d7bf30c941bd5accd922a54dea0f49c8 (patch) | |
| tree | c00481ba59ae72ff714f6a51777beb3e5dba127a /src/charset.c | |
| parent | 3ae62f22e0140acfbc54ed3a8dcd181904479293 (diff) | |
| download | emacs-d37478d0d7bf30c941bd5accd922a54dea0f49c8.tar.gz | |
(CHAR_COMPONENTS_VALID_P): Tell in a comment that some invalid pairs are
intentionally allowed.
Diffstat (limited to 'src/charset.c')
| -rw-r--r-- | src/charset.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/charset.c b/src/charset.c index 818457f8e1b..118d5fed9ba 100644 --- a/src/charset.c +++ b/src/charset.c @@ -143,7 +143,10 @@ invalid_character (c) (charset) = (str)[1], (c1) = (str)[2] & 0x7F, (c2) = (str)[3] & 0x7F; \ } while (0) -/* 1 if CHARSET, C1, and C2 compose a valid character, else 0. */ +/* 1 if CHARSET, C1, and C2 compose a valid character, else 0. + Note that this intentionally allows invalid components, such + as 0xA0 0xA0, because there exist many files that contain + such invalid byte sequences, especially in EUC-GB. */ #define CHAR_COMPONENTS_VALID_P(charset, c1, c2) \ ((charset) == CHARSET_ASCII \ ? ((c1) >= 0 && (c1) <= 0x7F) \ |