Closed
Bug 206207
Opened 21 years ago
Closed 10 years ago
PC address book name containing non-ascii characters fails during a palm sync
Categories
(MailNews Core Graveyard :: Palm Sync, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nbaca, Unassigned)
References
Details
Trunk build 2003-05-18: WinXP Overview: Create a Mozilla address book using non-ascii characters (i.e. à). Peform a palm sync and the address book never appears on the palm device. Expected Results: The palm device should display all Mozilla address books including those using non-ascii characters. Workaround: Users can create the non-ascii category on the palm device, perform a palm sync and it displays in the Mozilla AB. Note: cards with non-ascii characters are fine whether synced from MozAB to palm device or visa versa.
Reporter | ||
Comment 1•21 years ago
|
||
Marking nsbeta1 so that this is fixed eventually. I would expect this to be important for International.
Keywords: nsbeta1
Ninoschka, i wonder what happens if the AB name doesn't start witn non-ascii chars??
Comment 4•21 years ago
|
||
It's the same. If you use Mozilla with german locale, then the standard AB has non-ascii characters in the middle and it will not be created on the Palm.
Updated•20 years ago
|
Product: MailNews → Core
Comment 5•19 years ago
|
||
marking depends in case bug 237624 doesn't completely resolve the issue.
Assignee: cavin → nobody
Depends on: 237624
QA Contact: nbaca
Summary: Mozilla address book using non-ascii characters fails during a palm sync → PC address book name containing non-ascii characters fails during a palm sync
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
QA Contact: palmsync
Comment 6•10 years ago
|
||
This bug has been buried in the graveyard and has not been updated in over 5 years. It is probably safe to assume that it will never be fixed, so resolving as WONTFIX. [Mass-change filter: graveyard-wontfix-2014-09-24]
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•