Closed
Bug 81914
Opened 25 years ago
Closed 24 years ago
Getting POP mail has problems when language pack applied
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: kairo, Assigned: naving)
References
Details
This bug was first seen as bug 62735 but it doen't only happen with de-AT
language pack, it also happens with others.
Steps to Reproduce:
1. install Mozilla
2. install language pack (reproduced with de-AT or Asturian)
3. Create a new profile with that language
4. Open MailNews
5. Configure a (new) POP-account
6. Get messages (e.g. STRG-T or button/menu).
Actual results: Nothing. MailNews doesn't try to fetch new messages.
Expected results: MailNews gets new messages
From what 62735 discussion says, I expect that steps 4-6 are enough when
language pack is already applied.
If you create the account with en-US applied and change to the other language
later, the POP account stays working!
This was first reported with a nightly from 2000-12-11 (de-AT language pack),
reproduced several times with various milestones and nightlies since that date
and de-AT language.
Now we got a posting in n.p.m.l10n saying
"On the other hand, something that I've seen with Mozilla0.8, 0.9, and Netscape
6.01: if I install the English version, and then the Asturian langpack, and then
I try to setup an email account, it doesn't ask me for the password, so I cannot
check the email. But if I switch to English, the pop-up menu asking for the
password appears, and I can see the emails. Then I switch again to Asturian, and
email works fine."
There seems to be an underlying bug in MailNews here that some code doesn't deal
right with localized strings (I once thought of folder names but I can't debug).
Any idea?
Comment 1•25 years ago
|
||
L10N, are those language packs synchronized with trunk builds?
Umm... These packs are created by Mozilla Localisers. But it is possible that it
is an issue with unsynchronised packs
We used to have a problem with Japanese version of 6.0.
After we localized the default mail boxes to Japanese, It can't find the
correspondent POP mailboxes in English. It failed to connect to the server. So
we reverted back all the default mailboxes to English for that release. And the
i18n problem (bug 57440) is still there.
Comment 5•25 years ago
|
||
Is there way to check if the pop mbox names are localized in the lang packs?
| Reporter | ||
Comment 6•25 years ago
|
||
nhotta, danielmc: The langpacks are perfectly synchronized with the builds (as
far as I'm aware of it).
Maybe translated mail folder names (esp. Inbox, I think I _have_ translated it
to "Posteingang" in German [like everybody would assume in a good localization])
can cause that issue as ji stated.
Kostas <PKst@netscape.net> told me in n.p.m.l10n:
Hmm ....., I remember that I faced a similar problem with M.0.8 and the Greek
Language pack because the "inbox" strings were translated. When I changed the
"inbox" strings back to the original english everything was back to normal...
Comment 7•25 years ago
|
||
Robert, could you change those strings back to English and try again?
Comment 8•25 years ago
|
||
Looks like localization issue, reassign to rchen, cc to mcarlson.
Assignee: nhotta → rchen
So, this bug depends on bug 57440.
To work around, Mozilla Localisers have to put back English for their language
pack for now.
Reassigned to Tao.
Assignee: rchen → tao
Depends on: 57440
Comment 10•25 years ago
|
||
This is more like a mailnews i18n problem. L10n notes had been added into
"messenger.properties" (bug 64199)
Assignee: tao → putterman
| Reporter | ||
Comment 12•24 years ago
|
||
so can this one be set to FIXED as well now that bug 57440 is resolved FIXED?
Comment 13•24 years ago
|
||
Resolved this as fixed, since bug 57440 is fixed, connecting to POP mail account
with localized default mail foldernames shouldn't have problems now.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: MailNews → Core
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•