Closed
Bug 224087
Opened 21 years ago
Closed 21 years ago
IS_CJ_CHAR should not return true for u > 0xFFEF
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: timeless, Assigned: timeless)
Details
Attachments
(1 file)
621 bytes,
patch
|
smontagu
:
review+
roc
:
superreview+
|
Details | Diff | Splinter Review |
/Users/timeless/mozilla/content/base/src/nsPlainTextSerializer.cpp:
In member function `void nsPlainTextSerializer::Write(const nsAString&)':
1761: warning: comparison is always true due to limited range of data type
1761: warning: comparison is always true due to limited range of data type
![]() |
||
Comment 1•21 years ago
|
||
The problem is the last test in the IS_CJ_CHAR macro:
http://lxr.mozilla.org/seamonkey/source/intl/unicharutil/util/nsUnicharUtils.h#94
Don't we have a bug on that already? This would be a dup.
Whiteboard: DUPEME
Comment 2•21 years ago
|
||
I don't think it's a dupe (of bug 223707), because there are two, count 'em, two
versions of the macro, IS_CJ_CHAR and IS_CJK_CHAR. The difference is deliberate:
IS_CJ_CHAR doesn't include Korean characters.
In any case all these macros (and probably their callers) need updating to
Unicode 4.0, but I suggest you just correct the warning for now as in bug 223707.
.
Assignee: dom-to-text → timeless
Component: DOM to Text Conversion → Internationalization
QA Contact: amyy
Summary: warning: comparison is always true due to limited range of data type in member function `void nsPlainTextSerializer::Write(const nsAString&)' → IS_CJ_CHAR should not return true for u > 0xFFEF
Whiteboard: DUPEME
Attachment #134403 -
Flags: superreview?(tor)
Attachment #134403 -
Flags: review?(smontagu)
Comment 5•21 years ago
|
||
Comment on attachment 134403 [details] [diff] [review]
change the limit from 0xFFFF to 0xFFEF
r=smontagu
Attachment #134403 -
Flags: review?(smontagu) → review+
Attachment #134403 -
Flags: superreview?(tor) → superreview?(roc)
Attachment #134403 -
Flags: superreview?(roc) → superreview+
checked in
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•