Re: [ldapext] new version of LDIF

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

Yves Dorfsman wrote:
>Hallvard B Furuseth wrote:
>> If a file or entry has 'charset: ...' this should not only affect

Typo, it _should_ only affect...

>> 'attr: val', not 'attr:: val' and 'attr:< file'.  The two latter may
>> contain non-text data, e.g. a jpeg picture.
> 
> Hmmm... I think the IBM server already has such an extension. With utf-8 
> finally getting some traction, is there really any point to spend any energy 
> for other charset ?

I've no opinion, really.  UTF-8 has been "just about to take over the
world" for a decade now.  Maybe it's finally happening, but I'm not
holding my breath.  So as far as I'm concerned it'd be nice to have, but
low priority.

> What would the other charsets offer that utf-8 cannot, I mean beyond not 
> having to convert ?

Well, support for other applications than LDAPv3, since LDAPv3 will
require the LDIF parser to charset-convert to UTF-8.  But if such a
thing would need non-UTF-8 support it would likely have it now anyway.

-- 
Hallvard
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext