Open Bug 77381 Opened 24 years ago Updated 7 years ago

support charsets other than UTF8

Categories

(Directory :: LDAP XPCOM SDK, enhancement, P5)

Product:
Directory
Component:
LDAP XPCOM SDK
Type:
enhancement

Tracking

(Not tracked)

Milestone:
Future

People

(Reporter: dmosedale, Unassigned)

References

Details

Right now, we're assuming that all LDAP data is UTF8, because LDAPv3 data is defined to be stored that way. However, there are likely to be some number of legacy ldap servers still running with T.61, Latin-1, or some other charset. If the demand is big enough, the XPCOM SDK may need to deal with that.
Blocks: 17880
Status: NEW → ASSIGNED
Priority: -- → P3
Keywords: nsbeta1
Target Milestone: --- → mozilla0.9.2
reassign to Olga as QA contact
QA Contact: yulian → olgac
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla1.0
Blocks: 104166
Taking. However, I have yet to hear of any complaints about the lack of this functionality. Additionally, this bug becomes less relevant as LDAPv2 continues to be replaced by LDAPv3.
Assignee: leif → dmose
Status: ASSIGNED → NEW
Priority: P3 → P5
QA Contact: olgac → yulian
Target Milestone: mozilla1.0 → Future
Assigning bugs that I'm not actively working on back to nobody; use SearchForThis as a search term if you want to delete all related bugmail at once.
Assignee: dmose → nobody
Filter on "Nobody_NScomTLD_20080620"
Assignee: nobody → dmose
QA Contact: yulian → xpcom
Assignee: dmose → nobody
You need to log in before you can comment on or make changes to this bug.