Closed Bug 41439 Opened 24 years ago Closed 24 years ago

Int chars no longer gets imported correct

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Address Book & Contacts
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 38844

People

(Reporter: bugzilla, Assigned: chuang)

References

Details

(Whiteboard: [nsbeta2+]) 

When you import a Netscape 4.73 addressbook (.LDIF) danish chars no longer 
appears correct. A danish "æ" æ get imported as "æ".
This used to work!

Build 2000060308
The LDIF entry:
dn: cn=Hænrik Gemal,mail=gemal@dk.net
modifytimestamp: 20000223100831Z
cn: Hænrik Gemal
mail: gemal@dk.net
xmozillausehtmlmail: FALSE
givenname: Hænrik
sn: Gemal
objectclass: top
objectclass: person

should give me:
Hænrik Gemal
reassign to chuang. cc momoi.  Kat, do you know if this is happening with other
languages besides danish?
Assignee: putterman → chuang
Looks like a big regression.
Yes, this used to work during M16.I have a build from 
4/16 on my hard disk and it works with my multiligual
data as well as Latin1 & Japanese data imports with .ldif
files. But another build I have from 5/16 exhibits the
same problem Gemal talks about. So does the build from
6/3/2000.
Nominating for nsbeta2.
Keywords: nsbeta2
QA Contact: lchiang → momoi
It looks like we are misconverting UTF-8 data in .ldif files.
I believe this is the same bug as 38844.  Import utility has convert the UTF-8 
string twice in ldif file.  I have the fix.
Status: NEW → ASSIGNED
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [nsbeta2+]
This is a dup of bug # 38844
Gemal, I'm going to mark this a duplicate of 38844.
I've marked dependency on that bug. Please check out
your data when that bug gets fixed. I've assigned the
verification task to you. Thanks.

*** This bug has been marked as a duplicate of 38844 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Depends on: 38844
QA Contact: momoi → gemal
Resolution: --- → DUPLICATE
Verified duplicate.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.