27564 - [i18n] Profile migration fails for local Japanese mailboxes with 0x5c in them

Status: VERIFIED FIXED

(MailNews Core :: Profile Migration, defect, P3)

Description

[Katsuhiko Momoi]

** Observed with 2/12/2000 Win32 build **

This bug was discovered in the process of checking out Bug 7844.

1. I created 3 JPN mailbox folders with 4.7x.
2. Then I tried migrating this 4.7x profile with the above
   Mozilla build.
3. One of the 3 mail folder names contained the following
   byte sequence, .... 0x95 0x5c 0x8e 0xa6 in system charset (Shift_JIS).
4. In migrating this folder, Mozilla interpreted the 0x5c
   to be the backslash "\" and the migrated name contained
   only the bytea after it, i.e. 0x8e 0xa6

Naoki should know how to approach this problem.

Comment 1

[Andreas Otte]

I think the migration tool should escape the foldername before handing it to the
urlparser.

Comment 2

[dbragg]

Seth, I think this one might be in your area. Reassigning to y'all.

Comment 3

[(not reading, please use [e-mail] instead)]

marking m15.

momoi, can you help me get local japanese folders in 4.x?

Comment 4

[Katsuhiko Momoi]

http://rocknroll/users/momoi/publish/seamonkey/bugs/bug27564/

Seth, I deposited 2 Japanese mailbox files with 
matching .snm files at rocknroll. I wanted to Zip them but 
the utility failed because 2 of the files contained
0x5C and ZIP utility was not designed for Japanese.  :(

1. Please copy them into a 4.7x mail folder and try
   migrating. 
2. The shorter of the 2 file name contains 0x5C in the 
   2nd byte of the 1st character. The longer contains no
   0x5C value and should survive migration intact.

Note: I'm not sure if this is going to work 100%. 
      You're probably dropping Japanese file names into
      an US system. The US file system may do something
      funny to the names. Naoki? Also if the migration is
      supposed to take into account what kind of file system
      it is on before migrating file names, then not being
      on Jpaanese Windows would make things very difficult.

Comment 5

[Katsuhiko Momoi]

I may have to give these files on a disk.

Comment 6

[(not reading, please use [e-mail] instead)]

moving to m16.

momoi / naoki, is this really a mailnews bug, or an i18n bug?  I forget now.

Comment 7

[nhottanscp]

Not sure if mailnews or i18n but is somewhere in the migration code searching 
for a backslash?
If so and the string is not unicode then that might be a problem (misinterpret 
part of a double-byte character as a backslash).

Comment 8

[bobj]

Nominating for beta2.  Need to be able to migrate 4.x Japanese mailboxes.

Comment 9

[selmer (gone)]

Triage to M17.  Please add beta2 keyword if this must make beta2.  Please let me 
know if this must be done by M16 feature freeze.

Comment 10

[Katsuhiko Momoi]

Yes. this is definitely Beta 2 item. Migration of 4.x profiles should not fail just because
the name of the existing profile contained some characters we cannot handle.

Comment 11

[leger]

Putting on [nsbeta2+] radar.  

Comment 12

[leger]

Per momoi:
"this has been broken so long, we cannot go any further on profiles containing 
these characters. If we don't have this fixed soon, we will not know
what else might be broken with regard to these characters. In other words, we 
need moretime to learn more about profiles containing these characters in the 
names but are prevented from doing so because of this bug."

Moving to [dogfood+]

Comment 13

[(not reading, please use [e-mail] instead)]

busy with skin bugs and other features / bugs.

steve / varada, is this something varada can help out with?

Comment 14

[nhottanscp]

This might have been fixed by recent changes. Momoi san, when was the last time 
did you see this?

Comment 15

[Katsuhiko Momoi]

** Checked with 5/3/2000 Win32 build **

Thanks, nhotta!
This problem seems to have been fixed by another bug 
fix. I created a bunch of mailbox folders using 4.72 and
migrated a profile containing these mailbox files. 
Some of the mailbox files contained 0x5c characters and
they all seemed to work OK-- can display, copy, move
msgs contained in such folders.

I'm going to mark this bug resolved/fixed
and then verify it.

Comment 16

[Katsuhiko Momoi]

Marking the resolution verified.