Closed Bug 42777 Opened 25 years ago Closed 25 years ago

space treated wrongly, probably resulting in a warning about wrong character code

Categories

(Core :: Internationalization, defect, P3)

Product:
Core
Component:
Internationalization
Platform:
All
Other
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 47015

People

(Reporter: tarahim, Assigned: mozeditor)

Details

In Mail/News Compose (HTML) window, typing an ASCII space at the beginning of a line does not move the carret. It requires typing two spaces to move a carret to the right, and it moves by one double byte character width. This happens in the first two double byte character widths in a line, meaning first four ASCII spaces. After typing some spaces and returns, if the Option is Plain Text, a warning that wrong character code is contained in the message appears on Send. The bug might be a dup of 41637, but I am submitting it as a report on the warning problem. 2000061508M17 MacOS.
>In Mail/News Compose (HTML) window, typing an ASCII space at the beginning of a >line does not move the carret. It requires typing two spaces to move a carret >to the right, and it moves by one double byte character width. This >happens in the first two double byte character widths in a line, meaning >first four ASCII spaces. >Confirmed this problem on 6/15/2000 Win32 build. But I only saw the >problem for the first byte. Once a space is inserted after two >space bar hits, we seem to be able to insert ASCII spaces thereafter. >After typing some spaces and returns, if the Option is Plain Text, a warning >that wrong character code is contained in the message appears on Send. Was not able to confirm this problem. We need more precise reproducible steps. We also need to know which encoding the mail was supposed to be sent whent the warning came up. These 2 seem to be 2 separate bugs. Shall we deal with the 1st one here and defer the 2nd problem to some other bug? Or may be even an entirely new bug with reproducible steps?
Status: UNCONFIRMED → NEW
Ever confirmed: true
On the 2nd try I was able to reproduce the first problem as hirata-san describes. This problem also happens with general Composer. Should go to the Editor team for the first problem. Hirata-san, can you file the 2nd problem with reproducible detailed steps as a separate bug?
Assignee: nhotta → beppe
Product: MailNews → Browser
OK. I will try to find precise steps to reproduce the bug for the warning problem.
assigning to Joe for debugging
Assignee: beppe → jfrancis
Target Milestone: --- → M17
I think i am missing an important piece of information. Is this in Japanese IME mode that this happens? Because if not, then this is a worksforme. If it is, then it is a dup of 42574, right?
This is not dependent on IME. However, the encoding for the message was ISO- 2022-JP. I am not sure if it is a dup of 42574, since the problem is not confined to Japanese space, but single ASCII space is also affected.
ok, I understand this bug now. The key is that it doesn't happen on the first line. It only happens when you are immediately after a <br>. This is a dup of 43030, which I am working on. *** This bug has been marked as a duplicate of 43030 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Just to make sure. In my case, there is no need for typed <br>to cause this bug. The behavior starts right at the beginning of a message body. Is there an equivalent of <br> at the beginning of the body of a message?
ugh. ok, the I'm back to square one. I cannot reproduce this. I have a mac set up with system 9, with Japanese IME support installed. I turn it on from the menu bar. I type and see a space. It's a very wide space.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
OK, you were right. I have just found that there was indeed a <br> inserted when Mozilla displayed my signature in the mail compose window. Before typing anything in the body, I pressed delete, and could see the signature shift upward. Rest assured. Iam marking it as a dup of 43030. So, is it related to the <br> problem in various text areas? *** This bug has been marked as a duplicate of 43030 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
I am not so sure. When I tested without signature, the behavior was the same. The very first space did not appear after hitting space key. (Note that IME was not used.) On second space, cursor moved to the right by what looks like two spaces. On the third, coursor did not move. On the fourth, corsor moved again by two spaces. Afterwards, space appeared normal. Thus, first four spaces in every line appeared weird. That has been the same from the time this bug was filed.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Ok, lets leave this open and I'll try to reproduce it. Maybe it only happens in mail (i've been trying in Composer, which _should_ be the same, but maybe it isn't somehow...
The warning part of the problem is filed as 42871 but I assume that's not the current issue discussed in here.
I confirmed Hirata-san's initial report with a Windows build using Composer, not Mail composer. Here are precise stpes (confirmed with 6/20/2000 Win32 build) 1. Open Composer. 2. Don't turn on JPN IME but have it selected on the task bar. (i.e. ASCII input mode) 3. type abcd and then CR (This line is not significant but it gives you good contrast when you then try to reproduce this problem on the 2nd line.) 4. Now on the 2nd line, type "SP". --> nothing happens. the caret does not move. 5. Now type "SP" again. This time, the caret moves one ASCII space to right. 6. Now type "SP". --> nothing happens. the caret does not move. 7. Now type "SP" again. This time, the caret moves one ASCII space to right. At this point, the caret has moved 2 spaces to the right. 8. Now type "SP". This time, the caret moves to the right without a problem. After this point, there is no problem described in steps 4 and 6.
OS: Mac System 8.6 → other
Hardware: Macintosh → All
By the way, joe, it sounds like your Mac IME is set to insert a full-width Japanese space. I would try not to use the full-width space for this bug and instead choose to insert a half-widht/ASCII space instead.
Could you tell me how to tell IME that? I'm using Mac OS 9.
You either switch to US keyboard (US flag) by Command+space, or change the input mode within IME by hitting Control+shift+; in Kotoeri(JapaneseIME). You can also click the smaller sized "A" in the floating palette of IME to do this.
Yes. I agree with Hirata-san. This bug can be reproduced with the normal US keyboard ASCII. There is no reason to turn on the Japanese IME.
dup of 47015 *** This bug has been marked as a duplicate of 47015 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
OK. Verified as a duplicate of an umbrella bug.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.