Closed Bug 299688 Opened 19 years ago Closed 18 years ago

Japanese text is corrupted randomaly,

Categories

(Calendar :: Sunbird Only, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cup_o_smuck, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

I suspect that the unicode contains a escaped end of line that that is
corrulting the following line in the iCal format of the next entry... it doesnt
crash but the  text is display as ?? since the achors are misaligned... if i
change a nearby entry sometimes another field is uncorrupted and then something
else is corrupted... so the data on file is ok... but the displaying of it isnt
correct

Reproducible: Sometimes

Steps to Reproduce:
1. insert about 20 items with random japanese text
2. shut down Calandar and reset
3. look over the entries and notice that some of the names done display
4. this is very random... and i cant give u iCal files since they contain
senative infomation

Actual Results:  
something a corruption appears, something not...

Expected Results:  
the text is displayed correctly
ashley, do you still see this behavior with Sunbird 0.3a2? Over 9 months have passed since this bug report, so maybe something has changed.
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o

Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
I have followed all the steps and there is no data lose. This might have occured because of 0.2, but this bug should be closed.
I have tested this on Sunbird 0.3, and I can confirm Matthaeus's statement. There is no longer corruption of Japanese text. 

Ashley, if you can still reproduce this bug with Sunbird 0.3, please file a new issue using a test calendar so that you can also post the ICS file that creates the issue.

Since we cannot reproduce the issue, and since the issue appears to be resolved in the latest release, I am moving to works for me and removing qawanted flag.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.