Closed
Bug 275645
Opened 20 years ago
Closed 19 years ago
Chinese word can only show half
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: xbtsw, Assigned: smontagu)
References
()
Details
Attachments
(2 files)
Some Chinese words can only see half This problem usually appear in the last word of the sentence and usually only can show the left half of it. I also have a snap picture of this problem in jpg format,but I don't know how to sent it to you.
i have notice it in the bug describe, as you see, some Chinese word can only see half.
| Assignee | ||
Comment 2•20 years ago
|
||
The problem seems to be in the page source. I am guessing that the forum software is truncating the post titles to a fixed length, and this sometimes cuts a multi-byte character in half.
Assignee: bugs → smontagu
Component: View Source → Internationalization
Product: Firefox → Core
QA Contact: firefox.view-source → amyy
Version: 1.0 Branch → Trunk
Comment 3•20 years ago
|
||
(In reply to comment #2) > The problem seems to be in the page source. I am guessing that the forum > software is truncating the post titles to a fixed length, and this sometimes > cuts a multi-byte character in half. Indeed that appears to be the case. However, that doesn't explain what's captured in attachment 169347 [details] (the first case in the screenshot) because a lone lead byte of a multibyte character is invalid so that it has to be rendered with '?' or gibberish instead of a glyph being cut in half.
(In reply to comment #3) > (In reply to comment #2) > > The problem seems to be in the page source. I am guessing that the forum > > software is truncating the post titles to a fixed length, and this sometimes > > cuts a multi-byte character in half. > > Indeed that appears to be the case. However, that doesn't explain what's > captured in attachment 169347 [details] [edit] (the first case in the screenshot) because a lone > lead byte of a multibyte character is invalid so that it has to be rendered with > '?' or gibberish instead of a glyph being cut in half. > > > > Thanks for your kind reply, and a new discovery of this problem is that when I select the last unshown word in the sentence it will show correctly.But when I select the hole sentence the problem will happen again.Please see the attachment I update this time. And this problem will go in progress that means the more word words I selected the unshown part will be more, at last, when I select the hole sentence the unshown part will become half.
Updated•20 years ago
|
Attachment #169419 -
Attachment mime type: image/jpeg → application/x-rar-compressed
Comment 6•20 years ago
|
||
I can't reproduce it on Linux with gtk2+xft (1.7.5). I'll try my trunk build. re: attachment 169419 [details]: Open 7 jpeg files in attachment 169419 [details] and compare them side by side. The more characters are selected from the right, the more characters (among those not selected) disappear (get obscured by the selection?)
(In reply to comment #6) > I can't reproduce it on Linux with gtk2+xft (1.7.5). I'll try my trunk build. > > re: attachment 169419 [details] [edit]: > Open 7 jpeg files in attachment 169419 [details] [edit] and compare them side by side. The more > characters are selected from the right, the more characters (among those not > selected) disappear (get obscured by the selection?) And please notice the last character(before the "?"),the more characters I select from the right the more the last character disappear, at last, half of it disappeared.
Comment 8•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 9•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•