Closed
Bug 118618
Opened 23 years ago
Closed 23 years ago
Non-latin1 display name is dropped after Export/Import
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.8
People
(Reporter: marina, Assigned: nhottanscp)
Details
Attachments
(1 file)
600 bytes,
patch
|
naving
:
review+
sspitzer
:
superreview+
|
Details | Diff | Splinter Review |
*** observed with 2002-01-07 build ***
Steps to reproduce:
-Select your PAB or CA ( or any AB where there are non-latin1 entries);
-Import/Export this AB;
-now select the imported AB and note that the non-latin1
(cyrillic,japanese,chinese) Display names are missing, you can see only their
email addresses
Assignee | ||
Comment 3•23 years ago
|
||
>-Import/Export this AB;
Does this mean import first then export? When does the problem happen, after import?
no, i meant to save it first ( export) and then import into AB. Actually the
loss happens already on the Export stage, if i would open the exported AB (or
CA) in Notepad i would see the non-latin1 display names as commas ",,,,," or
just as space in Excel. So when those entries are imported they Display names
certainly are showing up as blank.
Summary: Non-latin1 display name is dropped after Import/Export → Non-latin1 display name is dropped after Export/Import
Assignee | ||
Comment 5•23 years ago
|
||
Is this a new problem or you can see it on older Netscape releases?
Status: NEW → ASSIGNED
well, the Export feature is new, it just was introduced. the Import was present
in 6.2. If i would use 6.2 rtm i would still see the imported AB ( from 6.2.1.+)
with missing non-latin1 display name but i think that the saving (exporting) is
not working correctly, i don't think it is an import problem.
Assignee | ||
Comment 7•23 years ago
|
||
What format did you use for the export, ldif?
it doesn't work in .ldif format yet, Seth made it available only in .csv, .tab
and .txt format. I used all three when testing.
Assignee | ||
Comment 9•23 years ago
|
||
For those format, I think it should be in a system charset. It should be UTF-8
for ldif.
Reassign to putterman.
Assignee | ||
Comment 10•23 years ago
|
||
Marina, when you tested cyrillic,japanese,chinese, did you used localized Windows?
Reporter | ||
Comment 11•23 years ago
|
||
no, i didn't.I know that the text format like csv and tab would be system
dependant but how would we handle multilingual PAB and CA in that case? My PAB
has entries in almost all languages.
Assignee | ||
Comment 12•23 years ago
|
||
LDIF uses UTF-8 so it can supports multiple languages.
Reporter | ||
Comment 13•23 years ago
|
||
would the display name shows up garbled in csv and tab then it would be maybe
less confusing as just a blank display..?
Assignee | ||
Comment 14•23 years ago
|
||
We usually put '?' for characters not converted to the target charset. Let me
make the change.
Assignee | ||
Comment 15•23 years ago
|
||
Comment 16•23 years ago
|
||
Comment on attachment 64042 [details] [diff] [review]
Set output behavior for unicode encoder to prevent the convesion to be aborted.
r=naving.
Can you test migrating
filters with non-ascii
filter name and folder name
(4.x to 6.x), thanks.
Attachment #64042 -
Flags: review+
Assignee | ||
Comment 17•23 years ago
|
||
I tested this for export address book to .txt. I don't think this is used for
migration which needs conversion to unicode but not from unicode. My change is
for converting from unicode.
Assignee | ||
Updated•23 years ago
|
Target Milestone: --- → mozilla0.9.8
Comment 18•23 years ago
|
||
Comment on attachment 64042 [details] [diff] [review]
Set output behavior for unicode encoder to prevent the convesion to be aborted.
sr=sspitzer
Attachment #64042 -
Flags: superreview+
Assignee | ||
Comment 19•23 years ago
|
||
checked in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 20•23 years ago
|
||
it is working correctly now: on Latin1 OS the imported/exported non-latin
entries re displayed as ?????. In ldif format all entries after Import/Export
are showing up correctly
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•