Closed
Bug 1382
Opened 26 years ago
Closed 20 years ago
Problems with UTF-8 encoded attributes
Categories
(Directory :: PerLDAP, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: leif, Assigned: leif)
Details
From: Berbiche Mohcine <berbiche.mohcine@uqam.ca>
I have some problem to access to "mailautoreplytext" attribut.
I have no problem to access to a value of "mailautoreplytext" attribut with
ldapsearch command .
The $entry->{mailautoreplytext}[0] return no value. But with
$entry->{mailautoreplytext;lang-fr-ca}[0] the answer is right but without
accentuated characters.
Could you please help.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•26 years ago
|
Priority: P2 → P3
Clearing "M" field since Directory product is not used for 5.0 specific project
bug metrics and will mess up our queries on milestones.
Assignee | ||
Updated•25 years ago
|
Priority: P3 → P2
Assignee | ||
Comment 3•25 years ago
|
||
From Johan Kristian:
wrote a document for Directory Server developers, which you might find useful.
Any attribute description may have an option that indicates its
language/locale. See
<draft-ietf-ldapext-lang>.
In LDAP v3, characters are represented in UTF-8. For the details, see:
RFC 2251(LDAP) section 4.1.2
RFC 2252 (LDAP attributes)
RFC 2253 (LDAP DN)
RFC 2254 (LDAP filter)
RFC 2279 (UTF-8)
This leaves clients responsible for converting between UTF-8 and their local
charset. It can be a problem, which
is not solved by any LDAP SDK (that I know of). A key problem is
differentiating string-valued attributes (which
require conversion) from others (which must not be converted), such as
certificates and photos.
Comment 4•24 years ago
|
||
This bug has not been touched for more than nine months. In most cases, that
means it has "slipped through the net". Please could the owner take a moment to
add a comment to the bug with current status, and/or close it.
Thank you :-)
Gerv
Updated•20 years ago
|
Status: ASSIGNED → NEW
Assignee | ||
Comment 5•20 years ago
|
||
Closing as a no-fix, PerLDAP will not do any character set conversion at this
point, but modern Perl's have good support for UTF8.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•