Closed Bug 299292 Opened 20 years ago Closed 19 years ago

exporting address book in ldif format outputs garbage whenever French letters like "é" are part of the data

Categories

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

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: ihoule, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319

Create an entry in the address book and write the first name as "Rémi".  Export
the address book using the ldif format.  Look up the ldif file with notepad and
you'll find that the "givenName:" tag contains garbage characters.  The same
thing happens for any other tag where vowels with French accents are used.

Reproducible: Always

Steps to Reproduce:
1.(See details)
2.
3.

Actual Results:  
The ldif file contains garbaged characters but is still usable.  However some
information is obviously lost since it is replaced with the garbled text.

Expected Results:  
The tag should have displayed "givenName: Rémi" instead of "givenName::
Gtks45FrT67*5"
Related to bug 168241 and Thunderbird bug 277560?
Reporter, I believe that this is correct functionality. The RFC specification
for the LDIF export is found at:

http://www.ietf.org/rfc/rfc2849.txt

Note that fairly early on it states that:

Any dn or rdn that contains characters other than those defined as
"SAFE-UTF8-CHAR", or begins with a character other than those defined as
"SAFE-INIT-UTF8-CHAR", above, MUST be base-64 encoded.  Other values MAY be
base-64 encoded.  Any value that contains characters other than those defined as
         "SAFE-CHAR", or begins with a character other than those defined as
"SAFE-INIT-CHAR", above, MUST be base-64 encoded. Other values MAY be base-64
encoded.



I've had a play around with the values we output, and as far as I can tell, they
are correctly base-64 encoded.

Therefore I'm resolving this bug as invalid, however, if you think we are
incorrectly encoding in base-64 please reopen with explainations and more
examples if possible.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
*** Bug 323130 has been marked as a duplicate of this bug. ***
*** Bug 341391 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.